PDI supports loose coupling of simulation codes with libraries:
- the simulation code is annotated in a library-agnostic way,
- libraries are used from the specification tree.
This approach works well for a number of concerns including: parameters reading, data initialization, post-processing, result storage to disk, visualization, fault tolerance, logging, inclusion as part of code-coupling, inclusion as part of an ensemble run, etc.
- PDI usage
- Core concepts
- First steps
- PDI example
- C API reference
- Specification tree reference
- List of PDI plugins
Join the team
You can work with us to make a better PDI:
- a 3-years engineer position: "Improvement and integration of the PDI library for High-performance code coupling",
- a 2-years post-doc position: "Data-driven code-coupling at Exascale",
- and we are always looking for people interested in an internship, drop an email if you are insterested.