This is a really important issue.  For those of you that have not tried it, the new unit system is amazing.  It can be slightly confusing at first, but the unit conversions work extremely well once the frontend has knowledge of the native unit system of the data.  The problem is really making sure that the native unit system is understood correctly.  There are cosmology comoving/proper frame issues as well as the fact that some systems define a velocity unit that is independent of the length and time units.  I think maybe the best way to do this is to have a very simple dataset for each frontend in which some basic quantities (velocities, densities, etc) are known and use them for unit testing.  I think a good sample dataset would be a uniform density/velocity grid, perhaps one with cosmology on and one off.  I'm sure this could be made for Enzo.  What about the rest of the codes?

Britton


On Thu, Dec 12, 2013 at 5:11 PM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi all,

There was some discussion in IRC of how to test out the new unit
refactor branch.  Not all of the frontends have been converted.

Here's how to pull it:

hg pull -r unitrefactor http://bitbucket.org/MatthewTurk/yt
hg up -r unitrefactor


Then, build as usual.  As a reminder, this is the primary yt repository now:

http://bitbucket.org/yt_analysis/yt

If you have that set as your "default", you can get back to the tip of
that repository like so:

hg up -r "remote(tip)"

If you want to make sure you're updating to a specific branch, swap
out "tip" for "yt" or "yt-3.0" (which will need to be in quotes, as -
is a special character in revsets.

-Matt
_______________________________________________
yt-dev mailing list
yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org