Flightloads > Import/Export > Import
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
Import
The Import capability allows the user to retrieve an aerodynamic model into the current MSC.Patran database described in an MSC.Nastran input file, an Aero Mesh Interface File, or an A502 File.
Model data, including lifting surface, body, control device and splines can be imported by reading an MSC.Nastran input file (.bdf or .dat file). 3D model data can be imported in two different ways. The user can read in an Aero Mesh Interface File (.ami file), see Appendix F for the user can read in an A502 File (.inp file). The import form shown here gives the user access to all three import methods.
 
Note:  
1. Upon reading in a MSC.Nastran input file, the appropriate entities are created in the database as if the user had performed the construction via the user interface. The appropriate session file commands mimicking this construction are created.
2. The aerodynamic coordinate system from the bulk data file as well as hinge line coordinate systems are copied into the MSC.Patran database. However, if a coordinate system of the same ID is already in the database, it is assumed that this coordinate system is to be used and the one from the bulk data file is not imported.
3. For the spline information to be imported, the structural nodes must already exist in the database. If you are importing both the structural and aerodynamic models into the database, you must import the structure first (using the File/Import option of the MSC.Patran Structural Preference) before using the MSC.FlightLoads Import option to obtain the aerodynamic model. If the structural nodes are not present, the aerodynamic model is imported but not the aeroelastic model.
4. Importing of 3D model data causes the appropriate entities to be created in the database. Currently, there is no user interface to allow the users to create 3D models from scratch so no commands are written to the session file.