Importing FEMAP
Previous Top Next

To import a FEMAP neutral file, select Files>Import>FEMAP.  Select the FEMAP neutral file from the Open menu and hit the Open button.  There are no options.  The data in the neutral file is converted into a Solaria model.  The FEMAP neutral file must be generated in Version 4.4 or later of the software.  The imported model will be generated in a new Solaria window and automatically drawn to the screen.

Important considerations

Though the user does not see it, Solaria works in absolute temperatures.  In FEMAP, temperature units are not defined, they must be consistent.  When temperatures are imported into Solaria the value assign in Solaria is the defined temperature plus the value defined for the absolute temperature.  If the model contains radiation then it is important that the absolute temperature be defined if units other than degree Kelvin or Rankine are used.  If degrees Celsius are used, define absolute temperature as 273.15.  If degrees Fahrenheit are used, define absolute temperature as 460.0.  If the model does not contain radiation then it is acceptable to define temperatures in Degrees Celsius or Fahrenheit and not define absolute temperature in FEMAP.

Element and Node numbering

All element and node numbering in Solaria is sequential.  Therefore when a FEMAP model with one node is imported, FEMAP node number 20, the Solaria model generated will have 20 nodes. You will see only the one node on the screen and it will have a node number of 20.  The other 19 nodes will be stored in memory but they are flagged as deleted.  If you go to Information>Model>Entire, the number of nodes shown is 1.  This is because deleted elements are not counted.  If a SINDA model is generated of the model, Solaria automatically compacts nodes prior to exporting the SINDA model.  Therefore there will be one node in the SINDA model, node number 1.  After exporting the model to SINDA, the single node number will be 1 and not 20. 

The following summarizes the data of the neutral file which is imported.

Model title - The FEMAP model title is saved as the Solaria model description

Materials/Properties

In Solaria , elements reference the material property directly.  The material property table defines all element properties.  In FEMAP, elements reference property data.  The property data in turn references the material data.  When Solaria reads a FEMAP neutral file, appropriate property data is assigned to the appropriate Solaria material.  When FEMAP elements are converted into Solaria elements, the element property reference is converted to the appropriate material property.  Limitation: There is a limit of 5000 materials and 5000 properties.  The properties and materials can have any numbering but the quantity for each cannot exceed 5000.

The following lists materials and properties which are imported.

Thermal conductivity - Isotropic and anisotropic, can be temperature or time dependent
Specific heat - Can be temperature or time dependent
Density - Can be temperature or time dependent
Temperature - Can be temperature or time dependent
Area for Rod/Bar/Line elements
Plate element thickness - If thickness is different at corner nodes, the numerical average of the four defined thickness’ is used.


Nodes - The X, Y and Z coordinates of nodes.  It is assumed that the node locations are based on the global coordinate system.  No conversions are performed.

Elements imported


FEMAP element            Solaria element             Comments
Line                              Resistor                        Area as factor, thickness, Kx in property table
Tri3                              Plate     
Tri6                              Plate                      Interstitial 3 nodes are not connected to the model
Quad4                          Plate     
Quad8                          Plate                    Interstitial 4 nodes are not connected to the model
Tetra4                          Tetrahedron      
Tetra10                         Tetrahedron      Interstitial 6 nodes are not connected to the model
Wedge6                        Brick     
Wedge15                      Brick                 Interstitial 9 nodes are not connected to the model
Brick8                           Brick     
Brick20                         Brick                 Interstitial 12 nodes are not connected to the model

During the solution of the FEMAP model in Solaria temperatures at the interstitial nodes will not be calculated.  During the export of the Solaria results to FEMAP, temperatures at these interstitial nodes are automatically determined by linearly interpolating between the two adjacent nodes. If the Solaria results are to exported back to FEMAP, it is therefore very important that the nodes NOT be removed by compacting nodes.  Solaria does not have any problems having nodes not attached to the model, it does not slow the solution in any way.  A file is saved to disk with the CON extension during the import of the FEMAP neutral file.  This file contains data which is needed when exporting the results back to FEMAP so therefore must not be deleted.

Loads Imported

Elemental Convection

In FEMAP, a convection "load" is assigned the temperature of the ambient fluid.  In Solaria a separate node defines this temperature.  When a FEMAP convection load is imported a node is automatically generated in Solaria.  The node is defined as a boundary node at the temperature defined for the convection load.  For efficiency, only one node is generated for each different convection ambient temperature.  Therefore, if there are 500 FEMAP convection loads to an ambient temperature of 50C, only one node is generated at a temperature of 50C.  All 500 Solaria convection elements will use this node as the ambient node.  All ambient nodes will be located at X=0.0, Y=0.0, Z=0.0.  The heat transfer coefficient will be assigned to the referenced property table.  The heat transfer coefficient can be temperature or time dependent.  The temperature can also be time dependent.  The Forced Convection option in FEMAP in not translated.

Elemental Radiation

All FEMAP radiation loads are imported as node-to-surface radiation elements.  A node is automatically generated in Solaria when a FEMAP radiation load is imported.  The node is defined as a boundary node at the temperature defined for the radiation load.  For efficiency, only one node is generated for each different radiation ambient temperature.  Therefore, if there are 500 FEMAP radiation loads to an ambient temperature of 50C, only one node is generated at a temperature of 50C.  All 500 TAS radiation elements will use this node as the ambient node.  All ambient nodes will be located at X=0.0, Y=0.0, Z=0.0.  The TAS radiation element will reference the property table where emissivity and view factor are defined.  Absorptivity is not imported. Values for emissivity and view factor must be constant, they cannot reference FEMAP functions. The temperature can  be time dependent.  The FEMAP Enclosure Radiation option is not supported.

Nodal Heat Generation (Type 5 in the FEMAP neutral file)

Nodal Heat Generation in FEMAP is imported as a nodal heat loads in Solaria.  The value of the heat flux is assigned as a constant value unless it references a function in FEMAP.  If so, the nodal heat load references the property table, its value is assigned to the property table and the property table references array data where the function is defined.

Element Heat Flux (Type 14 in the FEMAP neutral file)

A FEMAP element heat generation is imported as a surface heat load in Solaria  The value of the heat flux is assigned as a constant value unless it references a function in FEMAP.  If so, the surface heat load references the property table, its value is assigned to the property table and the property table references array data where the function is defined.

Element Heat Generation (Type 13 in the FEMAP neutral file)

A FEMAP element heat flux is imported as a volumetric heat load in Solaria  The value of the heat flux is assigned as a constant value unless it references a function in FEMAP.  If so, the volumetric heat load references the property table, its value is assigned to the property table and the property table references array data where the function is defined.

Boundary nodes

In FEMAP, boundary nodes can be defined at the nodal level or by the element.  In Solaria, boundary nodes can only be defined at the nodal level.  When element boundary temperatures are imported, the nodes associated with the element are defined as boundary nodes.  Unless the boundary temperature references a function in FEMAP, the boundary node is assigned a constant temperature.  The temperature assigned is the temperature defined in FEMAP plus the value of the absolute value defined in FEMAP.  If the boundary temperature references a function in FEMAP, the boundary node in Solaria will reference the property table.  The property table will in tern reference the array data where the function is defined.

Functions

FEMAP functions are imported as array data.  The functions are renumbered to be sequential as read from the FEMAP neutral file.  Limitation: There is a limit of 5000 functions.  The functions can have any numbering but the total quantity cannot exceed 5000.  Only type 1, Time dependent, and type 2, Temperature dependent, functions are imported.  There is no limit to the number of data pairs.

Coordinate Systems

No FEMAP coordinate systems are imported.  All materials and nodes must be based on the global cartesian coordinate system.