Dytran > Files > Files
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
Files
The Patran Dytran Preference uses or creates several files.The following table outlines each file and its uses. In the filename definition, jobname will be replaced with the jobname assigned by the user.
 
File Name
Description
*.db
This is the Patran database. During an Analyze pass, model data is read from, and during a Read Results pass, model and/or results data is written into. This file typically resides in the current directory.
jobname.dat
This is the Dytran input file created by the interface. This file typically resides in the current directory.
jobname.dat.rej
This file contains any keywords and data not recognized by the translator that reads in the Dytran input files. This file typically resides in the current directory.
jobname.arc
This is the Dytran archive file which is read by the Read Results pass. This file typically resides in the current directory.
jobname.ths
This is the Dytran time history file which is read by the Read Results pass. This file typically resides in the current directory.
jobname.flat
This file may be generated during a Read Results pass. If the results translation cannot write data directly into the specified Patran database it will create this jobname flat file. This file typically resides in the current directory.
MscDytranExecute
This is a unix script file which is called on to submit the analysis file to Dytran after translation is complete. This file might need customizing with site specific data, such as, host machine name and Dytran executable commands. This file contains many comments and should be easy to edit. Patran searches its file path to find this file, but it typically resides in the <installation_directory>/bin/exe directory. Either use the general copy in <installation_directory>/bin/exe, or place a local copy in a directory on the file path which takes precedence over the <installation_directory>/bin/exe directory.
p3dytran
This is the actual translation program, translating between the Patran database and an Dytran input file. It is typically run within Patran, transparent to the user, but can also be run independently. For example:
<installation_directory>/bin/exe/p3dytran -j my_job -d my_database.db > my_job.msg &
Patran searches its file path for this file, but it typically resides in the <installation_directory>/bin/exe directory. Note that i is the option for translating from an Dytran input file to an Patran database.
dytranp3
This is the actual reverse translation program. It is typically run within Patran, transparent to the user, but can also be run independently with the following command, (executable name) (jobfile name) (optional redirection of output) (optional backgrounding of process). For example, <installation_directory>/bin/exe/dytranp3 my_job.jbr > my_job.msg &
Patran searches its file path for this file, but it typically resides in the <installation_directory>/bin/exe directory.