I’ll merge today this feature.
It’s optional, by default the mass is not included in the STM.
As of now, there is a few limitations:
- it is not compatible with all native parameter drivers. For example the
TriggerDate
- only
Maneuver
inheritors are considered. If you have a customForceModel
modifying mass, it won’t see it because at the moment there is no direct access to the mass equation. To change that we would need to expose some sort ofgetMassDerivative
inForceModel
. I think it could make sense. By default it would return 0