Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
2006
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*November
*December
*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 smc.vnet.net
  • Subject: [mg68818] Re: Preventing NIntegrate from reevaluating after DumpSave and Get
  • From: Peter Pein <petsie at dordos.net>
  • Date: Sat, 19 Aug 2006 00:41:44 -0400 (EDT)
  • References: <ec3ps8$2c2$1@smc.vnet.net>
  • Sender: owner-wri-mathgroup at wolfram.com

Chris Rodgers schrieb:
> Hi,
....
> 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.
> 

Hi Chris,

maybe it helps to do a

resultlist = resultlist /. _NIntegrate -> NotANumber

_before_ dumpsaving?

I have to admit, I didn't try it.

Peter


  • Prev by Date: NonlinearRegress with weight
  • Next by Date: Re: Preventing NIntegrate from reevaluating after DumpSave and Get
  • Previous by thread: Preventing NIntegrate from reevaluating after DumpSave and Get
  • Next by thread: Re: Preventing NIntegrate from reevaluating after DumpSave and Get