You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
maxV in the simulation is too high for verletskin, collision cutoff, rebuild frequency (currently they are setup for 8km/s)
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
The text was updated successfully, but these errors were encountered:
Feature
Desired behavior
Throw errors / warnings if
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
The text was updated successfully, but these errors were encountered: