The names of the Analysis PCL library, <analysis_code>.plb, and the class which must exist in this library, <analysis_code>_load_aom_data, are derived from the analysis code name. Also, the mandatory functions within the <analysis_code>_load_aom_data PCL class (<analysis_type>_ are derived from the name of the available analysis types. The following rules should be used to convert the analysis code name or analysis code name or analysis type name to the <analysis_code> or <analysis_type> prefix.

For example, the prefix for “MSC.Nastran” is mscnastran,” for “Structural,” “structural,” and for “John Code,” “johncode.” This derived prefix is referenced in this chapter as either <analysis_code> or <analysis_type>.

It is recommended that the user add a unique prefix to all his PCL classes and class-less functions in order to ensure uniqueness in class and function name. For example, if the user were to create a PCL class which controlled selecting a file for an analysis code called “John Code” a good class name would be “john_select_file.” Just using “select_file” as the name might interfere with already existing Patran PCL classes or functions.