Ortho Slice AMR issue
Hello, I am having an issue with a FLASH simulation and AMR, using the OrthoSlice method. I am aware of the note at https://yt-project.org/doc/reference/api/yt.data_objects.selection_data_cont... but when I try to sort on the "t" field it is not found. Is that a derived field that should be constructed when yt loads the file, or is it the responsibility of the FLASH simulation to write the "t" field to file? Jupyter notebook: http://paste.yt-project.org/show/243/ Input file: http://use.yt/upload/cfef968c Thank you, -Stephen -- Stephen Coleman *Research Scientist* | RadiaSoft 720-502-3928 x 722 | coleman@radiasoft.net radiasoft.net | sirepo.com
Hi Stephen,
Good question -- so the "t" field specifically is generated when you
construct a ray, which would be either an OrthoRay or a Ray object. I
don't believe it will exist with a Slice.
On Fri, Jun 19, 2020 at 1:35 PM Stephen Coleman
Hello, I am having an issue with a FLASH simulation and AMR, using the OrthoSlice method. I am aware of the note at https://yt-project.org/doc/reference/api/yt.data_objects.selection_data_cont...
but when I try to sort on the "t" field it is not found. Is that a derived field that should be constructed when yt loads the file, or is it the responsibility of the FLASH simulation to write the "t" field to file?
Jupyter notebook: http://paste.yt-project.org/show/243/
Input file: http://use.yt/upload/cfef968c
Thank you, -Stephen
--
Stephen Coleman
Research Scientist | RadiaSoft
720-502-3928 x 722 | coleman@radiasoft.net
radiasoft.net | sirepo.com
_______________________________________________ yt-users mailing list -- yt-users@python.org To unsubscribe send an email to yt-users-leave@python.org https://mail.python.org/mailman3/lists/yt-users.python.org/ Member address: matthewturk@gmail.com
Hi Matthew, That's my mistake in the description in the email, but if you look at the code I am indeed seeing this problem while using ortho_ray.
Hi Stephen,
Oops, you're right! I'm sorry.
I'm reading the code right now, and it looks to me like the *orthoray*
specifically doesn't have a t field after all, and should already be
ordered. I'm also finding that it looks like it will have some odd
behaviors in non-Cartesian coordinates, which I will look into as
well. But it should just "be" ordered by the direction already.
On Fri, Jun 19, 2020 at 3:59 PM Stephen Coleman
Hi Matthew, That's my mistake in the description in the email, but if you look at the code I am indeed seeing this problem while using ortho_ray. _______________________________________________ yt-users mailing list -- yt-users@python.org To unsubscribe send an email to yt-users-leave@python.org https://mail.python.org/mailman3/lists/yt-users.python.org/ Member address: matthewturk@gmail.com
Please let me know if you are able to see the plots in the Jupyter notebook. The 2d slice shows a shape that is symmetric about x=0, but the 1d ray, taken through y=0, shows a significant shift away from that shape. I don't have another explanation for what might cause that shift.
Hi Stephen,
I was able to get your dataset, but the notebook was too big and the
pastebin cut it off. Could you upload it the same way you did the
dataset?
On Tue, Jun 23, 2020 at 1:00 PM Stephen Coleman
Please let me know if you are able to see the plots in the Jupyter notebook. The 2d slice shows a shape that is symmetric about x=0, but the 1d ray, taken through y=0, shows a significant shift away from that shape. I don't have another explanation for what might cause that shift. _______________________________________________ yt-users mailing list -- yt-users@python.org To unsubscribe send an email to yt-users-leave@python.org https://mail.python.org/mailman3/lists/yt-users.python.org/ Member address: matthewturk@gmail.com
Just a gentle reminder that this is still an issue. Wondering if anyone is able to see the jupyter notebook posted above
I've changed the underlying geometry of my simulation, so the meshing does not produce a situation where this issue arises anymore. I'll keep an eye out for this in the future, but it is no longer an urgent issue for me.
participants (3)
-
Matthew Turk
-
Stephen Coleman
-
Stephen Coleman