at some point in the future I think I am going to need to calculate gas surface density of halos, and I have a few questions. First, it appears to me that the Halo Profiler cannot do this currently, am I correct? If I am correct, does anyone have code out there that they're willing to give me that is trusted, that I can work into yt? I am certainly capable of writing new code myself, but sharing will save you and me and everyone lots of time. I will give you due credit, of course!
sskory(a)physics.ucsd.edu o__ Stephen Skory
http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student
I am getting a hang when I run the lightcone tools on ranger, and no
debug info is coming out at the hang. this is in the hg version
(current) of yt.
The routines I'm running is called test_vel_mask.py, which is creating
a lightcone with a halo map that includes the bulk line of sight halo
velocity. It includes a slight modification of HaloMask.py to
include velocities. However, I removed my changes, and ran again with
the same hang. The routine below is copied nearly directly from the yt
docs, with minor changes.
Routine is attached as test_wo_vel.py
Hang occurs with text line:
yt.lagos INFO 2010-04-05 12:06:15,657 Writing filtered halo
list to /scratch/00688/tg458377/box_size_study/50Mpc_1024/run_12_cl_5D/
traceback is attached as test_vel_traceback.out
Thanks for any help...
Google Voice: (774) 469-0278
Nicholas Earl reported a problem with his simulations -- 400x200x200
-- that resulted in a breakage in the smoothed covering grid, used for
ghost zone and vertex centered data generation. In r1679 I applied a
fix for this to the yt trunk, changing the rounding method for
calculation of the extents of a covering grid from "ceil" to "rint".
I investigated his data and what was happening was simply a precision
bug causing the ceil to go over, where I believed when I wrote the
code it would always be epsilon below the desired value.
This should only affect generation of ghost zones for L=0 grids; if
any of you happen to run volume renderings that die on getting vertex
centered data from L=0 grids, please let me know immediately and we'll
try to fix it in a more robust fashion.
I need some help with the ghost zone generation. Right now it's too
slow, because it performs a cascading interpolation from the lowest
levels to the highest levels, filling in available cells, then
interpolating to the next level and repeating the process. Looking
over the Enzo source code, I think we can do better: I think we should
be able to replicate the Enzo logic much more closely, which only
implicitly requires cascading interpolation, by checking parents and
sibling grids. The issue of Subling grids I think we will also need
to address. The current code is in AMRIntSmoothedCoveringGridBase.
It's not that pretty.
Does anybody have any ideas on whether or not we can do this better
than it currently is done? Getting vertex centered data requires the
ghost zones, and right now getting ghost zones is *easily* the most
time consuming step of the volume rendering for many datasets. Dave,
John, I know you've both dealt with this issue but if anybody has any
ideas, they'd be greatly appreciated!