Test simulations parameters for sensibility during runtime
- Dominant language
- Jupyter Notebook
- Stars
- 10
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
# Feature
## Desired behavior
Throw errors / warnings if
- [ ] maxV in the simulation is too high for verletskin, collision cutoff, rebuild frequency (currently they are setup for 8km/s)
- [x] particles go below 200km or such? (@FG-TUM we should also add automatic removal for that maybe another issue?)
- [ ] timestepsPerCollisionDetection: There is an upper bound for this when the interpolation is not precise enough anymore)
- ... what else may be useful?
## What needs to be done
Check loaded and running data against cfg / simulation values every N iterations (each will require computing a max over all velocities and all altitudes so shouldn't happen too often?
## How it can be tested
create sim / test case with fast and low altitude particles
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.