21.01.2015 Views

COMSOL Multiphysics™

COMSOL Multiphysics™

COMSOL Multiphysics™

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

elepspec<br />

Purpose<br />

elepspec<br />

Declare constraint point patterns.<br />

Syntax<br />

el.elem = 'elepspec'<br />

el.g{ig} = geomnum<br />

el.geom{ig}.ep = meshcases | patterns<br />

meshcases.default = patterns<br />

meshcases.case{elmcase} = patterns<br />

meshcases.mind{elmcase} = caselist<br />

patterns{iptrn} = lagorder | ptrnlist<br />

ptrnlist{2*itype-1} = bmtypename<br />

ptrnlist{2*itype} = lagorder | ptrn<br />

ptrn{ipnt} = lcoords<br />

Description<br />

The elepspec element defines local evaluation point patterns typically used for<br />

pointwise constraints. In contrast to most elements, the elepspec does not have a<br />

geomdim field. The geom field has one entry per geometry listed in the g field and<br />

one subfield, ep, which lists a number of patterns that other elements refer to by<br />

position.<br />

If there are no alternate mesh cases specified, each entry in the ep field is either an<br />

integral number, which is interpreted as a Lagrange point order to be used on all<br />

basic mesh element types and dimensions, or a cell array of pairs of basic mesh<br />

element type and a Lagrange order or an explicit pattern. For a list of basic mesh<br />

element type names, see elshape. Explicit patterns are cell arrays of points in the<br />

local coordinate system on each element, each point being a cell array of the same<br />

dimension as the basic mesh element type.<br />

If there are multiple mesh cases present in the model, the ep field is a struct with<br />

fields default, case, and mind. The default field has the same syntax as described<br />

above for the ep field itself. Multiple alternate cases which need the same evaluation<br />

point patterns can be grouped together using the mind field. This field is a cell array<br />

containing groups of mesh case numbers, each group, caselist, given as a cell<br />

array. For each element mesh case group, elmcase, an alternate pattern specification<br />

is given in the case field.<br />

Cautionary<br />

Currently, there can only be one elepspec element for each geometry, which is<br />

generated by default when converting the standard syntax. Therefore, no additional<br />

elepspec can be added in the fem.elem field unless meshextend is called with<br />

property standard set to off.<br />

72 | CHAPTER 1: COMMAND REFERENCE

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

Saved successfully!

Ooh no, something went wrong!