j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
There's a chance that the algorithm used by the quiver callback (used by annotate_velocity) is not doing the correct thing for non-Cartesian data near the origin.
Is there any chance you can make a script that demonstrates the issue you're seeing? If none of the public test datasets at yt-project.org/data are suitable for reproducing this issue, it would also help if you can make a test dataset available so that we can reproduce the behavior you're seeing. You can use the yt curldrop to share data:
On Wed, Jan 18, 2017 at 11:52 AM Lu, Yinghe email@example.com wrote:
> > > >
Hi, I have a question regarding how the function annotate_velocity is
performed. From one of the datasets I am analyzing ( I use FLASH4 data), at regions around simulation coordinates r=0 with the default setting (no scaling, no normalization), yt seems to plot velocity vectors pointing to random directions which is inconsistent with the field values of "velocity_magnitude" in that region that my simulation set it to. I wonder if anyone else has encountered this kind of problem before, and if there's a easy way to double check on the data. Thanks!
yt-users mailing list