Skip to content

openPMD-api: raise minimum required version to 0.17#5613

Draft
franzpoeschel wants to merge 11 commits intoComputationalRadiationPhysics:devfrom
franzpoeschel:openpmd-0-17
Draft

openPMD-api: raise minimum required version to 0.17#5613
franzpoeschel wants to merge 11 commits intoComputationalRadiationPhysics:devfrom
franzpoeschel:openpmd-0-17

Conversation

@franzpoeschel
Copy link
Copy Markdown
Contributor

@franzpoeschel franzpoeschel commented Jan 23, 2026

This should not be immediately merged, users should have some time to upgrade.

PR implements the following new features:

  • Use of RecordComponent::SCALAR has been discarded (need to scan for usage in other places / other plugins again though)
  • The JSON matcher has been discarded and the equivalent functionality of the openPMD-api is now used
  • --openPMD.toml now allows specifying openPMD backend options in TOML format, it is no longer needed to give them as a JSON string within TOML

TODO:

  • Scan again for use of RecordComponent::SCALAR
  • Write (and test) a documentation example for --openPMD.toml

@PrometheusPi
Copy link
Copy Markdown
Member

@franzpoeschel regarding your first statement:

This should not be immediately merged, users should have some time to upgrade.

What time frame for making this mainline do you envision?
I will set it as draft for now.

@franzpoeschel
Copy link
Copy Markdown
Contributor Author

What time frame for making this mainline do you envision?

Discussed with @psychocoderHPC in the last dev meeting: Some time halfway between now and the next PIConGPU release. Probably before/around summer break or so.

I will set it as draft for now.

The CI also runs on draft PRs, right?

@PrometheusPi
Copy link
Copy Markdown
Member

Yes, even in draft mode, the CI still checks the code.

@psychocoderHPC
Copy link
Copy Markdown
Member

@psychocoderHPC psychocoderHPC added this to the 0.9.0 / next stable milestone Feb 4, 2026
@psychocoderHPC psychocoderHPC added the refactoring code change to improve performance or to unify a concept but does not change public API label Feb 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

refactoring code change to improve performance or to unify a concept but does not change public API

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants