ProjectionTransferFunction()
Hi all I'm not having any success with off-axis projections using the pf.h.camera() with AMRKDTree and ProjectionTransferFunction(). cam.snapshot() returns an all-zeros array, even in situations where ColorTransferFunction() produces great images. This script (based on the first part of amrkdtree_downsampling.py) demonstrates the problem: http://paste.yt-project.org/show/3072/ Any ideas what's going wrong? Maybe something to do with preventing the log'ing of the field, which I attempted to do with "pf.field_info['Density'].take_log=False"? Thanks for you help! Mike -- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 B-116 Hearst Field Annex # 3411 * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************
Hi Mike, On Tue, Jan 22, 2013 at 4:25 PM, Michael Kuhlen <mqk@astro.berkeley.edu> wrote:
Hi all
I'm not having any success with off-axis projections using the pf.h.camera() with AMRKDTree and ProjectionTransferFunction(). cam.snapshot() returns an all-zeros array, even in situations where ColorTransferFunction() produces great images.
This script (based on the first part of amrkdtree_downsampling.py) demonstrates the problem: http://paste.yt-project.org/show/3072/
Any ideas what's going wrong? Maybe something to do with preventing the log'ing of the field, which I attempted to do with "pf.field_info['Density'].take_log=False"?
Last Summer, during the course of the threading of the volume renderer, the camera class was split up into a couple different things. You should be able to get exactly what you're looking for by using projection_camera instead of camera. The function off_axis_projection will also work for this purpose. Something I think could be improved is to make the off-axis projection functionality much more distinct from the volume rendering; this would allow, among other things, the ability to specify a data object rather than a kD-tree volume for the off axis projection. I think this would be a big improvement, since unlike the volume rendering, off-axis projections are unordered and can thus be trivially masked. Cameron is working on a YTEP to the effect of improving the volume rendering API, and this should probably be a part of that. -Matt
Thanks for you help!
Mike
-- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 B-116 Hearst Field Annex # 3411 * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
There's also OffAxisProjectionPlot, which wraps off_axis_projection, presenting an interface that is identical to the other plot window plotting routines. It would be great if there were a true off axis projection data object, it would be much easier to integrate OffAxisProjectionPlot with the other plot window routines. On Jan 22, 2013, at 1:55 PM, Matthew Turk wrote:
Hi Mike,
On Tue, Jan 22, 2013 at 4:25 PM, Michael Kuhlen <mqk@astro.berkeley.edu> wrote:
Hi all
I'm not having any success with off-axis projections using the pf.h.camera() with AMRKDTree and ProjectionTransferFunction(). cam.snapshot() returns an all-zeros array, even in situations where ColorTransferFunction() produces great images.
This script (based on the first part of amrkdtree_downsampling.py) demonstrates the problem: http://paste.yt-project.org/show/3072/
Any ideas what's going wrong? Maybe something to do with preventing the log'ing of the field, which I attempted to do with "pf.field_info['Density'].take_log=False"?
Last Summer, during the course of the threading of the volume renderer, the camera class was split up into a couple different things. You should be able to get exactly what you're looking for by using projection_camera instead of camera. The function off_axis_projection will also work for this purpose.
Something I think could be improved is to make the off-axis projection functionality much more distinct from the volume rendering; this would allow, among other things, the ability to specify a data object rather than a kD-tree volume for the off axis projection. I think this would be a big improvement, since unlike the volume rendering, off-axis projections are unordered and can thus be trivially masked. Cameron is working on a YTEP to the effect of improving the volume rendering API, and this should probably be a part of that.
-Matt
Thanks for you help!
Mike
-- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 B-116 Hearst Field Annex # 3411 * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
OK, it's good to know about pf.h.projection_camera. That works for me. I knew about off_axis_projection as well, but I had been using camera, since it allowed me to do 3 projections simultaneously (as long as they were unweighted). This functionality seems to have disappeared from ProjectionCamera, which only accepts a single field, not a list of fields. That's too bad, but definitely not a show stopper. Thanks for the help. Mike On Tue, Jan 22, 2013 at 1:58 PM, Nathan Goldbaum <nathan12343@gmail.com>wrote:
There's also OffAxisProjectionPlot, which wraps off_axis_projection, presenting an interface that is identical to the other plot window plotting routines.
It would be great if there were a true off axis projection data object, it would be much easier to integrate OffAxisProjectionPlot with the other plot window routines.
On Jan 22, 2013, at 1:55 PM, Matthew Turk wrote:
Hi Mike,
Hi all
I'm not having any success with off-axis projections using the
with AMRKDTree and ProjectionTransferFunction(). cam.snapshot() returns an all-zeros array, even in situations where ColorTransferFunction()
On Tue, Jan 22, 2013 at 4:25 PM, Michael Kuhlen <mqk@astro.berkeley.edu> wrote: pf.h.camera() produces
great images.
This script (based on the first part of amrkdtree_downsampling.py) demonstrates the problem: http://paste.yt-project.org/show/3072/
Any ideas what's going wrong? Maybe something to do with preventing the log'ing of the field, which I attempted to do with "pf.field_info['Density'].take_log=False"?
Last Summer, during the course of the threading of the volume renderer, the camera class was split up into a couple different things. You should be able to get exactly what you're looking for by using projection_camera instead of camera. The function off_axis_projection will also work for this purpose.
Something I think could be improved is to make the off-axis projection functionality much more distinct from the volume rendering; this would allow, among other things, the ability to specify a data object rather than a kD-tree volume for the off axis projection. I think this would be a big improvement, since unlike the volume rendering, off-axis projections are unordered and can thus be trivially masked. Cameron is working on a YTEP to the effect of improving the volume rendering API, and this should probably be a part of that.
-Matt
Thanks for you help!
Mike
-- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 B-116 Hearst Field Annex # 3411 * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- ********************************************************************* * * * Dr. Michael Kuhlen Theoretical Astrophysics Center * * email: mqk@astro.berkeley.edu UC Berkeley * * cell phone: (831) 588-1468 B-116 Hearst Field Annex # 3411 * * skype username: mikekuhlen Berkeley, CA 94720 * * * *********************************************************************
participants (3)
-
Matthew Turk -
Michael Kuhlen -
Nathan Goldbaum