[yt-users] Reading in Potential Field

[Matthew Turk]

Hi Greg,

This thread can provide some insight:

http://lists.spacepope.org/pipermail/yt-users-spacepope.org/2011-July/001742.html

In short, yt does not provide a conversion because a conversion is
unknown to it.  We have taken the route of notifying the user of this.

If you want to provide a conversion factor for PotentialField, which
you know to be correct, I would encourage you not to go the yt route
and instead submit a patch to Enzo that writes out a
#CGSConversionFactor entry in the parameter file for PotentialField.
You can do this by going to the enzo source page:

http://bitbucket.org/enzo/enzo-dev

forking the repository, and adding the appropriate units in
WriteParameterFile, similar to how it is done for Density, and then
issuing a pull request with this change.  I'm sure it will be useful
for others!

-Matt

On Thu, Mar 1, 2012 at 5:17 PM,  <meecegre at msu.edu> wrote:
> Hi Everyone,
>
> I'm trying to use yt to calculate the spin parameter of a halo generated by
> Enzo. I have enzo writing out the potential using the -g flag, but when yt
> reads in the field, it isn't able to figure out the units or recognize it as
> a known field. Also, yt is keeping the potential data in code units, rather
> than converting to CGS. When I make a plot of the potential, the plot says
> that the units are unknown.
>
> When I load the dataset into yt, the relavant output is
> yt : [INFO     ] 2012-03-01 17:10:20,349 Adding unknown field PotentialField
> to list of fields
>
> I discussed this probelm with Brian O'Shea and Britton Smith. Not sure if
> anyone else has run into this issue.
>
> -- Greg Meece
>
> _______________________________________________
> yt-users mailing list
> yt-users at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
>