Is there a simple explanation for why they can’t be treated as normal fields and what that refactoring would look like? SlicePlot suffers from the same issue for the same reason (it’s getting dropped at the PlotWindow stage). Douglas Rudd Scientific Computing Consultant Research Computing Center drudd@uchicago.edu<mailto:drudd@uchicago.edu> On Nov 7, 2014, at 12:58 PM, Nathan Goldbaum <nathan12343@gmail.com<mailto:nathan12343@gmail.com>> wrote: This is due to implementation details in the PlotWindow class. It would take some refactoring to allow plotting these fields. Patches welcome :) On Fri, Nov 7, 2014 at 10:56 AM Matthew Turk <matthewturk@gmail.com<mailto:matthewturk@gmail.com>> wrote: Yes, this is frustrating, and I have been bitten by it. On Fri Nov 07 2014 at 12:54:32 PM Douglas Rudd <issues-reply@bitbucket.org<mailto:issues-reply@bitbucket.org>> wrote: New issue 937: to_pw silently drops some fields https://bitbucket.org/yt_analysis/yt/issue/937/to_pw-silently-drops-some-fie... Douglas Rudd: to_pw silently drops fields from frb._exclude_fields and _key_fields without notifying the user. ``` #!python
ds = yt.load("outputs/sedov_000960.art") fields = ["density","temperature","dx"] plot = ds.slice(2, ds.domain_center[2]).to_pw(fields) print plot.fields ['density', 'temperature']
In this case ('index', 'dx') is in both exclusion lists. Any reason I can't plot a slice of my resolution?
_______________________________________________
yt-dev mailing list
yt-dev@lists.spacepope.org<mailto:yt-dev@lists.spacepope.org>
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________
yt-dev mailing list
yt-dev@lists.spacepope.org<mailto:yt-dev@lists.spacepope.org>
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
_______________________________________________
yt-dev mailing list
yt-dev@lists.spacepope.org<mailto:yt-dev@lists.spacepope.org>
http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org