Fields > Reference fields
Reference fields vs. table fields
Reference fields are similar to table fields except that you can create reference fields only from the results of a prior solve.
The use cases for reference fields and table fields frequently overlap. For example, you could use either a reference field or a table field to define the displacement field needed for a breakout model.
Understanding how reference fields differ from table fields can help you determine which type of field to use. A reference field differs from a table field in the following ways:
A reference field has access to the model geometry and the mesh. Consequently, reference fields tend to be more accurate and less CPU intensive than table fields.
A reference field does not store the actual numerical data. It retrieves data that is already stored in files. This is an important consideration if the field is very large. Reference fields minimize the increase in size of the FEM and Simulation files.
A reference field automatically updates itself if you rerun the model. This is clearly beneficial if you intend to revise and solve a model repeatedly.
A reference field does not allow you to select the interpolation method. Table fields allow you to select from multiple interpolation methods.
A reference field is not saved with the part file. A table field is saved with the part file. Consequently, file management tasks are easier with table fields.
How do I
Create a reference field
Define a boundary condition using a reference field
Use a reference field in a thermal stress analysis
Learn more
Reference fields
Specifying the range of fields created from results
Look up more details
Independent domain options for reference fields
Dependent domain options for reference fields
Quick links
Command reference
Pre/Post video examples
Bulk Entry Descriptions
Simcenter 3D tutorials
Browse Simcenter 3D help by product area
Reference fields vs. table fields, Simcenter 3D 2021.1 Series
© 2020 Siemens
window.mainLanguage="en_US"
window.delivId=""
window.projectId=""
MathJax.Hub.Config({ TeX: { extensions: ["autoload-all.js"] }, tex2jax: { displayMath: [ ] }, "SVG": { scale: 125 } });
Source: https://docs.sw.siemens.com/en-US/doc/289054037/PL20200601120302950.advanced/xid881858 · retrieved 2026-07-17