[Yt-dev] yt: moving pickled things

david collins antpuncher at gmail.com
Thu Mar 12 08:44:13 PDT 2009


Yeah, that'd be the way to do it.  Good thinking.



d.

On Wed, Mar 11, 2009 at 8:14 PM, Matthew Turk <matthewturk at gmail.com> wrote:
> I have had a thought, Dave.  These were all from your subclass of
> EnzoStaticOutput, right?  I think perhaps the right thing to do would
> be for your subclass to override _hash().  Of course the Orion outputs
> would need this as well.
>
> -Matt
>
> On Wed, Mar 11, 2009 at 3:07 PM, david collins <antpuncher at gmail.com> wrote:
>> Generalizing this kind of thing is no small task.  One important
>> question in the design is 'how general,' since trying to generalize
>> everything will cause you to re-create Lisp.
>>
>> d.
>>
>> On Wed, Mar 11, 2009 at 2:55 PM, Matthew Turk <matthewturk at gmail.com> wrote:
>>>> I like the "I'm going to change this: yes/no/don't warn me" design
>>>> pattern, so it's not bugging me, but it lets me know it's doing
>>>> something.
>>>
>>> That's a good point.  We need to retain in-the-background runability,
>>> so perhaps moving the old to a backup location and modifying the new
>>> one would be the best solution.
>>>
>>>> Is your goal to make this a general AMR analysis tool, or only for enzo?
>>>
>>> Thank you for the reminder.  You are 100% right, and in fact, the hash
>>> system right now does not even work for Orion.  I will think on this,
>>> because ... yeah.  It needs to be looked at and rethought, I think.
>>> Thank you.
>>> _______________________________________________
>>> Yt-dev mailing list
>>> Yt-dev at lists.spacepope.org
>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>
>> _______________________________________________
>> Yt-dev mailing list
>> Yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
> _______________________________________________
> Yt-dev mailing list
> Yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>



More information about the yt-dev mailing list