Hi guys,<br><br>I am not in favor of changing the width to something related to the halo radius. One of the main ideas behind the halo profiler projection routine is to get images of halos with a constant width so that they can all be compared against each other. I agree with Sam that if we change this to something not constant then these images become a lot let useful as an analysis tool.<br>
<br>I think just indicating that the image is going to be a certain size, or adding some sort of max image size argument is fine. Honestly, I think sometimes it's just fine to throw up your hands and say, "We warned you!" Maintaining usefulness is a lot more important to me than seeing everything just run without an error.<br>
<br>Britton<br><br><div class="gmail_quote">On Mon, Apr 11, 2011 at 8:47 PM, Sam Skillman <span dir="ltr"><<a href="mailto:samskillman@gmail.com">samskillman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Matt, Stephen,<div><br></div><div>I think there is then an issue of how does the user know what the size of the image is. Perhaps we should load up some hdf5 attributes that include things like length, pixel scale, etc. The nice thing about the old behavior was that you could easily figure out what the size was from looking at what the default was. And if you changed it, then you know from the start. <br>
<div><br></div><div>Thoughts? I would be in favor of this change assuming we add the hdf5 attributes.</div><div>Sam</div><div><div></div><div class="h5"><div><br><div class="gmail_quote">On Mon, Apr 11, 2011 at 8:34 PM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Sam,<br>
<br>
My feeling is that the HaloProfiler does a *lot*, and I would like to<br>
see it become feature parity with enzo_anyl. (A shame that we haven't<br>
yet fully recreated that enzo_anyl experience yet, with anything in<br>
yt...) As such, I think we should be positioning it as useful for a<br>
lot of domains.<br>
<br>
I guess the choice is really, do we want it to do something smart? Or<br>
do we want to let the code knowingly go down, and then tell the user<br>
"Sorry, but we warned you!" while shaking our heads and shrugging our<br>
shoulders.<br>
<br>
-Matt<br>
<div><div></div><div><br>
On Mon, Apr 11, 2011 at 8:20 PM, Sam Skillman <<a href="mailto:samskillman@gmail.com" target="_blank">samskillman@gmail.com</a>> wrote:<br>
> Hi<br>
> I would advocate, instead of changing the default, adding a message that<br>
> says: halo profiler projections will be NxN, and preferably have it print<br>
> somewhere just before it might die. That way when it does crash, it will be<br>
> simpler to figure out why.<br>
> Two Cents,<br>
> Sam<br>
> On Mon, Apr 11, 2011 at 8:11 PM, Stephen Skory <<a href="mailto:s@skory.us" target="_blank">s@skory.us</a>> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> I just spent some time trying to diagnose a segfault when the<br>
>> HaloProfiler was trying to make projections of the haloes. The problem<br>
>> was in making the FixedResolutionBuffer, the image it was trying to<br>
>> make was 16K by 16K, which cannot fit in any normal machine's memory.<br>
>> I think this is because I am looking at a zoom-in simulation of a<br>
>> smallish cosmological size, with high resolution in the region of<br>
>> interest. The default projection width in the HaloProfiler is 8 Mpc,<br>
>> so I had a big numerator and a small denominator.<br>
>><br>
>> What do we think about changing this default to some multiple of the<br>
>> halo maximum radius? I think any constant value will make problems.<br>
>><br>
>><br>
>> --<br>
>> Stephen Skory<br>
>> <a href="mailto:s@skory.us" target="_blank">s@skory.us</a><br>
>> <a href="http://stephenskory.com/" target="_blank">http://stephenskory.com/</a><br>
>> <a href="tel:510.621.3687" value="+15106213687" target="_blank">510.621.3687</a> (google voice)<br>
>> _______________________________________________<br>
>> Yt-dev mailing list<br>
>> <a href="mailto:Yt-dev@lists.spacepope.org" target="_blank">Yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
><br>
> _______________________________________________<br>
> Yt-dev mailing list<br>
> <a href="mailto:Yt-dev@lists.spacepope.org" target="_blank">Yt-dev@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
><br>
_______________________________________________<br>
Yt-dev mailing list<br>
<a href="mailto:Yt-dev@lists.spacepope.org" target="_blank">Yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<br>
Yt-dev mailing list<br>
<a href="mailto:Yt-dev@lists.spacepope.org">Yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br>