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
As a feedback to the last stakeholder meeting, @elPlaneador proposed to add a remainingContribution node below remainingContributions in order to allocate the contributions more closely to individual components that cause these contributions.
One drawback is that the components in question are not explicitly specified via the CPACS schema, making automated interpretation of the content difficult. I recommend collecting specific components (antennas, sensors, etc.) when applying the feature in practice, so that if they are used too laxly in practice, an additional enumeration can be added that explicitly specifies what exactly causes the remaining contribution.
The text was updated successfully, but these errors were encountered:
cpacs/vehicles/aircraft/model/analyses/loadCases/aeroCases/aeroCase/aeroData/vehicle/coefficientsBreakdown/remainingContributions:
As a feedback to the last stakeholder meeting, @elPlaneador proposed to add a
remainingContribution
node belowremainingContributions
in order to allocate the contributions more closely to individual components that cause these contributions.One drawback is that the components in question are not explicitly specified via the CPACS schema, making automated interpretation of the content difficult. I recommend collecting specific components (antennas, sensors, etc.) when applying the feature in practice, so that if they are used too laxly in practice, an additional enumeration can be added that explicitly specifies what exactly causes the remaining contribution.
The text was updated successfully, but these errors were encountered: