Hi Dave, The specification for the projection node naming is: /Projections/[axis]/[fieldname]_[weight] Unless the field being stored *is* the weighting field (which, in retrospect, is not really necessary) in which case it is: /Projections/[axis]/weight_field_[fieldname] So yes, it does distinguish. For instance, here's the list of nodes for one of my test datasets: /Projections/0/Density_Density Dataset {37267} /Projections/0/Density_None Dataset {37267} /Projections/0/pdx Dataset {37267} /Projections/0/pdy Dataset {37267} /Projections/0/px Dataset {37267} /Projections/0/py Dataset {37267} /Projections/0/weight_field_Density Dataset {37267} So it has stored both weighted and unweighted Density projections, along with the Density field for weighting purposes. Looks like I could do some pruning of what gets stored. -Matt On Thu, Jun 18, 2009 at 2:22 PM, david collins<antpuncher@gmail.com> wrote:

Hi--

When yt caches a projection, it saves the projection in filename.yt. Does it distinguish between different projections with different weights?

d. _______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org