Services & Resources / Wolfram Forums
MathGroup Archive
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 2006

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: Preventing NIntegrate from reevaluating after DumpSave and Get

  • To: mathgroup at
  • Subject: [mg68817] Re: Preventing NIntegrate from reevaluating after DumpSave and Get
  • From: Jens-Peer Kuska <kuska at>
  • Date: Sat, 19 Aug 2006 00:41:43 -0400 (EDT)
  • References: <ec3ps8$2c2$>
  • Sender: owner-wri-mathgroup at


you must remove the NIntegrate[] calls *before* you make the dump-save.
Or, just an idea


overwrite temporal NIntegrate[]


Chris Rodgers wrote:
> Hi,
> I have been running a computation in Mathematica which attempts to
> NIntegrate[myformula,{t,0,infinity}] for many different model parameters.
> The results are in a large list. e.g.
> resultslist = {0, 7, 13.33,
> NIntegrate[myformula_at_tricky_parameter_vals,{t,0,infinity}],11,2,...}
> Notice that sometimes NIntegrate does not converge for particular model
> parameters.
> At the end of a long-running batch job, I DumpSave this results list.
> Now, my question is this:
> When I load the results back into Mathematica and try to use them things
> are very slow. I suspect that this is because Mathematica retries
> evaluating all the NIntegrate[...] on which it got stuck the first time
> around.
> I have tried e.g.
> Get[""]
> sanelist = resultslist /. NIntegrate[___]->NotANumber
> but this also takes ages evaluating the NIntegrate[...].
> Is there an easy way to load the .mx file and eliminate any of the
> non-converged NIntegrate[...] entries without having to wait for them to
> all be evaluated another time?
> Many thanks in advance,
> Chris Rodgers.

  • Prev by Date: Re: Re: too many special linear matrices
  • Next by Date: Re: "Skip this Input cell" module?
  • Previous by thread: Re: Preventing NIntegrate from reevaluating after DumpSave and Get
  • Next by thread: memory issues