Hi John,<div><br></div><div>I just verified that it breaks on my even simpler data with the MosaicFisheyeCamera with no_ghost=False (getting the vertex centered data). However, it does not fail when doing a normal rendering. I'm out of steam for tonight, but hopefully we'll track this down right away. If you want to do stuff for now, you can do hg backout <code style="border-style:initial;border-color:initial;font-size:12px;color:rgb(43,84,125);text-align:left;margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px;border-top-width:0px;border-right-width:0px;border-bottom-width:0px;border-left-width:0px;border-style:initial;border-color:initial;font-style:inherit;font-family:'Bitstream Vera Sans Mono','DejaVu Sans Mono',Monaco,monospace;vertical-align:baseline;line-height:12px;border-style:initial;border-color:initial;background-image:initial;background-color:initial"><a class="execute" href="https://bitbucket.org/samskillman/yt-mosaicfisheye/changeset/e699c92663c2" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px;border-top-width:0px;border-right-width:0px;border-bottom-width:0px;border-left-width:0px;border-style:initial;border-color:initial;font-size:12px;font-family:Helvetica,Arial,sans-serif;vertical-align:baseline;color:rgb(43,84,125);line-height:28px;text-align:left;background-color:rgb(255,255,255)">e699c92663c2</a></code> and stay on the latest tip without that ghost zone change. I'm sure this'll be a high priority to fix.</div>
<div><br></div><div>Best,</div><div>Sam</div><div><br><div class="gmail_quote">On Tue, Jan 17, 2012 at 9:24 PM, John Wise <span dir="ltr"><<a href="mailto:jwise@physics.gatech.edu">jwise@physics.gatech.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I forgot to include the debugging output from the crash.<br>
<br>
yt : [INFO ] <a href="tel:2012-01-17%2023" value="+12012011723">2012-01-17 23</a>:16:58,301 Rendering fisheye of 100^2<br>
vz = nan nan -26.912 nan, dv = 0.604703, ds = 14 6 16, dp = 0.911364 0.9 0.395297<br>
OINDEX(0,0,0) = nan, OINDEX(0,0,1) = nan<br>
vz = nan nan -26.9203 nan, dv = 0.414264, ds = 14 6 16, dp = 0.934091 -0.1 0.585736<br>
OINDEX(0,0,0) = nan, OINDEX(0,0,1) = nan<br>
Segmentation fault<br>
<div class="HOEnZb"><div class="h5"><br>
On 17 Jan 2012, at 23:21, John Wise wrote:<br>
<br>
> Hi,<br>
><br>
> I tried to make some volume renderings with the latest tip (f7e39b91cc6b), and it was crashing because there were NaNs in the data when offset_interpolate was called. I could make it crash in a small fisheye rendering (100x100) of a 128^3 AMR simulation. I've uploaded the dataset (538MB) and script to<br>
><br>
> <a href="http://www.physics.gatech.edu/~jw254/scpics/RD0009.tar" target="_blank">http://www.physics.gatech.edu/~jw254/scpics/RD0009.tar</a><br>
> <a href="http://paste.yt-project.org/show/2042/" target="_blank">http://paste.yt-project.org/show/2042/</a><br>
><br>
> I uploaded a diff of my debugging statement to here.<br>
><br>
> <a href="http://paste.yt-project.org/show/2041/" target="_blank">http://paste.yt-project.org/show/2041/</a><br>
><br>
> When I reverted back to the changeset (1558cb36d03b) before the ghost zone update, this problem when away. Could someone look at this or tell me where to search for the bug?<br>
><br>
> Thanks!<br>
> John<br>
><br>
> On 17 Jan 2012, at 17:29, Matthew Turk wrote:<br>
><br>
>> Hi Britton,<br>
>><br>
>> Looks great. Thanks.<br>
>><br>
>> As a sidenote, I added the functionality to auto-detect which fields<br>
>> are needed; supplying them in ValidateSpatial should be faster,<br>
>> though. Thanks!<br>
>><br>
>> -Matt<br>
>><br>
>> On Tue, Jan 17, 2012 at 5:22 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>> wrote:<br>
>>> Hi everyone,<br>
>>><br>
>>> I'm finally following up on this thread. I just submitted a pull request<br>
>>> for the docs that includes some documentation of how to create fields that<br>
>>> use ghost zones. Some of it was a little tricky to explain, so let me know<br>
>>> if the wording can be improved.<br>
>>><br>
>>> Britton<br>
>>><br>
>>><br>
>>> On Wed, Jan 4, 2012 at 2:03 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>> wrote:<br>
>>>><br>
>>>> Hi Britton,<br>
>>>><br>
>>>> On Wed, Jan 4, 2012 at 1:32 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>><br>
>>>> wrote:<br>
>>>>> Hi Matt,<br>
>>>>><br>
>>>>> I'm not sure I understand the change that you're talking about, but it<br>
>>>>> seems<br>
>>>>> that they were auto-detected in the past, since the example without them<br>
>>>>> there used to work. I'm in favor of returning to that if possible.<br>
>>>>> Regardless, I think it would be worthwhile to add something to the<br>
>>>>> derived<br>
>>>>> fields documentation discussing this. I could add that if we wanted it,<br>
>>>>> but<br>
>>>>> it will be good to have it reviewed, since I'm not very familiar with<br>
>>>>> how it<br>
>>>>> works.<br>
>>>><br>
>>>> I think the best solution would be to have it simply auto-detect the<br>
>>>> fields necessary, rather than mandating they be specified (which may<br>
>>>> not always give the correct results.) I'll implement this tomorrow<br>
>>>> morning.<br>
>>>><br>
>>>> After some digging, it seems to me that this situation arose because<br>
>>>> we fixed a bug which had silently allowed this to occur, related to<br>
>>>> checking for field parameters in fields requiring ghost zones.<br>
>>>><br>
>>>> -Matt<br>
>>>><br>
>>>>><br>
>>>>> Britton<br>
>>>>><br>
>>>>><br>
>>>>> On Wed, Jan 4, 2012 at 1:26 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>>>>> wrote:<br>
>>>>>><br>
>>>>>> Hi Britton,<br>
>>>>>><br>
>>>>>> It may not be documented, but I think we can actually auto-detect<br>
>>>>>> them; this would add on a list of lists of strings to the hierarchy,<br>
>>>>>> but I think that is manageable. Would this be worthwhile?<br>
>>>>>><br>
>>>>>> -Matt<br>
>>>>>><br>
>>>>>> On Wed, Jan 4, 2012 at 1:24 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>><br>
>>>>>> wrote:<br>
>>>>>>> Hi Sam,<br>
>>>>>>><br>
>>>>>>> That fixed it, thanks! I actually encountered this problem while<br>
>>>>>>> working on<br>
>>>>>>> my own derived field that used ghost zones and was using<br>
>>>>>>> VorticitySquared as<br>
>>>>>>> my example for how to do it. I think in the past it was not required<br>
>>>>>>> to<br>
>>>>>>> list the fields with ValidateSpatial, which is why it was working as<br>
>>>>>>> is<br>
>>>>>>> in<br>
>>>>>>> older versions. I wasn't able to find documentation on how to make<br>
>>>>>>> fields<br>
>>>>>>> that use ghost_zones. If it's in there and I just missed it, could<br>
>>>>>>> someone<br>
>>>>>>> point me toward it? If not, I could add something to the Creating<br>
>>>>>>> Derived<br>
>>>>>>> Fields section.<br>
>>>>>>><br>
>>>>>>> Britton<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> On Wed, Jan 4, 2012 at 11:46 AM, Sam Skillman <<a href="mailto:samskillman@gmail.com">samskillman@gmail.com</a>><br>
>>>>>>> wrote:<br>
>>>>>>>><br>
>>>>>>>> Hey Britton,<br>
>>>>>>>><br>
>>>>>>>> It looks like VorticitySquared wasn't specifying the necessary<br>
>>>>>>>> fields<br>
>>>>>>>> (x,y,z velocity) in the definition. I will push a change<br>
>>>>>>>> momentarily<br>
>>>>>>>> after<br>
>>>>>>>> I look around at any other ghost zone requiring fields to make sure<br>
>>>>>>>> they<br>
>>>>>>>> work. DivV, for example, does the right thing.<br>
>>>>>>>><br>
>>>>>>>> Sam<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> On Wed, Jan 4, 2012 at 9:32 AM, Britton Smith<br>
>>>>>>>> <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>><br>
>>>>>>>> wrote:<br>
>>>>>>>>><br>
>>>>>>>>> Hi everyone,<br>
>>>>>>>>><br>
>>>>>>>>> I'm having a problem using fields that use ghost zones. The<br>
>>>>>>>>> following<br>
>>>>>>>>> simple script:<br>
>>>>>>>>> <a href="http://paste.yt-project.org/show/2010/" target="_blank">http://paste.yt-project.org/show/2010/</a><br>
>>>>>>>>><br>
>>>>>>>>> gives this error:<br>
>>>>>>>>> <a href="http://paste.yt-project.org/show/bOikDPScBBtDiUGvH11X/" target="_blank">http://paste.yt-project.org/show/bOikDPScBBtDiUGvH11X/</a><br>
>>>>>>>>><br>
>>>>>>>>> I am working from the tip, but I get the same behavior from yt/2.3.<br>
>>>>>>>>> In<br>
>>>>>>>>> yt/2.2, everything is working. I am working now to narrow that<br>
>>>>>>>>> range<br>
>>>>>>>>> down a<br>
>>>>>>>>> bit, but does anyone have an idea?<br>
>>>>>>>>><br>
>>>>>>>>> Britton<br>
<br>
_______________________________________________<br>
yt-users mailing list<br>
<a href="mailto:yt-users@lists.spacepope.org">yt-users@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org</a><br>
</div></div></blockquote></div><br></div>