Patran Thermal Execution

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">

2. Build or modify a TEMPLATEDAT file suitable for the problem. This file contains templates for the Material ID numbers (MIDs) assigned in Patran Plus as well as templates for the Template ID (TID) boundary condition codes assigned in Patran. The TEMPLATEDAT file can be thought of as a pointered list architecture. Since Patran Thermal requires a great deal of data for boundary conditions (which is typical of nonlinear codes), it is convenient to build a library of these boundary condition data sets and store them in the TEMPLATEDAT file. These boundary condition data sets are then referenced by a TID from Patran. For example, a time and temperature-dependent heat source may be applied to a portion of your mesh from Patran Plus merely by assigning a heat source TID to that part of the mesh. This TID points to a MACROfunction TID data set in the TEMPLATEDAT file. More than one mesh portion may use the same TEMPLATEDAT TID data set if needed. TID data sets supported by the TEMPLATEDAT file include Material ID sets (MID), MACROfunction sets (MACRO), convective data sets (CONV) hydraulic network data sets (FLUID), and radiation data sets (VFAC). The TEMPLATEDAT file for the problem MUST exist prior to executing the PATQ translator program.

3. Execute the PATQ program to translate the Patran Plus neutral file data and the TEMPLATEDAT file data into QTRAN input data file segments and into an input file for the radiation view factor code (VIEW FACTOR) if required. During this translation phase, PATQ takes the Patran Plus finite element data and boundary condition data and translates it into a mathematically exact resistor/capacitor network model.

Note:	The conductive resistors coming from PATQ are mathematical in nature and have no physical basis (e.g., negative A/L ratios are not uncommon). Do not be alarmed. They are necessary for the mathematical exactness of the translation.

4. If the problem involves the calculation of thermal radiation view factors, execute VIEW FACTOR now. It will read the VFINDAT file generated by PATQ and will generate a QTRAN input data file segment named VFRESDAT for radiative resistors.

5. Create (or edit an existing) QINDAT file. QINDAT is the QTRAN input data file. QINDAT contains a number of run control parameters and other data necessary for QTRAN to execute. It will normally contain a number of “$INSERT” filename commands. The $INSERT commands cause the referenced file name to be inserted by QTRAN into the input data stream as QTRAN executes. This keeps the QINDAT file rather small and reference the larger PATQ output files with $INSERT commands. In addition to the PATQ output files, maintain the additional $INSERT files (e.g., a MATDAT file for material property data and a MICRODAT file for QTRAN microfunction data). It should be noted that QTRAN will honor ANY file name included as a $INSERT file. There is nothing special to QTRAN about the PATQ output files. This allows customized data files to be built for the particular applications.

6. Now the QINDAT file has been constructed or modified for the problem. This includes the $INSERT commands necessary for any PATQ output files being used by the model as well as any other data such as material properties, microfunction data, and the VIEW FACTOR VFRESDAT file. Execute PATQ again. This time, select the menu option that will build a new QTRAN main module. What PATQ does is read the QINDAT file that will be run through QTRAN and counts up how large the array dimensions for QTRAN need to be. When the counting process is finished, PATQ then writes out about 300 lines of Fortran into a file called QTRANFOR. QTRANFOR is the QTRAN main module and consists of very little other than dimension statements and a call to subroutine CRUNCH.

7. Now that QTRANFOR exists, compile it and link it to the QTRAN library. The results are in an executable image of QTRAN that is optimally dimensioned for the problem. If using any user-supplied subroutines, these subroutines must be included in the linking process. The exact procedure will be installation-dependent. The user has the ability to execute a predimensioned, predefined QTRAN executable which is in the thermal library with the name qtran_lib.exe. Even if you are executing the predefined executable the step that create the QTRANFOR file should still be performed as this step also loads any undefined material properties from the library.

8. Execute QTRAN. QTRAN will read in the QINDAT file and will generate the output files STATBIN and QOUTDAT, as well as one or more Patran nodal results files named NRnnnNRF (where nnn is an integer number corresponding to each QTRAN print dump). STATBIN is a status file to which QTRAN continuously writes. QOUTDAT is the results output file for the QTRAN run. QINDAT and QOUTDAT are text files. STATBIN is a binary direct access file that can be queried by using the QSTAT utility provided with Patran Thermal. NRnnnNRF files are standard Patran nodal results files containing temperature data as well as the net nodal heat flow rate and the explicit stable time step for each node. The NRnnnNRF files can be read directly by Patran, and they can also be used as restart files for QTRAN. PATQ can also convert the NRnnnNRF files to a Patran neutral file format for use as thermal load conditions for structural codes.

The qtran_lib.exe file in the p3thermal_files/lib directory can be replace with one tailored to one’s specific needs. If the problem being executed terminates with errors associated with the problem dimensions simply follow the normal run procedures in which the qtran.f file is compiled, linked and run. The qtran.f file can be altered to better suit a users normal run environment or can be linked with a users specific user library to a special executable. To have this new executable be the standard executed when the direct execution option is flagged, simply replace the qtran_lib.exe with the new qtran.exe created changing its name to qtran_lib.exe.

QINDAT	This file is read by both PATQ and QTRAN. PATQ takes the QINDAT file and generates a new QTRAN main program module named QTRANFOR.
QOUTDAT	This file is generated by QTRAN and is read by PATQ. PATQ takes the QOUTDAT file and (a) generates Patran nodal results files, (b) generates Patran neutral file segments, or (c) generates time-temperature print-plots.
QPLOTDAT	This file is generated by QTRAN and may be read by PATQ. PATQ takes the QPLOTDAT file and converts it from binary to an ASCII file.
NRnnnNRF	These files are standard Patran nodal results files generated by QTRAN. One NRnnnNRF file is generated for each QTRAN print dump. PATQ can process these files and convert them to NFnnnDAT files (standard Patran neutral files) which can be used to apply thermal load conditions to structural models. PATQ can also read a sequence of NRnnnNRF files and generate Patran X-Y plot files, thereby allowing you to use Patran’s X-Y plot utility to display temperature histories. Finally, PATQ also reads one or more NRnnnNRF files when it is performing a temperature interpolation from a thermal mesh to a dissimilar structural mesh. Output columns in the nodal results files. * These values are not put in the nodal results file if it is created from a QOUTDAT file.
TEMPLATEDAT	This file is read by PATQ and contains material property ID numbers along with boundary condition template data.
THERMAL$DIR:[LIBRARY]TEMPLATEBIN
	This file is read by PATQ and contains the default MID templates for the material property database.
THERMAL$DIR:[LIBRARY]TEMPLATETXT
	This file can be read by PATQ and converted to TEMPLATEBIN. The TEMPLATETXT file is text and can by modified by your system manager using a text editor.
THERMAL$DIR:[LIBRARY]MPIDMKS, THERMAL$DIR:[LIBRARY]MPIDIPS, THERMAL$DIR:[LIBRARY]MPIDFPH, and THERMAL$DIR:[LIBRARY]MPIDCGS
	These files are material property database files which can be read by PATQ when generating a new QTRANFOR file. These text files can be modified with your system editor. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively. These files are material property database files which can be read by PATQ when generating a new QTRANFOR file. These text files can be modified with your system editor. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively.
THERMAL$DIR:[LIBRARY]MPIDMKSBIN, THERMAL$DIR:[LIBRARY]MPIDIPSBIN, THERMAL$DIR:[LIBRARY]MPIDFPHBIN, and THERMAL$DIR:[LIBRARY]MPIDCGSBIN
	These files are material property database binary files which can be read by PATQ when generating a new QTRANFOR files. These files can be created by executing PATQ utility menu pick 2. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively.
OLDMATDAT	This file is read by PATQ and contains material property data to be translated to LCI type material property tables.
PATQINP	This file is an input file that contains all the responses to the PATQ menu request. This file is required when batch submittals are executed with the PATQB or OTRANB commands.

QINDAT

This file is read by both PATQ and QTRAN. PATQ takes the QINDAT file and generates a new QTRAN main program module named QTRANFOR.

QOUTDAT

This file is generated by QTRAN and is read by PATQ. PATQ takes the QOUTDAT file and (a) generates Patran nodal results files, (b) generates Patran neutral file segments, or (c) generates time-temperature print-plots.

QPLOTDAT

This file is generated by QTRAN and may be read by PATQ. PATQ takes the QPLOTDAT file and converts it from binary to an ASCII file.

NRnnnNRF

These files are standard Patran nodal results files generated by QTRAN. One NRnnnNRF file is generated for each QTRAN print dump. PATQ can process these files and convert them to NFnnnDAT files (standard Patran neutral files) which can be used to apply thermal load conditions to structural models. PATQ can also read a sequence of NRnnnNRF files and generate Patran X-Y plot files, thereby allowing you to use Patran’s X-Y plot utility to display temperature histories. Finally, PATQ also reads one or more NRnnnNRF files when it is performing a temperature interpolation from a thermal mesh to a dissimilar structural mesh.

Output columns in the nodal results files.

* These values are not put in the nodal results file if it is created from a QOUTDAT file.

TEMPLATEDAT

This file is read by PATQ and contains material property ID numbers along with boundary condition template data.

THERMAL$DIR:[LIBRARY]TEMPLATEBIN

This file is read by PATQ and contains the default MID templates for the material property database.

THERMAL$DIR:[LIBRARY]TEMPLATETXT

This file can be read by PATQ and converted to TEMPLATEBIN. The TEMPLATETXT file is text and can by modified by your system manager using a text editor.

THERMAL$DIR:[LIBRARY]MPIDMKS,

THERMAL$DIR:[LIBRARY]MPIDIPS,

THERMAL$DIR:[LIBRARY]MPIDFPH, and

THERMAL$DIR:[LIBRARY]MPIDCGS

These files are material property database files which can be read by PATQ when generating a new QTRANFOR file. These text files can be modified with your system editor. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively. These files are material property database files which can be read by PATQ when generating a new QTRANFOR file. These text files can be modified with your system editor. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively.

THERMAL$DIR:[LIBRARY]MPIDMKSBIN,

THERMAL$DIR:[LIBRARY]MPIDIPSBIN,

THERMAL$DIR:[LIBRARY]MPIDFPHBIN, and

THERMAL$DIR:[LIBRARY]MPIDCGSBIN

These files are material property database binary files which can be read by PATQ when generating a new QTRANFOR files. These files can be created by executing PATQ utility menu pick 2. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively.

OLDMATDAT

This file is read by PATQ and contains material property data to be translated to LCI type material property tables.

PATQINP

This file is an input file that contains all the responses to the PATQ menu request. This file is required when batch submittals are executed with the PATQB or OTRANB commands.

PATQMSG	This file is a message file that contains all output written to the screen and the users response. This is a standard ASCII text file that is a record of a PATQ session.
PATQSES	This file is a standard ASCII text file that contains the responses of all user request mode by PATQ. This file can be renamed to PATQINP and used for input to future PATQ batch executions. The responses, if different from those used during the creation, would be edited to reflect new desired responses.
QTRANFOR	This file is generated by PATQ from a complete QINDAT file. QTRANFOR is the main program module for QTRAN. QTRANFOR must be compiled and linked with the QTRAN library to generate a new executable QTRAN for each problem.
THERMAL$DIR:[LIBRARY]MPIDMKSBIN, THERMAL$DIR:[LIBRARY]MPIDIPSBIN, THERMAL$DIR:[LIBRARY]MPIDFPHBIN, and THERMAL$DIR:[LIBRARY]MPIDCGSBIN
	These files are material property database binary files which can be generated by PATQ utility menu pick 2. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively.
QPLOTTXT	This file is generated by PATQ from the QPLOTDAT file created by QTRAN and converts it from binary to an ASCII file.
NRnnnNRF	These files can be generated by PATQ from a QTRAN QOUTDAT output file. One NRnnnNRF file is generated for each print dump. Normally, this does not have to be done because QTRAN generates these files automatically. Output columns in the nodal results files. * These columns are not generated from QOUTDAT files using PATQ menu pick 5.
NFnnnNEU	These files are the Patran neutral files generated by PATQ from a QTRAN QOUTDAT output file, from QTRAN NRnnnNRF nodal results files, or from a temperature interpolation operation.
TITLEDAT	This file provide information about when and what versions of code were used to generate the input file being executed. In addition it contains a user defined description of the job.
PNODEDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains flow network node definition data (DEFPND cards).
NODEDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains the node definition data (DEFNOD cards).
NODXYZDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains the node location data cards in cartesian coordinates.
MATDAT	PATQ will generate material properties if the material property selected does not exist in the mat.dat file and is in the supplied P/THERMAL database. This file can also be created by direct translation if material properties are specified by the fields function in the Patran model. A mat.dat.apnd file in the model directory will be appended to the mat.dat file in all subdirectories which are spawned from Patran.
CONDUCDAT	This file is generated when a neutral file is translated. It contains the conductive resistor data. This is a binary file. When used with the $INSERT command, the file name should be followed with a “,C” to tell QTRAN that this is a binary conductive resistor data file. For example: “$INSERT CONDUCDAT,C”
FRESDAT	This file is generated when neutral file is translated. It is an ASCII file and contains the flow network resistor data.
CONVECDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains the convective resistor data.
TRARSTDAT	An ASCII radiation interchange file created by the reverse translation of a TRASYS analysis.
NEVRST.DAT	An ASCII radiation interchange file created by the reverse translation of a NEVADA analysis.
RESDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains miscellaneous resistor data, including advective resistor data.
CAPDAT	This file is generated when a neutral file is translated. It contains the capacitor data. This is a binary file. When used with the $INSERT command, the file name should be followed with a “,CAP” to tell QTRAN that this is a binary capacitor data file. For example: “$INSERT CAP.DAT,CAP”
TRAMICDAT	Micro function tables to define the periodic heating on surfaces exposed to solar radiation. This is created by the reverse translation of a TRASYS orbital analysis.
NEVMICDAT	Micro function tables to define the periodic heating on surfaces exposed to solar radiation. This is created by the reverse translation of a NEVADA orbital analysis.
QMCRODAT	This file is generated when a neutral file is translated. It is an ASCII file and contains the QMACRO function heat source data.
TRAQMADAT	This is an ASCII file created by the reverse translation of a TRASYS analysis and relates the micro function data to the QMACRO function heating definition for each surface that receives solar radiation during an orbital flight.
NEVQMADAT	This is an ASCII file created by the reverse translation of a TRASYS analysis and relates the micro function data to the QMACRO function heating definition for each surface that receives solar radiation during an orbital flight.
TMACRODAT	This file is generated when a neutral file is translated. It is an ASCII file and contains the TMACRO function temperature boundary condition data.
MMACRODAT	This file is generated when a neutral file is translated. It is an ASCII file and contains MMACRO function mass flow rate boundary condition data.
PMACRODAT	This file is generated when a neutral file is translated. It is an ASCII file and contains PMACRO function pressure boundary condition data.
TFIXDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains the node numbers of the fixed nodes.
PFIXDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains the nodes numbers for which pressure is fixed.
TEMPDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains the initial temperatures of nodes whose temperatures were assigned with Patran Loads & Boundary Conditions.
PRESSDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains initial pressures of nodes whose pressures were assigned with Patran Loads & Boundary Conditions.
QBASEDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains the constant heat source data for nodes assigned constant heat sources with the Patran Loads & Boundary conditions.
TRQBASDAT	Average heat sources over an orbit defined from the reverse translation of a TRASYS analysis. This file should not be included if the periodic heating is defined.
NEVBASDAT	Average heat sources over an orbit defined from the reverse translation of a NEVADA analysis. This file should not be included if the periodic heating is defined.
MDBASEDAT	This file is generated when a neutral file is translated. It is an ASCII file and contains the constant mass flow rate data for nodes assigned a constant mass flow rate with Patran Loads & Boundary Conditions.
NEWMATDAT	This file is created by PATQ with utility menu pick 11 and contains material property data that has been translated to LCI type material property tables.
TEMPLATEDAT	The template.dat file will be created if materials are defined which are in the P/THERMAL material database but were not defined in the template.dat file. If direct translation is specified and a template.dat.apnd file is supplied in the model create directory, it will be added to the template.dat file when the job is executed.

PATQMSG

This file is a message file that contains all output written to the screen and the users response. This is a standard ASCII text file that is a record of a PATQ session.

PATQSES

This file is a standard ASCII text file that contains the responses of all user request mode by PATQ. This file can be renamed to PATQINP and used for input to future PATQ batch executions. The responses, if different from those used during the creation, would be edited to reflect new desired responses.

QTRANFOR

This file is generated by PATQ from a complete QINDAT file. QTRANFOR is the main program module for QTRAN. QTRANFOR must be compiled and linked with the QTRAN library to generate a new executable QTRAN for each problem.

THERMAL$DIR:[LIBRARY]MPIDMKSBIN,

THERMAL$DIR:[LIBRARY]MPIDIPSBIN,

THERMAL$DIR:[LIBRARY]MPIDFPHBIN, and

THERMAL$DIR:[LIBRARY]MPIDCGSBIN

These files are material property database binary files which can be generated by PATQ utility menu pick 2. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively.

QPLOTTXT

This file is generated by PATQ from the QPLOTDAT file created by QTRAN and converts it from binary to an ASCII file.

NRnnnNRF

These files can be generated by PATQ from a QTRAN QOUTDAT output file. One NRnnnNRF file is generated for each print dump. Normally, this does not have to be done because QTRAN generates these files automatically.

Output columns in the nodal results files.

* These columns are not generated from QOUTDAT files using PATQ menu pick 5.

NFnnnNEU

These files are the Patran neutral files generated by PATQ from a QTRAN QOUTDAT output file, from QTRAN NRnnnNRF nodal results files, or from a temperature interpolation operation.

TITLEDAT

This file provide information about when and what versions of code were used to generate the input file being executed. In addition it contains a user defined description of the job.

PNODEDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains flow network node definition data (DEFPND cards).

NODEDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains the node definition data (DEFNOD cards).

NODXYZDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains the node location data cards in cartesian coordinates.

MATDAT

PATQ will generate material properties if the material property selected does not exist in the mat.dat file and is in the supplied P/THERMAL database. This file can also be created by direct translation if material properties are specified by the fields function in the Patran model. A mat.dat.apnd file in the model directory will be appended to the mat.dat file in all subdirectories which are spawned from Patran.

CONDUCDAT

This file is generated when a neutral file is translated. It contains the conductive resistor data. This is a binary file. When used with the $INSERT command, the file name should be followed with a “,C” to tell QTRAN that this is a binary conductive resistor data file. For example:

“$INSERT CONDUCDAT,C”

FRESDAT

This file is generated when neutral file is translated. It is an ASCII file and contains the flow network resistor data.

CONVECDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains the convective resistor data.

TRARSTDAT

An ASCII radiation interchange file created by the reverse translation of a TRASYS analysis.

NEVRST.DAT

An ASCII radiation interchange file created by the reverse translation of a NEVADA analysis.

RESDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains miscellaneous resistor data, including advective resistor data.

CAPDAT

This file is generated when a neutral file is translated. It contains the capacitor data. This is a binary file. When used with the $INSERT command, the file name should be followed with a “,CAP” to tell QTRAN that this is a binary capacitor data file. For example:

“$INSERT CAP.DAT,CAP”

TRAMICDAT

Micro function tables to define the periodic heating on surfaces exposed to solar radiation. This is created by the reverse translation of a TRASYS orbital analysis.

NEVMICDAT

Micro function tables to define the periodic heating on surfaces exposed to solar radiation. This is created by the reverse translation of a NEVADA orbital analysis.

QMCRODAT

This file is generated when a neutral file is translated. It is an ASCII file and contains the QMACRO function heat source data.

TRAQMADAT

This is an ASCII file created by the reverse translation of a TRASYS analysis and relates the micro function data to the QMACRO function heating definition for each surface that receives solar radiation during an orbital flight.

NEVQMADAT

TMACRODAT

This file is generated when a neutral file is translated. It is an ASCII file and contains the TMACRO function temperature boundary condition data.

MMACRODAT

This file is generated when a neutral file is translated. It is an ASCII file and contains MMACRO function mass flow rate boundary condition data.

PMACRODAT

This file is generated when a neutral file is translated. It is an ASCII file and contains PMACRO function pressure boundary condition data.

TFIXDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains the node numbers of the fixed nodes.

PFIXDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains the nodes numbers for which pressure is fixed.

TEMPDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains the initial temperatures of nodes whose temperatures were assigned with Patran Loads & Boundary Conditions.

PRESSDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains initial pressures of nodes whose pressures were assigned with Patran Loads & Boundary Conditions.

QBASEDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains the constant heat source data for nodes assigned constant heat sources with the Patran Loads & Boundary conditions.

TRQBASDAT

Average heat sources over an orbit defined from the reverse translation of a TRASYS analysis. This file should not be included if the periodic heating is defined.

NEVBASDAT

Average heat sources over an orbit defined from the reverse translation of a NEVADA analysis. This file should not be included if the periodic heating is defined.

MDBASEDAT

This file is generated when a neutral file is translated. It is an ASCII file and contains the constant mass flow rate data for nodes assigned a constant mass flow rate with Patran Loads & Boundary Conditions.

NEWMATDAT

This file is created by PATQ with utility menu pick 11 and contains material property data that has been translated to LCI type material property tables.

TEMPLATEDAT

The template.dat file will be created if materials are defined which are in the P/THERMAL material database but were not defined in the template.dat file. If direct translation is specified and a template.dat.apnd file is supplied in the model create directory, it will be added to the template.dat file when the job is executed.

TCOUPLDAT	This file is generated by direct translation in Patran when temperature coupling boundary conditions have been specified. It contains a node ID and the companion node which is to be used as internal calculation node IDs.
MATDAT	This file is generated by direct translation in Patran when P/THERMAL material properties have been specified in the general fields. A mat.dat.apnd file in the model creation directory will be appended to any material properties specified in the model.
TEMPLATEDAT	This file is generated by direct translation in Patran when P/THERMAL material translation has been selected. A template.dat.apnd file in the model creation directory will be appended to any material definitions specified in the model.
MICRODAT	This file is generated by direct translation in Patran when P/THERMAL microfunctions have been specified in the general fields. A micro.dat.apnd file in the model creation directory will be appended to any micro functions specified in the model.
GAP_CONVECDAT	This file is generated by direct translation in Patran when gap convection or convection between regions is the requested option for the convective boundary condition.
GAP_RADDAT	This file is generated by direct translation in Patran when gap radiation or radiation between regions is the requested option for the radiation boundary condition.

TCOUPLDAT

This file is generated by direct translation in Patran when temperature coupling boundary conditions have been specified. It contains a node ID and the companion node which is to be used as internal calculation node IDs.

MATDAT

This file is generated by direct translation in Patran when P/THERMAL material properties have been specified in the general fields. A mat.dat.apnd file in the model creation directory will be appended to any material properties specified in the model.

TEMPLATEDAT

This file is generated by direct translation in Patran when P/THERMAL material translation has been selected. A template.dat.apnd file in the model creation directory will be appended to any material definitions specified in the model.

MICRODAT

This file is generated by direct translation in Patran when P/THERMAL microfunctions have been specified in the general fields. A micro.dat.apnd file in the model creation directory will be appended to any micro functions specified in the model.

GAP_CONVECDAT

This file is generated by direct translation in Patran when gap convection or convection between regions is the requested option for the convective boundary condition.

GAP_RADDAT

This file is generated by direct translation in Patran when gap radiation or radiation between regions is the requested option for the radiation boundary condition.

../CONVECDATAPND	This file is created by the user and can be used to define any type of conductor that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be pulled into any QTRAN execution that is in a subdirectory associated with the model.
../CAPDATAPND	This file is created by the user and can be used to define capacitors that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be pulled into any QTRAN execution that is in a subdirectory associated with the model.
../MATDATAPND	This file is created by the user and can be used to define material properties that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be appended to any mat.dat file that is created while the job is being spawn for execution.
../TEMPLATEDATAPND	This file is created by the user and can be used to define materials and their associated material properties that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be appended to any template.dat file that is created while the job is being spawn for execution.
../MICRODATAPND	This file is created by the user and can be used to define micro functions that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be appended to any micro.dat file that is created while the job is being spawn for execution.

../CONVECDATAPND

This file is created by the user and can be used to define any type of conductor that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be pulled into any QTRAN execution that is in a subdirectory associated with the model.

../CAPDATAPND

This file is created by the user and can be used to define capacitors that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be pulled into any QTRAN execution that is in a subdirectory associated with the model.

../MATDATAPND

This file is created by the user and can be used to define material properties that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be appended to any mat.dat file that is created while the job is being spawn for execution.

../TEMPLATEDATAPND

This file is created by the user and can be used to define materials and their associated material properties that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be appended to any template.dat file that is created while the job is being spawn for execution.

../MICRODATAPND

This file is created by the user and can be used to define micro functions that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be appended to any micro.dat file that is created while the job is being spawn for execution.

VFINDAT	This file is the main input data file for VIEW FACTOR. It is generated by PATQ from a Patran neutral file. It is a text file.
VFNODEDAT	This file is a VIEW FACTOR output file that contains radiosity nodes generated by VIEW FACTOR. It is a text file.
VFRESDAT	This file is the main VIEW FACTOR output file and contains all of the radiative resistor data generated by VIEW FACTOR for QTRAN. VIEW FACTOR allows this file to be named anything but for now we shall call it VFRESDAT. This file is binary, but may be converted to text by PATQ if desired. The “,RAD” tells QTRAN that this is a binary file and must be used with the $INSERT command. For example: “$INSERT VFRESDAT,RAD”

VFINDAT

This file is the main input data file for VIEW FACTOR. It is generated by PATQ from a Patran neutral file. It is a text file.

VFNODEDAT

This file is a VIEW FACTOR output file that contains radiosity nodes generated by VIEW FACTOR. It is a text file.

VFRESDAT

This file is the main VIEW FACTOR output file and contains all of the radiative resistor data generated by VIEW FACTOR for QTRAN. VIEW FACTOR allows this file to be named anything but for now we shall call it VFRESDAT. This file is binary, but may be converted to text by PATQ if desired. The “,RAD” tells QTRAN that this is a binary file and must be used with the $INSERT command. For example:

“$INSERT VFRESDAT,RAD”

QINDAT	This file is the input data file for QTRAN. QTRAN will honor the command “$INSERT filename” whenever it is encountered in the QINDAT file. QTRAN will also honor a “$RESTART filename next_nnn_value” command, where filename refers to a QTRAN nodal results file (i.e., one of the NRnnnNRF files). This is a text file.
QOUTDAT	This file is the output data file generated by QTRAN. This is a text file. For further information see System Energy Balance, 221.
QPLOTDAT	This file is the output data file generated by QTRAN. This is a binary file which contains specified node temperatures at each converged iteration.
STATBIN	This file is the status file generated by QTRAN. STATBIN is continually updated by QTRAN during execution. This is a binary direct access file that may be accessed with the QSTAT utility.
NRnnnNRF	These files are the Patran nodal results files that QTRAN generates. One NRnnnNRF file is generated for each QTRAN print dump, beginning with NR0DAT and incrementing the “nnn” with each successive print dump. These files may also be used as restart files for QTRAN. These are binary files in standard Patran nodal results file format.
NRnnnASC	These files are the Patran nodal results files that QTRAN generates if the ASCII flag is selected. One NRnnnASC file is generated for each QTRAN print dump, beginning with NR0ASC and incrementing the “nnn” with each successive print dump. These are text files in standard Patran nodal results file format and can be examined with the editor.
NPnnnNRF	These files are the Patran pressure nodal results files that QTRAN generates for the hydraulic nodes. Two values can be put in this file - pressure and net mass flow rate. One NPnnnNRF file is generated for each QTRAN print dump, beginning with NP0NRF and incrementing the “nnn” with each successive print dump. These are binary files in standard Patran nodal results file format.
NPnnnASC	These files are the Patran pressure nodal results files that QTRAN generates for the hydraulic nodes. Two values can be put in this file - pressure and net mass flow rate. One NPnnnASC file is generated for each QTRAN print dump, beginning with NP0ASC and incrementing the “nnn” with each successive print dump. These are text files in standard Patran nodal results file format and can be examined with the editor.
NHnnnNRF	These files are the Patran hydraulic element files that QTRAN generates for the hydraulic network. Four values can be put in this file which represent elemental quantities - mass flow rate, differential head, fluid velocity, and volumetric flow rate. In addition to the selected values, the entrance and exit node number of the element is specified. One NHnnnNRF file is generated for each QTRAN print dump, beginning with NH0NRF and incrementing the “nnn” with each successive print dump. These are binary files in standard Patran nodal results file format.
NHnnnASC	These files are the Patran hydraulic element nodal results files that QTRAN generates for the hydraulic nodes. Four values can be put in this file which represent elemental quantities - mass flow rate, differential head, fluid velocity, and volumetric flow rate. In addition to the selected values, the entrance and exit node number of the element is specified. One NHnnnASC file is generated for each QTRAN print dump, beginning with NH0ASC and incrementing the “nnn” with each successive print dump. These are text files in standard Patran nodal results file format and can be examined with the editor.

QINDAT

This file is the input data file for QTRAN. QTRAN will honor the command “$INSERT filename” whenever it is encountered in the QINDAT file. QTRAN will also honor a “$RESTART filename next_nnn_value” command, where filename refers to a QTRAN nodal results file (i.e., one of the NRnnnNRF files). This is a text file.

QOUTDAT

This file is the output data file generated by QTRAN. This is a text file. For further information see System Energy Balance, 221.

QPLOTDAT

This file is the output data file generated by QTRAN. This is a binary file which contains specified node temperatures at each converged iteration.

STATBIN

This file is the status file generated by QTRAN. STATBIN is continually updated by QTRAN during execution. This is a binary direct access file that may be accessed with the QSTAT utility.

NRnnnNRF

These files are the Patran nodal results files that QTRAN generates. One NRnnnNRF file is generated for each QTRAN print dump, beginning with NR0DAT and incrementing the “nnn” with each successive print dump. These files may also be used as restart files for QTRAN. These are binary files in standard Patran nodal results file format.

NRnnnASC

These files are the Patran nodal results files that QTRAN generates if the ASCII flag is selected. One NRnnnASC file is generated for each QTRAN print dump, beginning with NR0ASC and incrementing the “nnn” with each successive print dump. These are text files in standard Patran nodal results file format and can be examined with the editor.

NPnnnNRF

These files are the Patran pressure nodal results files that QTRAN generates for the hydraulic nodes. Two values can be put in this file - pressure and net mass flow rate. One NPnnnNRF file is generated for each QTRAN print dump, beginning with NP0NRF and incrementing the “nnn” with each successive print dump. These are binary files in standard Patran nodal results file format.

NPnnnASC

These files are the Patran pressure nodal results files that QTRAN generates for the hydraulic nodes. Two values can be put in this file - pressure and net mass flow rate. One NPnnnASC file is generated for each QTRAN print dump, beginning with NP0ASC and incrementing the “nnn” with each successive print dump. These are text files in standard Patran nodal results file format and can be examined with the editor.

NHnnnNRF

These files are the Patran hydraulic element files that QTRAN generates for the hydraulic network. Four values can be put in this file which represent elemental quantities - mass flow rate, differential head, fluid velocity, and volumetric flow rate. In addition to the selected values, the entrance and exit node number of the element is specified. One NHnnnNRF file is generated for each QTRAN print dump, beginning with NH0NRF and incrementing the “nnn” with each successive print dump. These are binary files in standard Patran nodal results file format.

NHnnnASC

These files are the Patran hydraulic element nodal results files that QTRAN generates for the hydraulic nodes. Four values can be put in this file which represent elemental quantities - mass flow rate, differential head, fluid velocity, and volumetric flow rate. In addition to the selected values, the entrance and exit node number of the element is specified. One NHnnnASC file is generated for each QTRAN print dump, beginning with NH0ASC and incrementing the “nnn” with each successive print dump. These are text files in standard Patran nodal results file format and can be examined with the editor.