vsbv#
- Booleans.vsbv(nv1='', nv2='', sepo='', keep1='', keep2='', **kwargs)#
Subtracts volumes from volumes.
Mechanical APDL Command: VSBV
- Parameters:
- nv1
str Volume (or volumes, if picking is used) to be subtracted from. If ALL, use all selected volumes. Volumes specified in set
NV2are removed from setNV1. If P, graphical picking is enabled (valid only in the GUI) and remaining fields are ignored. A component name may also be substituted forNV1.- nv2
str Volume (or volumes, if picking is used) to subtract. If ALL, use all selected volumes (except those included in the
NV1argument). A component name may also be substituted forNV2.- sepo
str Behavior if the intersection of the
NV1volumes and theNV2volumes is an area or areas:(blank)- The resulting volumes will share area(s) where they touch.SEPO- The resulting volumes will have separate, but coincident area(s) where they touch.
- keep1
str Specifies whether
NV1volumes are to be deleted:(blank)- Use the setting ofKEEPon the boptn command.DELETE- DeleteNV1volumes after vsbv operation (override boptn command settings).KEEP- KeepNV1volumes after vsbv operation (override boptn command settings).
- keep2
str Specifies whether
NV2volumes are to be deleted:(blank)- Use the setting ofKEEPon the boptn command.DELETE- DeleteNV2volumes after vsbv operation (override boptn command settings).KEEP- KeepNV2volumes after vsbv operation (override boptn command settings).
- nv1
Notes
Generates new volumes by subtracting the regions common to both
NV1andNV2volumes (the intersection) from theNV1volumes. The intersection can be a volume(s) or area(s). If the intersection is an area andSEPOis blank, theNV1volume is divided at the area and the resulting volumes will be connected, sharing a common area where they touch. IfSEPOis set to SEPO,NV1is divided into two unconnected volumes with separate areas where they touch. See the Modeling and Meshing Guide for an illustration. See the boptn command for an explanation of the options available to Boolean operations. Element attributes and solid model boundary conditions assigned to the original entities will not be transferred to the new entities generated. vsbv,ALL,ALL will have no effect because all the volumes in setNV1will have been moved to setNV2.