-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lat / Lon particle output #4
Comments
Resolved by #15. |
Closed by #15 |
I'm seeing a bug when testing my particle output for this. latParticle seems to be working but not lonParticle. See below. I select an arbitrary particle number, then manually convert its x/y/z location to lat/lon and check it against the output latParticle/lonParticle. |
@bradyrx, great catch. There is a shift in longitude that is needed to correspond to a direct mapping with the mesh, e.g., see be19e75 I needed to add this for consistency with respect to our mesh conversion / coordinate system for the mesh. If you check for cell centers closest to the particles (which is the metric I used), do you reasonable results? This was how I validated the longitude of the particles. |
@bradyrx, please close (or leave open) until we have this 100% resolved. Thanks! |
Thanks for the feedback and suggestion. Just wanted to vet the simple fixes (i.e. lat/lon/global ID) on my own through python and not just paraview. See below implementation for verification: |
I think you need to do this since I'm not an assignee. No comment & close option for me. |
Thanks! |
Consider including in input in particle initialization. |
Particle output should be reported in latitude and longitude coordinates to facilitate global analysis.
The text was updated successfully, but these errors were encountered: