Перейти до змісту

Translation status

This page has not yet been translated into Ukrainian, or its translation is out of date. The current English version is shown as a fallback.

!PARTITION

Line 1

!PARTITION, TYPE=<type>, METHOD=<method>, DOMAIN=<domain> [, optional parameter]
Parameter
TYPE Domain decomposition type (required)
METHOD Domain decomposition method (required)
DOMAIN Number of domains (required)
DEPTH Overlap depth (optional)
UCD Output of a UCD file for the domain decomposition image (optional)
CONTACT Handling of contact points in domain decomposition (optional)
CONTACT_OWNER Ownership scheme for parallel contact (optional)
Parameter Parameter Value Description
TYPE NODE-BASED Node-based decomposition
ELEMENT-BASED Element-based decomposition
METHOD RCB RCB method; the decomposition reference axes must be specified on line 2
KMETIS kMETIS
PMETIS pMETIS
DOMAIN Number of domains
DEPTH Overlap depth of subdomains (DEPTH=1 if omitted)
Cannot be specified when TYPE=ELEMENT-BASED
UCD UCD file name (optional)
CONTACT DEFAULT Perform ordinary domain decomposition without considering contact points (handled the same as SIMPLE)
AGGREGATE Assign the master and slave surfaces to the same subdomain
DISTRIBUTE Distribute the nodes on the master surface evenly among the subdomains
SIMPLE Perform ordinary domain decomposition without considering contact points (handled the same as DEFAULT)
CONTACT_OWNER MASTER Master-owner scheme (default). Partition the master surface by element-owning domains and replicate slave nodes to each master-owning domain
SLAVE Slave-owner scheme. Retain each slave node only in its owning domain and place the entire master surface in that domain
Can be specified only when TYPE=NODE-BASED

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

CONTACT_OWNER

In parallel contact analysis, this parameter specifies which domain is responsible for which part of a contact pair.

MASTER (default) partitions the master surface by the domains that own its elements and replicates slave nodes to all domains containing the master surface. Duplicate contact candidates are reconciled by aggregation across domains.

SLAVE reverses this arrangement. Each slave node is retained only by the domain that owns it, and that domain receives the entire master surface of the contact pair. With finite sliding (INTERACTION=FSLID on !CONTACT), a slave node may slide across a domain-partition boundary on the master surface. Under MASTER, master-surface adjacency is constructed only within each domain, so the adjacency search can be interrupted at the boundary; the slave node can then be judged temporarily out of contact, causing the Lagrange multiplier and friction history to be lost. Under SLAVE, the master surface required for the search is always available within the same domain, so this problem does not occur and the solution does not depend on the number of domains.

Because a domain specified with SLAVE retains the entire master surface, its memory usage and number of neighboring domains increase. It cannot be used together with TYPE=ELEMENT-BASED.

Line 2 (required only for METHOD=RCB)

(Line 2) DIR1, DIR2, DIR3, ... (specify for the number of decompositions)
Variable Name Attribute Description
DIRX C Decomposition reference axis (specified using lowercase x, y, or z)

Control File Examples

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
AI-assisted translation May contain errors Official docs Status