The attached test Params_LhsDeps_OutgoingAsymptote.script sets the OutgoingAsymptote state in different orders in the mission sequence. The report file should contain lines with identical data, but OutgoingRHA, OutgoingDHA, and OutgoingBVAZI differ in each case.
Running Params_LhsDeps_OutgoingAsymptote_Debug.script shows why. This reportfile shows the truth data in line 1, then it shows IncomingAsymptote and OutgoingAsymptote data before and after each line setting a component of the state.
When HyperbolicRadPer is set, GMAT is going through the IncomingAsymptote system, and the Incoming parameters are being held constant. This causes the Outgoing parameters to change, which is not what the user intended. This occurs with C3Energy also, if you place that line last.
What we actually need is four new parameters, none of which are shared:
- IncomingRadPer (instead of HyperbolicRadPer)
TA does not show the same behavior, so we don't need to split that off.
SharedParamTests.zip contains script that try all state reps with shared params in different orders. It would help if someone else could bang on it also, since I keep missing things.