-
Notifications
You must be signed in to change notification settings - Fork 200
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
Particle diagnostic silently writes zero position if x y z is not explicitly specified #4841
Comments
Thanks for the nice reproducer. Could you confirm that #4855 fixes this issue? |
Discussed on I/O channel: We will try the following update:
|
@kale-j Thank you for the report!
Can you point me to where the docs still read that? This must have slipped through. We changed this behavior (and the docs) so that positions are treated like any other particle property as well when we transitioned our particles to a pure SoA data structure in the last months.
Thanks for the reproducer 🙏 This should simply not write the position when not selected (bug). |
Thanks, agreed! And also, we have additionally shortcuts |
@RemiLehe @ax3l |
I pushed an update to both outdated docs and diagnostics: #4914 |
One of the changes in the last few months (some time between December and March) has affected the default behavior of the output for the particle data diagnostic. The new behavior seems unexpected and is not documented.
In a Full diagnostic, consider
<diag_name>.<species_name>.variables = w
Previous behavior:
Particle position is written in addition to the weight
-- this is what the documentation indicates should happen
Current behavior:
Zeros are written for the particle position regardless of where the particles actually are
The actual particle position is only written if the desired positions are explicitly specified, i.e.,
<diag_name>.<species_name>.variables = w x y z
MWE is attached
inputs_3d.txt
The text was updated successfully, but these errors were encountered: