Hi
I would advocate, instead of changing the default, adding a message that says: halo profiler projections will be NxN, and preferably have it print somewhere just before it might die.  That way when it does crash, it will be simpler to figure out why.  
Two Cents,
Sam

On Mon, Apr 11, 2011 at 8:11 PM, Stephen Skory <s@skory.us> wrote:
Hi all,

I just spent some time trying to diagnose a segfault when the
HaloProfiler was trying to make projections of the haloes. The problem
was in making the FixedResolutionBuffer, the image it was trying to
make was 16K by 16K, which cannot fit in any normal machine's memory.
I think this is because I am looking at a zoom-in simulation of a
smallish cosmological size, with high resolution in the region of
interest. The default projection width in the HaloProfiler is 8 Mpc,
so I had a big numerator and a small denominator.

What do we think about changing this default to some multiple of the
halo maximum radius? I think any constant value will make problems.


--
Stephen Skory
s@skory.us
http://stephenskory.com/
510.621.3687 (google voice)
_______________________________________________
Yt-dev mailing list
Yt-dev@lists.spacepope.org
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org