During the normal mission (not the vector mission), the drag coefficient is calculated inside a function equation_outer passed to a solver to find the trim point. The output of the function is driven to zero by the solver. As a result, the drag coefficient, corresponding to the trim point is not accessible outside of this function.
The goal is to make the trimmed drag coefficient accessible in the mission phases (climb, cruise...) computation and fill the dedicated field in mission FlightPoints.
An idea would be to use a trimmed polar. One would have to drop the drag due to elevator deflection provided that this term is small (which probably it is) and that the HTP is not trimmable.
If some more degrees of freedom are necessary, then using a polar object which implements the CL, CD calculation is another idea.
During the normal mission (not the vector mission), the drag coefficient is calculated inside a function
equation_outerpassed to a solver to find the trim point. The output of the function is driven to zero by the solver. As a result, the drag coefficient, corresponding to the trim point is not accessible outside of this function.The goal is to make the trimmed drag coefficient accessible in the mission phases (climb, cruise...) computation and fill the dedicated field in mission FlightPoints. An idea would be to use a trimmed polar. One would have to drop the drag due to elevator deflection provided that this term is small (which probably it is) and that the HTP is not trimmable.
If some more degrees of freedom are necessary, then using a polar object which implements the CL, CD calculation is another idea.