We'd be happy to help. It'd be great if you could help and do some detective work, too. :) Specifically, maybe you can figure out which field is being profiled at the time of the crash, maybe submit the parameter file so we can take a look at it, and then see what it guesses the limits are. Maybe you could try generating an AMRSphere yourself with the center/radius it's using (this should be visible inside the HOP output file) and see if the data being fed into the profiler (not the halo profiler, but Binned1DProfile) is meaningful or not -- unfortunately because the dataset is so big, and since neither of us have run into this before, we're going to have to rely on a bit of your sleuthing.
Typically -- in my experience -- the specific problem you are bringing up is from a data source not having enough data points inside the binning range. I've made up a patch that should make this more explicit. Regardless, this is a flaw that needs to be addressed in yt. The patch below doesn't give *much* information, but it will tell you if what we're seeing is what I think it is.
On Sun, Mar 22, 2009 at 9:54 PM, Stephen Skory email@example.com wrote:
Hi Britton & Matt,
first of all, thanks very much for working on the parallel halo profiler! I appreciate it very much.
I am having some trouble running it on a L7 dataset. Specifically, I am getting the error below at all processor counts (this is a -np 1 run, rev 1226):
It's getting late so I'll take another whack at it tomorrow morning. I'm sending it out on the chance that one of you might have some insight.
firstname.lastname@example.org o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_(_)_______________
Yt-dev mailing list Ytemail@example.com http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org