Hi Matt,

Thanks for your help.  Adjust by grid._id_offset did not work, but I can that what is happening is that all processors are trying to call _read_field_names using grid 1, when only processor 0 owns that grid.  I will look into why now, but if you have any intuition where to check next, that would be awesome.

Thanks,
Britton

On Mon, Jul 13, 2015 at 1:51 PM, Matthew Turk <matthewturk@gmail.com> wrote:
Hi Britton,

What looks suspicious to me is the way it's using grid.id.  This might
lead to an off-by-one error.  Can you try it with
grid.id-grid._id_offset and see if that clears it up?

On Mon, Jul 13, 2015 at 7:42 AM, Britton Smith <brittonsmith@gmail.com> wrote:
> Hi all,
>
> I've recently been trying to use yt's inline analysis functionality with
> Enzo and am having some difficultly getting it to work in parallel.  I am
> using the development tip of yt.  In serial, everything works fine, but in
> parallel, I get the following error:
> http://paste.yt-project.org/show/5694/
>
> It seems that the issue is that yt is not correctly identifying which grids
> are available on a given processory for the EnzoDatasetInMemory object.
> Does anyone have an idea of how to fix this?  Has anyone else seen this?
>
> For reference, my user_script is just this:
>
> import yt
> from yt.frontends.enzo.api import EnzoDatasetInMemory
>
> def main():
>     ds = EnzoDatasetInMemory()
>     ad = ds.all_data()
>     print ad.quantities.total_quantity("cell_mass")
>
> Thanks for any help,
>
> 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