Desired capability or behavior.
Currently business class seat and passenger information is not used when Aviary is asked to size the fuselage based on seat data.
This matches the legacy flops fortran code, but is confusing for the user if they change the number of business class seats, or seat pitch then it will have no effect on the computed size of the aviary fuselage.
For reference the equivalent BWB component does include all 3 passenger classes:
We need to add the variables to the component, design and code some new equations that describe how to calculate fuselage length based on all 3 passenger classes, and then add these changes to the documentation.
Is your feature request related to a problem? Please describe.
No response
Associated Bug Report
No response