The diagrams shown below indicate how the functions, scripts, programs and files which constitute the LS-DYNA Preference affect the Patran environment. Site customization, in some cases, is indicated.

Figure 1‑1 shows the process of running an analysis. The lsdyna3d.plb library defines the Translation Parameter, Solution Type, Solution Parameter, and Output Request forms called by the Analysis form. When the Apply button is pushed on the Analyze form pat3lsdyna is executed. pat3lsdyna reads data from the database and creates the LS-DYNA input file. A message file is also created to record any translation messages. If pat3lsdyna finishes successfully, and the user requests it, the script will then start LS-DYNA.

Figure 1‑2 shows the process of reading information from LS-DYNA State or Time History files. When the Apply button is selected on the Read Results form, either a .jbm or .jbr file is created, depending on whether model or results data is to be read. The LsdynaPat3Submit script is also started. The script, in turn, starts the lsdynapat3 results translation. The Patran database is closed while this translation occurs.

lsdynapat3 reads the data from the LS-DYNA State and Time History Files. If lsdynapat3 can find the desired database, the results will be loaded directly into it. However, if it cannot find the database (e.g., you are running on incompatible platforms), lsdynapat3 will write all the data into a flat file. This flat file can be taken to wherever the database is, and read by using the read file selections.

Figure 1‑3 shows the process of translating information from a LS-DYNA input file into a Patran database. The behavior of the main Analysis/Read Input File form and the subordinate file select form is dictated by the lsdyna3d.plb PCL library. The Apply button on the main form activates the pat3lsdyna program which reads the specified LS-DYNA input file into the Patran database.