10 Mar 2021 10 Mar '21
Handling equations of states outside of frontends also seem like a nice thing to do, but there should be room for extensions at the frontend level. In AMRVAC we have a handful of EOS and users are even allowed to define their own, which completely unsupported atm in the frontend.
The idea here is more that there would be a class which could take a few field definitions (do you have density+temperature, or density+internal energy, or something else) and then define the rest of the fields from those. But this wouldn’t be something that is separate from frontends--on the contrary, each frontend would use EOS objects to create field definitions from the fields and other metadata defined on disk.