[yt-dev] RFC: Change in behavior for pf.current_time in Enzo frontend
Matthew Turk
matthewturk at gmail.com
Thu Nov 1 11:54:23 PDT 2012
Hi all,
Right now, amongst the confusing parameters available to an Enzo
frontend parameter file, we have:
pf["InitialTime"]
pf.current_time
These two are right now exactly the same. However, in most/all of the
other frontends, pf.current_time is (or should be) the actual time in
seconds. For Enzo this would mean multiplying by pf["seconds"].
Changing this could adversely affect many user scripts. However, not
changing it means we continue with this confusing behavior. For
instance, the TimeStamp callback is currently totally incorrect for
Enzo, but completely correct for FLASH.
Is this an important enough change to overcome the old behavior? Or
should this be deferred to 3.0?
[+-][01]
-Matt
More information about the yt-dev
mailing list