[Yt-dev] new comm problem

Sam Skillman samskillman at gmail.com
Fri Oct 21 07:49:32 PDT 2011


Hi Stephen,

It looks like the other derived camera classes that were overwriting
__init__ didn't have the ParallelAnalysisInterface initialization, which has
now been fixed in:
https://bitbucket.org/yt_analysis/yt/changeset/510d1815e9af/

Basically you have to send "self" to the PAI __init__() function, as you'll
see in the diff on that changeset.

Hope that helps.

Sam

On Fri, Oct 21, 2011 at 6:56 AM, Stephen Skory <s at skory.us> wrote:

> Matt,
>
> > That is correct; PAI's initializer must now be called.  Is there a
> > subclass that's missing that?  The PAI initializer grabs the
> > communicator on the top of the stack.  Have you seen issues with
> > _grids or _distributed, that aren't being hit by the test suite?  The
> > small data is now passing, and it should have coverage of DQ's,
> > profiles (1 and 2D), PHOP and so on.
>
> I'm seeing a crash in camera.py where trying to use "self.comm.rank"
> is dying because "self.comm" is None. Can you point me to an example
> of where the initializer is correctly called (as much for my own
> development as a human being as for this specific problem)?
>
>
> --
> Stephen Skory
> s at skory.us
> http://stephenskory.com/
> 510.621.3687 (google voice)
> _______________________________________________
> Yt-dev mailing list
> Yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20111021/33e43048/attachment.html>


More information about the yt-dev mailing list