Bevy has tremendous potential as a framework for scientific simulations: it's fast, modular, easy to read/write and hooks in readily to convenient features like graphics and UIs.
This is a tracking issue to discuss the important features to help us get there (h/t @alec-deason). Many of these are "ecosystem" issues, rather than something that needs to be solved by the Bevy engine itself.
Universal features
Improved documentation and API maturity. Templates and guides are a big part of this, as is battle-tested correctness.
Charts / graphing integration.
Statistical integrations.
Ergonomic data logging.
Headless mode (#22, #436), with good file-driven configuration.
Deterministic RNG. This includes good enough APIs to get to zero-system ambiguities (#1312) and ordered query iteration (#1470), but the story is complex.
Fixed point support, for more stable computations.
Ergonomic saving and loading (#1442) with checkpointing.
Cross-machine distributed processing.
System order visualization and modification.
Better testing and correctness tools. #1481 is a good start.
Domain specific features
Indexes (#1587, #1527), for simple and correct grid-based simulations.
Bevy has tremendous potential as a framework for scientific simulations: it's fast, modular, easy to read/write and hooks in readily to convenient features like graphics and UIs.
This is a tracking issue to discuss the important features to help us get there (h/t @alec-deason). Many of these are "ecosystem" issues, rather than something that needs to be solved by the Bevy engine itself.
Universal features
Domain specific features