Hello FESTIM Community,
I wanted to share a project I’ve been working on called Processforge, which aims to bring a declarative, infrastructure-as-code workflow (similar to Terraform) to physics simulation engines like FESTIM and OpenMC.
The goal is to make FESTIM runs completely deterministic, version-controlled, and easily offloadable to local or cloud Docker instances without manual setup or environment configurations. I recently recorded a video showing how a FESTIM thermal desorption spectra (TDS in tungsten example on the documentation site) simulation can be defined in a Processforge JSON flowsheet and executed seamlessly via the CLI locally or in the cloud:
Some notes on why Processforge was developed: Define materials, species, traps, and boundary conditions in a structured, version-controllable format so that collaboration is easier. Execute runs across local containers or cloud providers (e.g., AWS, Railway, Docker) using standard commands (pf init, pf plan, pf run) so it can be “1-click” eventually.
I would love feedback on what parts of the FESTIM API should be abstracted in the flowsheet JSON vs. exposed for advanced custom parameters. If you have existing FESTIM simulations or benchmarks you’d like to see running declaratively in Processforge, I’d be happy to help build the flowsheets with you and collaborate.
Please let me know what you think! Thank you and looking forward!