HeatSourceAssignment Properties

(To be removed) Heat source assignments

HeatSourceAssignment will be removed. Use the CellLoad and FaceLoad properties of femodel instead. (since R2023a) For more information on updating your code, see Version History.

A HeatSourceAssignment object contains a description of the heat sources for a thermal model. A ThermalModel container has a vector of HeatSourceAssignment objects in its HeatSources.HeatSourceAssignments property.

Create heat source assignments for your thermal model using the internalHeatSource function.

Properties

RegionType — Region type

'Face' | 'Cell'

Region type, specified as 'Face' for a 2-D region, or 'Cell' for a 3-D region.

Data Types: char | string

RegionID — Region ID

vector of positive integers

Region ID, specified as a vector of positive integers. To determine which ID corresponds to which portion of the geometry, use the pdegplot function. Set the 'FaceLabels' name-value pair to 'on'.

Data Types: double

HeatSource — Heat source value

number | function handle

Heat source value, specified as a number or a function handle. A heat source with a negative value is called a heat sink.

Data Types: double | function_handle

Label — Label for use with linearizeInput

character vector | string

Label for use with linearizeInput, specified as a character vector or a string.

Data Types: char | string

Version History

Introduced in R2017a

R2025a: To be removed

HeatSourceAssignment will be removed. Use the CellLoad and FaceLoad properties of femodel instead.

For example, you can check the heat sources for faces of a 2-D geometry as follows.

model = femodel(AnalysisType="thermalSteady", ...
                Geometry=@lshapeg);
model.FaceLoad(1) = faceLoad(Heat=10);
model.FaceLoad(2) = faceLoad(Heat=20);
model.FaceLoad(3) = faceLoad(Heat=30);
model.FaceLoad

The unified finite element model workflow defines the type of a problem and all of its parameters as the properties of an femodel object. This object enables you to specify physical parameters for structural, thermal, and electromagnetic types of analyses. The solver in the unified workflow uses only the parameters (properties) appropriate for the current analysis type while ignoring all other properties. If you switch the analysis type by setting the AnalysisType property of the model, the solver uses the appropriate set of properties corresponding to the new analysis type.

For more help migrating your existing code that uses ThermalModel to the unified finite element workflow, see Migration from Domain-Specific to Unified Workflow.