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
I noticed that according to the documentation, the global controls lexicon has an optional key launchAzimuth which is supposed to override the automatic azimuth calculation, however, that key in controls is never used in the code, instead there is a check if launchAzimuth exists on the mission lexicon and if not, it is being calculated and added to mission.
I think it makes more sense to have it on the mission lexicon since I'd imagine this would be used for specific missions, rather than on a specific vehicle, so it would be good to update the docs to fix this.
The text was updated successfully, but these errors were encountered:
I noticed that according to the documentation, the global
controls
lexicon has an optional keylaunchAzimuth
which is supposed to override the automatic azimuth calculation, however, that key incontrols
is never used in the code, instead there is a check iflaunchAzimuth
exists on themission
lexicon and if not, it is being calculated and added tomission
.I think it makes more sense to have it on the
mission
lexicon since I'd imagine this would be used for specific missions, rather than on a specific vehicle, so it would be good to update the docs to fix this.The text was updated successfully, but these errors were encountered: