AGILE features a growing number of design tools with CPACS interfaces.
In order to provide a space collecting multiple CPACS configurations, the CPACS Hangar is launched!
The CPACS configurations hosted in the CPACS Hangar are assembled to challenge the tools’ robustness in different aspects of the CPACS definition itself.
Therefore, the CPACS files mostly include the geometric description of the aircraft components. No analysis results are provided, and the configurations are not necessarily feasible designs with respect to all the different disciplines.
The CPACS Hangar will be expanded during the project, with additional configurations for testing purposes in terms of robustness, including disciplinary oriented verifications.
A section of the CPACS Hangar will be dedicated to collect the Design Campaigns final designs.
First patch for Tools robustness checks:
1) D150_AGILE_Hangar.xml (download)
This CPACS file contains the AGILE D150 configuration with a detailed definition of the aircraft components. External shape, moveables, and internal structural components are defined.
This is the reference CPACS definition file which all the tools should be able to process.
It also includes the mission trajectory for the design mission.
2) NASA_CRM_AGILE_Hangar.xml (download)
The CPACS file contains the outer shape of the NASA CRM. CPACS sections are extracted by “slicing” the original CAD model, and it has been tested with external aerodynamic solvers (from VLM to unstructured based Euler methods).
The positioning of the airfoils and profiles is done mostly through global coordinates in the airfoil definition. This is an example of a different way in which the aerodynamic shapes can be defined.
3) TP_AGILE_Hangar.xml (download)
This configuration resemble a regional Turboprop, featuring high-wing and T-tail.
Only the outer shape is provided.
4) Boxwing_AGILE_Hangar.xml (download)
This definition of the Boxwing configuration could be challenging.
The wing is described by only one wing component, but the definition of the structure uses three separate component segments definitions.
All the tools which rely on data defined within the componentSegment nodes (e.g. structural layout) should check if they can process this CPACS file.