We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For species-derived fields (density, charge density, etc.) we don't currently correlate the name with the particle species.
VisualPIC as post-processing tool (@AngelFP) correlates the two in its gui, so it would be great to hint this explicitly.
One way to achive this: consistent naming scheme (e.g. PIConGPU & WarpX: <species>_<filter>_<fieldName>; FBPIC: <fieldName>_<species>).
<species>_<filter>_<fieldName>
<fieldName>_<species>
Another way: define a string attribute on the field with the species name (nice because simple and non-breaking).
One could even define this in the base standard for meshes.
The text was updated successfully, but these errors were encountered:
ax3l
RemiLehe
franzpoeschel
AngelFP
No branches or pull requests
For species-derived fields (density, charge density, etc.) we don't currently correlate the name with the particle species.
VisualPIC as post-processing tool (@AngelFP) correlates the two in its gui, so it would be great to hint this explicitly.
One way to achive this: consistent naming scheme (e.g. PIConGPU & WarpX:
<species>_<filter>_<fieldName>
; FBPIC:<fieldName>_<species>
).Another way: define a string attribute on the field with the species name (nice because simple and non-breaking).
One could even define this in the base standard for meshes.
The text was updated successfully, but these errors were encountered: