21.01.2015 Views

COMSOL Multiphysics™

COMSOL Multiphysics™

COMSOL Multiphysics™

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

multiphysics<br />

appl.dim provides the dependent variable names. The default is obtained from the<br />

application mode for physics modes. For PDE modes with no mode field and with<br />

a numeric appl.dim, default variable names are substituted according to the global<br />

position in the system.<br />

appl.elemdefault contains a string indicating what kind of element is the default<br />

in this application. This method is used to generate the defaults for<br />

appl.XXX.gporder, appl.XXX.cporder, appl.shape, appl.XXX.shape, and<br />

appl.sshape. See elemdefault for a list of valid strings.<br />

appl.edg is a structure with fields describing the edge data. The structure contains<br />

one field for each of the application-specific edge parameters, with the field name<br />

equal to the parameter name. Each field should be a cell array containing data for<br />

the edges.<br />

appl.equ is a structure with fields describing the PDE data on subdomains. The<br />

structure contains one field for each of the application-specific PDE parameters,<br />

with the field name equal to the parameter name. Each field should be a cell array<br />

containing data for the subdomains.<br />

appl.mode is a string with the name of the application mode or an application mode<br />

object. If the appl.mode field is omitted, the application structure can be used to<br />

describe ordinary coefficient/general/weak form PDE problem. This is useful in<br />

the definition of multiphysics problems, where coefficient/general/weak form<br />

models can be combined with application mode models. See the <strong>COMSOL</strong><br />

Modeling Guide for a description of the application-specific data for each<br />

application mode.<br />

appl.pnt is a structure with fields describing the point data. The structure contains<br />

one field for each of the application-specific point parameters, with the field name<br />

equal to the parameter name. Each field should be a cell array containing data for<br />

the points.<br />

appl.shape is a cell array of shape function objects.<br />

appl.sshape is an integer giving the order of geometry approximation.<br />

The fields fem.XXX.shape and fem.xxx.shape are ind-based cell arrays of vectors<br />

pointing to elements of appl.shape. Indicates which shape functions to use in each<br />

domain group. An empty vector indicates that no shape functions are used in this<br />

domain group. Zero indicates that the affected domain group should use defaults<br />

or inherit shape functions. Appl.XXX.shape takes defaults, whereas<br />

appl.xxx.shape inherits from appl.XXX.shape. Where there is a conflict over<br />

306 | CHAPTER 1: COMMAND REFERENCE

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!