Saving variable value without lazy evaluation

2009-08-12 Thread Etienne Rivard
Hello Everyone, I have a problem related to saving the results I get with fipy. It's in some way related to my previous post entitled Using functions from the math or numpy modules. I'm working on a transient problem and I need to store the values of my variables at each time step. I

Re: Saving variable value without lazy evaluation

2009-08-12 Thread Daniel Wheeler
Hi Etienne, Answers below. On Wed, Aug 12, 2009 at 9:13 AM, Etienne Rivardetienne.riv...@uni-bayreuth.de wrote: Hello Everyone, I have a problem related to saving the results I get with fipy. It's in some way related to my previous post entitled Using functions from the math or numpy

Re: Saving variable value without lazy evaluation

2009-08-12 Thread Jonathan Guyer
On Aug 12, 2009, at 11:08 AM, Daniel Wheeler wrote: On Wed, Aug 12, 2009 at 9:13 AM, Etienne Rivardetienne.riv...@uni-bayreuth.de wrote: Then, at each time step, I would append the value of the variable to the list: d['T'].append(T.getValue()) The problem is that each entry of the list

Re: Saving variable value without lazy evaluation

2009-08-12 Thread Daniel Wheeler
On Wed, Aug 12, 2009 at 12:04 PM, Jonathan Guyergu...@nist.gov wrote: I think the issue is that T is a solution variable, not the result of an operation, so there's no evaluation to do. T.getValue() just returns T.value, which is a reference to an array. When the value of T changes (e.g. via

Re: Saving variable value without lazy evaluation

2009-08-12 Thread Jonathan Guyer
On Aug 12, 2009, at 12:18 PM, Daniel Wheeler wrote: In a sense that is how it should work. A true evaluation creates a new array as does a copy. Should getValue() be creating a copy if it doesn't do an evaluation? In general, I don't think that's desirable, but I agree that this case is