Input files
Input files need to be created by user prior to the conversion. Files can be exported/generated from user’s FEA software. This page shows the file structure for all pdfPost input files.
Elements File
Nodes File
Components File
Values File
Displacements File
Symbols File
Elements File
Contains finite element information (element number, type, nodes) as a comma-separated value.
// Example
1,1,1,3 //LINE ELEMENT
2,1,3,4,0,0,0,0,0,0,0,0 //LINE ELEMENT
3,2,145,146,154,162 //PLANE ELEMENT
4,2,162,154,153,161,0,0,0,0,0,0 //PLANE ELEMENT
5,3,1352,1351,1469,1468,1827,1828,1762,1761,0,0 //SOLID ELEMENT
6,3,1827,1828,1762,1761,916,917,1781,1780 //SOLID ELEMENT
Remarks:
- order of node numbers is important especially for SOLID elements. Details can be found in Supported Elements section
- elementType should be properly defined in Project Properties – Element
- no additional data (comments etc.) is allowed
- one Elements File is required for single pdfPost project
Nodes File
Contains node numbers and coordinates. All the node numbers listed in Elements File should be stored here.
// Example
1,-0.165,-2.39568586,1.5462205
2,-1.54622108,-2.39568586,0.165
3,-0.228479909,-2.39568586,1.53812249
4,-0.29157285,-2.39568586,1.52741878
5,-0.354172154,-2.39568586,1.51412911
Remarks:
- <single> stands for Single-precision floating-point (4 bytes = 32 bits) with period ‘.’ (never a comma) as the decimal mark
- if nodes given in Elements File are not defined within Nodes File, converter will produce an error and conversion will stop
- no additional data (comments etc.) is allowed
- one Nodes File is required for single pdfPost project
Components File
Contains the definitions of element groups.
firstElementNumber<Int>
secondElementNumber<Int>
…
lastElementNumber<Int>
// Example
Group1,ELEMENTS
1
2
3
Group2,ELEMENTS
4
5
60
70
Group3,ELEMENTS
90
Remarks:
- componentType is to be “ELEMENTS”
- componentName corresponds with Name in Project properties – Component.
- no additional data (comments etc.) is allowed
- at least, one Components File is required for single pdfPost project
Values File
Contains elemental or nodal values. Based on this file content, element colors are generated. Based on type of the result, values file has different format:
Elemental values:
// Example
1,-45.05
2,156.45
3,0.00
4,0.0045
Nodal values:
// Example
1,-45.05, -35.08, -30.25
2,156.45, 223.48, 456.44, 184.12
3,0.00,0.00,0.00,0.00
4,0.0045,0.0085,0.0012,0.0036,0.01,0.153
Remarks:
- <single> stands for Single-precision floating-point (4 bytes = 32 bits) with period ‘.’ (never a comma) as the decimal mark
- values not defined within this file will be set to 0.00 by default
- no additional data (comments etc.) is allowed
- multiple Values Files can be used for single pdfPost project (multiple plots within one PDF document). Please check Project Properties – Plot
Displacements File (optional)
Contains node numbers and corresponding displacement values.
// Example
1,-0.165,-0.395,0.546
2,-0.546,-0.566,0.165
3,-0.228,-0.395,0.538122
4,-0.2915,-0.86,0.2778
5,-0.3541,-0.586,0.2911
Remarks:
- <single> stands for Single-precision floating-point (4 bytes = 32 bits) with period ‘.’ (never a comma) as the decimal mark
- no additional data (comments etc.) is allowed
- Displacement Files can differ for each plot. If deformation is disabled (0), no Displacements File is required
Symbols File (optional)
Contains node numbers and corresponding displacement values.
// Example
1,UX,15.5,BCs
2,UY,20.5,BCs
3,FZ,255.48,Forces
4,FY,-15.4,Forces
5,MASS,1500.0,Masses
Remarks:
- <single> stands for Single-precision floating-point (4 bytes = 32 bits) with period ‘.’ (never a comma) as the decimal mark
- no additional data (comments etc.) is allowed
- Symbol Files can differ for each plot. symbolName string has to be defined in SymbolDefinitions xml