The selective subcycling method in Abaqus/Explicit is based on domain decomposition. In this method subcycling zones are defined that remain unchanged during the analysis. The domain-level parallelization method (“Parallel execution in Abaqus/Explicit,” Section 3.5.3) is invoked automatically when subcycling zones are defined. Each subcycling zone, as well as the non-subcycling zone, is independently decomposed into the user-specified number of parallel domains. The “master” domains are defined as the parallel domains that are derived from the non-subcycling zone and are integrated with the largest stable time increment. The remaining parallel domains derived from the subcycling zones are integrated using smaller time increments, or “subcycles.”

The subcycle time increment sizes are chosen as integer divisors of the time increment used in the master parallel domains. Therefore, all parallel domains exactly reach the same time points as the master parallel domains. During subcycling, nodes that lie on the interface with the non-subcycling zone require special treatment. The velocity at the interface nodes is taken from the non-subcycling zone and is constant during subcycles. This produces an interface node displacement field that varies linearly during the subcycles.

Subcycling zones are defined by element sets. You can include all element types in these sets except Eulerian element types EC3D8R and EC3D8RT. However, all parallel domains must have at least one deformable element to provide the stable time increment. Abaqus/Explicit issues an error message if there is no deformable element in a parallel domain. You can define an arbitrary number of subcycling zones. However, some modeling features cannot be split between subcycling zones. Abaqus/Explicit automatically merges subcycling zones that contain features that cannot be split. Subcycling zones are merged together when:

• the zones overlap;

• the zones share the same nodes;

• a node is in one subcycling zone, but its adjacent nodes are in a different subcycling zone;

• subcycling zones are involved in the same constraint equation, connector, or rigid body; or

• general contact is specified in the analysis.

When subcycling zones are merged, the smallest stable time increment among the merged zones is used. The constraint, connector, or rigid body is always assigned to the subcycling zone if any one of its nodes is involved in that subcycling zone. Since the domain-level parallelization method is used, all restrictions on parallel domain decomposition apply to subcycling zones. These restrictions prevent certain features from being split across master parallel domains, as well as parallel domains that contain the subcycling zones (See “Parallel execution in Abaqus/Explicit,” Section 3.5.3). Analytical rigid surfaces cannot be included in the general contact domain when a subcycling zone is defined.

Efficient selective subcycling requires proper choice of subcycling zones. For each subcycling zone, the time increment size should be small compared to the non-subcycling zone, producing a large number of subcycles. The number of subcycles is the ratio of the stable time increment size in the non-subcycling zone to the stable time increment sizes in the subcycling zones. In addition to a large number of subcycles, the number of elements in a subcycling zone should generally be small compared to the total number of elements in the model for optimal performance benefit. If a majority of elements in the model are in subcycling zones, there will not be much performance benefit.

*SUBCYCLING, ELSET=element_set_name

The subcycling algorithm used in Abaqus/Explicit provides sufficient accuracy for most complex dynamic models. However, because of the relatively large time increment size used in the non-subcycling zone and the interpolation used on zone interface nodes, subcycling solutions can introduce a truncation error, which may slightly alter results compared with traditional solutions. This error should not affect the overall dynamic behavior of the model. Special attention should be given to the interface between the subcycling zone and non-subcycling zone when general contact (see “Defining general contact interactions in Abaqus/Explicit,” Section 36.4.1) is involved. It is not necessary to define a pair of surfaces that have the potential for contacting each other within the same zone. However, to minimize truncation errors, it is highly recommended that a single surface that has the potential for contacting others not be split across the zones.

Output (see “Output,” Section 4.1.1) and mass scaling (see “Mass scaling,” Section 11.6.1) are always performed at the same time points reached by all parallel domains.

The selective subcycling method in Abaqus/Explicit is based on domain decomposition. In this method subcycling zones are defined that remain unchanged during the analysis. The domain-level parallelization method (“Parallel execution in Abaqus/Explicit,” Section 3.5.3) is invoked automatically when subcycling zones are defined. Each subcycling zone, as well as the non-subcycling zone, is independently decomposed into the user-specified number of parallel domains. The “master” domains are defined as the parallel domains that are derived from the non-subcycling zone and are integrated with the largest stable time increment. The remaining parallel domains derived from the subcycling zones are integrated using smaller time increments, or “subcycles.”

The subcycle time increment sizes are chosen as integer divisors of the time increment used in the master parallel domains. Therefore, all parallel domains exactly reach the same time points as the master parallel domains. During subcycling, nodes that lie on the interface with the non-subcycling zone require special treatment. The velocity at the interface nodes is taken from the non-subcycling zone and is constant during subcycles. This produces an interface node displacement field that varies linearly during the subcycles.

Subcycling zones are defined by element sets. You can include all element types in these sets except Eulerian element types EC3D8R and EC3D8RT. However, all parallel domains must have at least one deformable element to provide the stable time increment. Abaqus/Explicit issues an error message if there is no deformable element in a parallel domain. You can define an arbitrary number of subcycling zones. However, some modeling features cannot be split between subcycling zones. Abaqus/Explicit automatically merges subcycling zones that contain features that cannot be split. Subcycling zones are merged together when:

• the zones overlap;

• the zones share the same nodes;

• a node is in one subcycling zone, but its adjacent nodes are in a different subcycling zone;

• subcycling zones are involved in the same constraint equation, connector, or rigid body; or

• general contact is specified in the analysis.

When subcycling zones are merged, the smallest stable time increment among the merged zones is used. The constraint, connector, or rigid body is always assigned to the subcycling zone if any one of its nodes is involved in that subcycling zone. Since the domain-level parallelization method is used, all restrictions on parallel domain decomposition apply to subcycling zones. These restrictions prevent certain features from being split across master parallel domains, as well as parallel domains that contain the subcycling zones (See “Parallel execution in Abaqus/Explicit,” Section 3.5.3). Analytical rigid surfaces cannot be included in the general contact domain when a subcycling zone is defined.

Efficient selective subcycling requires proper choice of subcycling zones. For each subcycling zone, the time increment size should be small compared to the non-subcycling zone, producing a large number of subcycles. The number of subcycles is the ratio of the stable time increment size in the non-subcycling zone to the stable time increment sizes in the subcycling zones. In addition to a large number of subcycles, the number of elements in a subcycling zone should generally be small compared to the total number of elements in the model for optimal performance benefit. If a majority of elements in the model are in subcycling zones, there will not be much performance benefit.

*SUBCYCLING, ELSET=element_set_name

The subcycling algorithm used in Abaqus/Explicit provides sufficient accuracy for most complex dynamic models. However, because of the relatively large time increment size used in the non-subcycling zone and the interpolation used on zone interface nodes, subcycling solutions can introduce a truncation error, which may slightly alter results compared with traditional solutions. This error should not affect the overall dynamic behavior of the model. Special attention should be given to the interface between the subcycling zone and non-subcycling zone when general contact (see “Defining general contact interactions in Abaqus/Explicit,” Section 36.4.1) is involved. It is not necessary to define a pair of surfaces that have the potential for contacting each other within the same zone. However, to minimize truncation errors, it is highly recommended that a single surface that has the potential for contacting others not be split across the zones.

Output (see “Output,” Section 4.1.1) and mass scaling (see “Mass scaling,” Section 11.6.1) are always performed at the same time points reached by all parallel domains.