Hi Sam,

That fixed it, thanks!  I actually encountered this problem while working on my own derived field that used ghost zones and was using VorticitySquared as my example for how to do it.  I think in the past it was not required to list the fields with ValidateSpatial, which is why it was working as is in older versions.  I wasn't able to find documentation on how to make fields that use ghost_zones.  If it's in there and I just missed it, could someone point me toward it?  If not, I could add something to the Creating Derived Fields section.

Britton

On Wed, Jan 4, 2012 at 11:46 AM, Sam Skillman <samskillman@gmail.com> wrote:
Hey Britton,

It looks like VorticitySquared wasn't specifying the necessary fields (x,y,z velocity) in the definition.  I will push a change momentarily after I look around at any other ghost zone requiring fields to make sure they work.  DivV, for example, does the right thing.

Sam


On Wed, Jan 4, 2012 at 9:32 AM, Britton Smith <brittonsmith@gmail.com> wrote:
Hi everyone,

I'm having a problem using fields that use ghost zones.  The following simple script:
http://paste.yt-project.org/show/2010/

gives this error:
http://paste.yt-project.org/show/bOikDPScBBtDiUGvH11X/

I am working from the tip, but I get the same behavior from yt/2.3.  In yt/2.2, everything is working.  I am working now to narrow that range down a bit, but does anyone have an idea?

Britton

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



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