MSC.FlightLoads V2001 R2 patch

---

This patch is created to correct several limitations and issues in MSC.FlightLoads 2001 R2 release. The following is the list of the limitations and issues that have been fixed in this patch.
If the user changes the name of the selected existing job in Flutter, an error message occurs.
When an existing job is selected in Flutter Analysis, and the job name is then modified, an error message will occur. Actually, the existing job function will fail even with the same job name. The existing job function for Flutter was not implemented.

BDF translation failed for large Flutter analysis problems.
Large Flutter analysis problems failed in BDF translation only on the SUN platform.

Mach number tolerance needed in Flight Loads Aeroelasticity
There is no tolerance when comparing a Mach number that is input for flutter analysis to a Mach number that is input in a mach/k pairs table.

For example: I can input a Mach number of 0.80002 into a mach/k pairs table. I can then set up a flutter run and input mach=0.8 When I try to run the job, I get the following error:

Mach value of the selected subcase is not available in the selected Mach-Frequency pair. Please select valid subcase prior to submittal.

A Mach number tolerance of 0.001 should be added to this check.

Add toggle to Mach input on M/K pairs form
On the form to input mach/K pairs, the input for Mach number has two possibilities:

1. If a single Mach number is to be input, only one of "Min Mach" or "Max Mach" needs to be input, along with "Number".

2. If a range of mach numbers are to be input, then all three fields need to be entered.

The fact that possibility #1 even exists is not obvious from the form as it currently exists. To fix this, a toggle should be created, similar to the "Dimensional" toggle for the Frequency input. This toggle should be called "Mach Range", and its default setting should be "off". With the toggle set to "off", there should be only one field to fill in, with the label "Mach". With the toggle set to "on" there should be three input fields, exactly as exists in the current version.

Coordinate system not always written out in the BDF.
When the coordinate system is only referenced by monitor points, that coordinate system is not written out in the BDF file.

Incorrect spline type on Export of TPS splines against 3D meshes.
When you create a surface spline for an Imported (AMIF) 3D aero mesh and then Export/BDF Fragment the resulting spline, it is incorrectly designated an IPS spline--3D meshes are always TPS splines.

FLFACT card's SID not reset between sessions.
The forward translated bdf file used in FLDS for flutter analysis has FLFACT cards to specify flutter parameters. The SID (set identification number) of the FLFACT cards are not reset between FLDS sessions (same instance of P3 running).

Can not select an existing monitor point to Create a new one.
In CREATE/MONITOR POINT, an existing monitor point can not be selected. This is inconsistent with other CREATE forms in Patran. Normally one uses this method to create another similar entity instead of going to VERIFY or MODIFY first and then using the data for creation of the new one.

Spline Verify fails if xdb attached in structure rather than Flightloads
If a xdb that contains modal results is attached to Patran under the Structures preference, then spline verify fails with the following error:

There are no [Eigenvectors] results on the structural nodes in the chosen Spline(s).

If the same xdb is attached in the Flight Loads Results Browser, then the spline verify works as expected.

3D spline verification is broken due to the inconsistent component ids of AECOMP datablock created.
The match between the component ids of Nastran AECOMP datablock and what are referred to by SPLINEi entries are broken for 3D spline verification. This is a side effect of the match mechanism being updated for the ADB export case, but not the 3D spline verification case.

Error message #404 encountered in ADB export.
This quality is created for the following observed problems in the area of Flds ADB export and spline verification:

1. In the process of adb export, error message 404 comes up indicating that some nonexistent node ids are used while writing AEBOX datablocks.
2. For a large aero 3D model with multiple large splines, AELIST entries are all zeros for some SPLINE4 cards.
3. Currently, the duplicated aero grids ids are existing in AELIST entries for different splines.

Installation:

• Download the file flds_2001r2_patch_<MACHINE>.tar.Z below for <MACHINE> platform.
• Uncompress the file by typing gzip -d flds_2001r2_patch_<MACHINE>.tar.gz.
• Untar the uncompressed file by typing tar -xvf flds_2001r2_patch_<MACHINE>.tar.
• Up to this point, two files should be obtained. There are p3flds.plb and libflds.<EXT> where <EXT> varies with platforms or aero.dll for WINNT platform. Replace p3flds.plb in P3_HOME with the new one. Replace libflds.<EXT> or aero.dll in P3_HOME/lib with the new one.