This is a photon and neutron raytracing extension for openPMD that has been developed as part of the Panosc project. It is supposed to represent the minimal set of variables to correctly save and represent raytracing simulations.
Description
This extension has been based on the BeamPhysics extension, trying to maintain functionality as close as possible. Furthermore, a working API with C++ and Python bindings based on this extension definition is in the making and will be provided when completed.
We have already created widgets for Oasys simulation package which allows for export of openPMD files. However, the scripts are based on a previous, working version of the extension.
New Components
EXT_BeamPhysics_PRAYTRACE.md
Logic Changes
Which logic changes are conceptually introduced?
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?
How does this affect already existing files with previous versions of the standard?Is this change possible to be expressed in a way, that an automated tool can update the file?Link code/pull requests that implement the upgrade logic!
This is a photon and neutron raytracing extension for openPMD that has been developed as part of the Panosc project. It is supposed to represent the minimal set of variables to correctly save and represent raytracing simulations.
Description
This extension has been based on the BeamPhysics extension, trying to maintain functionality as close as possible. Furthermore, a working API with C++ and Python bindings based on this extension definition is in the making and will be provided when completed.
We have already created widgets for Oasys simulation package which allows for export of openPMD files. However, the scripts are based on a previous, working version of the extension.
New Components
EXT_BeamPhysics_PRAYTRACE.mdLogic Changes
Which logic changes are conceptually introduced?
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?
libopenPMD(upcoming): https://github.com/ComputationalRadiationPhysics/libopenPMD/...Reader 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/...openPMD-viewer: https://github.com/openPMD/openPMD-viewer/...yt: https://github.com/yt-project/yt/...VisIt: https://github.com/openPMD/openPMD-visit-pluginlibopenPMD(upcoming): https://github.com/ComputationalRadiationPhysics/libopenPMD/...XDMF(upcoming): https://github.com/openPMD/openPMD-tools/...Data Converter
How does this affect already existing files with previous versions of the standard? Is this change possible to be expressed in a way, that an automated tool can update the file? Link code/pull requests that implement the upgrade logic!