PCL and Customization > Creating New Analysis Forms Using PCL > Contents of the Analysis Library
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
Contents of the Analysis Library
As a minimum, the Analysis library should contain one PCL class called <analysis_code>_load_aom_data. The <analysis_code>_load_aom_data class must contain as many functions as there are analysis types related to the current analysis code and the name of each of these functions is <analysis_type>. For example, if the analysis code “ANSYS” has two analysis types, “Structural” and “Thermal,” then the PCL library “anays.plb” must contain the PCL class, “ansys_load_aom_data” and this class must contain two functions called “structural” and “thermal”.
Of course, the Analysis library will most likely contain many more functions than the minimum set mentioned above. Most of the time the <analysis_code>_load_aom_data class will reference a PCL class, <apply_class>, which will contain the “apply” function activated by the Apply button on the main Analysis form and the Analysis functions. All subordinate Analysis forms will be controlled by PCL classes which exist in the Analysis library. Any PCL application code, such as the actual application, if written in PCL, or functions which will gather data for an external application, prepare Patran for an external application (such as close the database, if necessary) and spawn the external application program, should exist in the Analysis library.