performance_assessment: wrong span_limit xml-node & error due to missing polar data
Description
- changed span limit check xml node name
- added try-catch statement in ceiling calculation for missing polar data: performance_assessment now sets the thrust=drag in case there are no polar data available which results in ROC=0 meaning the max ceiling is reached. This might affect the ceiling performance plot though. I am open for suggestions about a more elegant solution.
Screenshots/Logs
Testing Instructions
Developer Checklist
-
Code has been tested locally and/or in pipeline. -
(if applicable) documentation updated. -
(if applicable) impact of new dependencies reviewed and included in project. -
Merge conflicts resolved with the target branch.
Additional Notes
Add any information reviewers should focus on, e.g., specific files, functions, or changes of interest.