[Yt-dev] Volume rendering with current (3628:da3894bf42a5) change set

[Matthew Turk]

Hi Chris,

Sorry for the brief reply (I'm actually on vacation while moving,
stealing a bit of time at the computer.)

On Thu, Dec 30, 2010 at 1:44 PM, Chris Malone <chris.m.malone at gmail.com> wrote:
> Hi Matt,
>
> Thanks for the feedback.
>
>> That's a bit odd!  My guess is that something's up with the center and
>> domain left edge info.  Can you run with --detailed or
>> --paste-detailed, and it should give info about the center and LE
>> variables.  Alternately, you can run with:
>>
>> python2.6 -m pdb some_script.py
>>
>> and print LE, LE.shape, self.back_center, self.back_center.shape.  It
>> seems likely to me it's something like one is shaped (3,1) and the
>> other (1,3) or (3,) or something.
>
> After using the debugger as you suggested and looking more closely it seems
> that LE is still an empty list because self.bricks = None even after a call
> to self.partition_grids().  The latter is not working properly because
> self._brick_collection.source._grids is an empty ndarray.  For example, I
> get the following DEBUG message before the fatal error:
>
> yt         DEBUG      2010-12-30 16:40:49,932 Preloading ['Density'] from 0
> grids
>
> I now need to track down why _grids is not being filled appropriately; all
> the other grid-type-lists I have found are properly filled.

My guess is actually the width argument -- you're setting it to 1.0,
and the center to 0.5, 0.5, 0.5.  Can you try with:

W = pf['unitary']
c = 0.5*(pf.domain_right_edge + pf.domain_left_edge)

which should grab all the bricks?

>
>> Do you want to push your Maestro changes so that we can
>> take a look at them, see how they are implemented?
>
> I have some clean-up to do on the code, but I will certainly push it once I
> have things a bit better organized.

Awesome!

-Matt

>
> Chris
>>
>> -Matt
>>
>> On Wed, Dec 29, 2010 at 4:19 PM, Chris Malone <chris.m.malone at gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > As previously mentioned, I'm working in my spare time to add support for
>> > the
>> > Maestro code to yt.  I am able to read in the data, make slices of
>> > various
>> > variables, and save the resulting plots.  I tried, however, to follow
>> > the
>> > cookbook recipe for volume rendering and I keep getting an error while
>> > attempting to ray_cast.
>> >
>> > Here is the script I use: http://paste.enzotools.org/show/1470/
>> >
>> > and here is the traceback:
>> > http://paste.enzotools.org/show/Jn7X2pBPkUD0yhhLwrVv/
>> >
>> > I'm not sure if this is an issue with the way I have implemented Maestro
>> > support or if there is a bug in the visualization.  Could someone please
>> > try
>> > my script with their own parameter file to at least verify there is no
>> > bug
>> > in ray_cast?
>> >
>> > Thanks,
>> >
>> > Chris
>> >
>> > _______________________________________________
>> > Yt-dev mailing list
>> > Yt-dev at lists.spacepope.org
>> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>> >
>> >
>> _______________________________________________
>> Yt-dev mailing list
>> Yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
> _______________________________________________
> Yt-dev mailing list
> Yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>