Closed ax3l closed 3 years ago
We found that relaxing the type of particle IDs can be useful for some applications.
Also fixes inprecise wording about the particle group where this belongs to.
base
Previously fixed to 64bit integers, the ID can now be an arbitrary integer.
How does this change affect data writers? What would a writer need to change? Does this pull request change the interpretation of existing data writers?
openPMD-api
id
How does this change affect data readers?
What would a reader need to change? Link implementation examples!
openPMD-validator
openPMD-viewer
yt
VisIt
No conversion needed, since the prior type is still allowed.
Description
We found that relaxing the type of particle IDs can be useful for some applications.
Also fixes inprecise wording about the particle group where this belongs to.
Affected Components
baseLogic Changes
Previously fixed to 64bit integers, the ID can now be an arbitrary integer.
Writer Changes
How does this change affect data writers? What would a writer need to change? Does this pull request change the interpretation of existing data writers?
openPMD-api: https://github.com/openPMD/openPMD-api is not affected, since users write theidthemselvesReader Changes
How does this change affect data readers?
What would a reader need to change? Link implementation examples!
openPMD-validator: https://github.com/openPMD/openPMD-validator/pull/62openPMD-viewer: https://github.com/openPMD/openPMD-viewer should be unaffected due to dynamic typingyt: https://github.com/yt-project/yt unaffectedVisIt: https://github.com/openPMD/openPMD-visit-plugin unaffectedopenPMD-api: https://github.com/openPMD/openPMD-api is not affected, since users write theidthemselvesData Converter
No conversion needed, since the prior type is still allowed.