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

Figure 1‑1 shows the process of running an analysis. The mscdytran.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 p3dytran is executed. p3dytran reads data from the database and creates the Dytran input file. If p3dytran finishes successfully, and the user requests it, the script will then start Dytran.

Figure 1‑2 shows the process of reading information from Dytran Archive or Time History files. When the Apply button is selected on the Read Results form the dytranp3 results translation is started. The Patran database is closed while this translation occurs. dytranp3 reads the data from the Dytran State and Time History Files. If dytranp3 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), dytranp3 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 an Dytran 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 mscdytran.plb PCL library. The apply button on the main form activates the p3dytran program which reads the specified Dytran input file into the Patran database.