yt-3.0 question: find_field_value_at_point()
Hi there, I've been working with yt-3.0 and Ramses over the past few days. One thing that seems to not be working (or rather, to not be existing) is pf.h.find_field_value_at_point() I'm not sure if this is a problem or a design choice for 3.0- if the latter, is there a new way to do the same thing? best, Nick
Hi Nick, There's actually a current issue on the issue tracker for this: https://bitbucket.org/yt_analysis/yt/issue/499/missing-hierarchy-functions They should be pretty simple to port over to 3.0, but I'm not sure when I'll be able to get to it. Perhaps someone else more familiar with 3.0 could give it a shot. Sam On Thu, Apr 4, 2013 at 8:30 AM, nick moeckel <nickolas1@gmail.com> wrote:
Hi there,
I've been working with yt-3.0 and Ramses over the past few days. One thing that seems to not be working (or rather, to not be existing) is pf.h.find_field_value_at_point()
I'm not sure if this is a problem or a design choice for 3.0- if the latter, is there a new way to do the same thing?
best, Nick
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
Hi Nick, Sam is correct that porting over find_field_value_at_point should be pretty simple to get working, here's how I would do it: - use pf.h.find_points() to find the most-refined grid at your point(s). - use that grid's size (left edge/right edge/size) to figure out the index of the cell in the grid that contains your point(s), which is straightforward algebra. - use that index to select out the values from the field arrays (grid[field][index]) This is basically how find_field_value_at_point works and you can look at that in 2.x as a guide. If you get it working, you are encouraged to issue a pull request for it! Good luck! On Thu, Apr 4, 2013 at 8:45 AM, Sam Skillman <samskillman@gmail.com> wrote:
Hi Nick,
There's actually a current issue on the issue tracker for this: https://bitbucket.org/yt_analysis/yt/issue/499/missing-hierarchy-functions
They should be pretty simple to port over to 3.0, but I'm not sure when I'll be able to get to it. Perhaps someone else more familiar with 3.0 could give it a shot.
Sam
On Thu, Apr 4, 2013 at 8:30 AM, nick moeckel <nickolas1@gmail.com> wrote:
Hi there,
I've been working with yt-3.0 and Ramses over the past few days. One thing that seems to not be working (or rather, to not be existing) is pf.h.find_field_value_at_point()
I'm not sure if this is a problem or a design choice for 3.0- if the latter, is there a new way to do the same thing?
best, Nick
_______________________________________________ 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
-- Stephen Skory s@skory.us http://stephenskory.com/ 510.621.3687 (google voice)
Good deal, thanks for the guidance. Nick On Apr 4, 2013 4:51 PM, "Stephen Skory" <s@skory.us> wrote:
Hi Nick,
Sam is correct that porting over find_field_value_at_point should be pretty simple to get working, here's how I would do it:
- use pf.h.find_points() to find the most-refined grid at your point(s). - use that grid's size (left edge/right edge/size) to figure out the index of the cell in the grid that contains your point(s), which is straightforward algebra. - use that index to select out the values from the field arrays (grid[field][index])
This is basically how find_field_value_at_point works and you can look at that in 2.x as a guide. If you get it working, you are encouraged to issue a pull request for it!
Good luck!
On Thu, Apr 4, 2013 at 8:45 AM, Sam Skillman <samskillman@gmail.com> wrote:
Hi Nick,
There's actually a current issue on the issue tracker for this:
https://bitbucket.org/yt_analysis/yt/issue/499/missing-hierarchy-functions
They should be pretty simple to port over to 3.0, but I'm not sure when
be able to get to it. Perhaps someone else more familiar with 3.0 could give it a shot.
Sam
On Thu, Apr 4, 2013 at 8:30 AM, nick moeckel <nickolas1@gmail.com> wrote:
Hi there,
I've been working with yt-3.0 and Ramses over the past few days. One
I'll thing
that seems to not be working (or rather, to not be existing) is pf.h.find_field_value_at_point()
I'm not sure if this is a problem or a design choice for 3.0- if the latter, is there a new way to do the same thing?
best, Nick
_______________________________________________ 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
-- Stephen Skory s@skory.us http://stephenskory.com/ 510.621.3687 (google voice) _______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
participants (3)
-
nick moeckel -
Sam Skillman -
Stephen Skory