Currently, if you set the 'target_range' in post_mission within your phase_info object then a constraint will be added to make the mission distance match that value. This is easily confusing with Mission.Design.RANGE also existing. Users might set one or the other thinking it would impact the mission they're evaluating. We should consolidate or clarify this in some way to prevent confusion.
Another consideration is that we're trying to keep the aircraft definition and mission definition as two separate files. If the user sets Mission.Design.RANGE in their .csv, should that directly affect the performed mission length in Aviary? This might need to wait for the notion of off-design to come into Aviary; it's definitely affected.
Please chat with me about more details on this issue before tackling it.
Is your feature request related to a problem? Please describe.
Desired capability or behavior.
Currently, if you set the
'target_range'inpost_missionwithin yourphase_infoobject then a constraint will be added to make the mission distance match that value. This is easily confusing withMission.Design.RANGEalso existing. Users might set one or the other thinking it would impact the mission they're evaluating. We should consolidate or clarify this in some way to prevent confusion.Another consideration is that we're trying to keep the aircraft definition and mission definition as two separate files. If the user sets
Mission.Design.RANGEin their .csv, should that directly affect the performed mission length in Aviary? This might need to wait for the notion of off-design to come into Aviary; it's definitely affected.Please chat with me about more details on this issue before tackling it.
Is your feature request related to a problem? Please describe.
No response
Associated Bug Report
No response