MathGroup Archive 2006

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

Search the Archive

Preventing NIntegrate from reevaluating after DumpSave and Get

  • To: mathgroup at smc.vnet.net
  • Subject: [mg68754] Preventing NIntegrate from reevaluating after DumpSave and Get
  • From: Chris Rodgers <rodgers at physchem.NOSPAMox.aREMOVEc.uk>
  • Date: Fri, 18 Aug 2006 03:11:58 -0400 (EDT)
  • Organization: University Of Oxford, England
  • Sender: owner-wri-mathgroup at wolfram.com

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["MyFile.mx"]

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: General--Simplify exponents in exponential terms
  • Next by Date: Re: calculate Recurrence Equations
  • Previous by thread: General--Simplify exponents in exponential terms
  • Next by thread: Re: Preventing NIntegrate from reevaluating after DumpSave and Get