!PARTITION¶

line 1¶

!PARTITION, TYPE=<type>, METHOD=<method>, DOMAIN=<domain> [, optional parameter]

Parameter
TYPE	Domain division type (required)
METHOD	Domain decomposition method (required)
DOMAIN	Number of division (required)
DEPTH	Overlap depth (optional)
UCD	Output UCD file for the segmented image (optional)
CONTACT	Contact node handling in domain decomposition (optional)
CONTACT_OWNER	Ownership scheme for parallel contact (optional)

Parameter	Parameter value	Contents
TYPE	NODE-BASED	node-based division
	ELEMENT-BASED	element-based division
METHOD	RCB	RCB method, the division reference axis must be specified on line 2
	KMETIS	kMETIS
	PMETIS	pMETIS
DOMAIN		number of divisions
DEPTH		The overlap depth of the partial region (DEPTH=1 if omitted) Cannot be specified when TYPE=ELEMENT-BASED
UCD		UCD file name (can be abbreviated)
CONTACT	DEFAULT	Perform domain decomposition without considering contact nodes (same as SIMPLE)
	AGGREGATE	Assign master and slave surfaces to the same subdomain
	DISTRIBUTE	Distribute the nodes of the master surface evenly to each subdomain
	SIMPLE	Perform domain decomposition without considering contact nodes (same as DEFAULT)
CONTACT_OWNER	MASTER	Master-owner scheme (default). The master surface is split by the domain owning each element, and the slave nodes are replicated to every domain holding part of that master surface
	SLAVE	Slave-owner scheme. Each slave node is held only by the domain that owns it, and that domain receives the whole master surface Can only be specified when TYPE=NODE-BASED

CONTACT and CONTACT_OWNER are independent parameters and may be combined freely.

CONTACT_OWNER¶

Selects which domain is responsible for which part of a contact pair in a parallel contact analysis.

MASTER (the default) splits the master surface by the domain owning each element and replicates the slave nodes to every domain that holds part of that master surface. Duplicate contact candidates are arbitrated by a reduction across domains.

SLAVE inverts this. Each slave node is held only by the domain that owns it, and that domain receives the whole master surface of the pair. In a finite sliding analysis (INTERACTION=FSLID of !CONTACT) a slave node can slide across a domain boundary of the master surface. Under MASTER the adjacency of the master surface is built per domain only, so the neighbour search is cut at the boundary: the slave node is judged out of contact for one step and its Lagrange multiplier and friction history are lost. Under SLAVE the master surface needed for the search is always present in the same domain, so this does not happen and the solution does not depend on the number of domains.

A domain specified with SLAVE holds the whole master surface, so its memory usage and its number of neighbouring domains increase. It cannot be combined with TYPE=ELEMENT-BASED.

Line 2 (required only if METHOD=RCB)¶

(Line 2) DIR1, DIR2, DIR3, ... (Specify the number of installments)

variable name	attribute	contents
DIRX	C	Division reference axis (specified by lowercase x, y, or z)

Example of a control file¶

Example 1

!PARTITION, TYPE=NODE-BASED, METHOD=RCB, DOMAIN=8, DEPTH=1, UCD=mesh.inp
x, y, z

Example 2

!PARTITION, TYPE=ELEMENT-BASED, METHOD=PMETIS, DOMAIN=32

Example 3 (finite sliding contact analysis)

!PARTITION, TYPE=NODE-BASED, METHOD=PMETIS, DOMAIN=8, CONTACT_OWNER=SLAVE