Specifying How Branches Are Checked

Model Reference Manual

Clash Detection : Specifying How Branches Are Checked

Specifying How Branches Are Checked

BRANCH ACHECK BCHECK

Assuming that the user has not specified NOCHECK BRANCHES (refer to Ignoring Clashes Within Specified Element Types), check for clashes within pipe branches in either of two ways:

•

As a full primitive-by-primitive check of every component within each branch - known as a Type A check (or ACHECK)

•

As a simplified check which ignores the possibility of clashes between certain pairs of components within the branches - known as a Type B check (or BCHECK)

(Clashes between adjacent components and attachments within a Branch are ignored automatically.)

The purpose of the BCHECK option is to eliminate from the clash report spurious clashes that result when zero-length components (such as welds and olets) separate other components or tubing. To specify a BCHECK, the warning message

*** BRANCH CHECKING - OPTION B ***

will be output as part of the report header. This is because, although most of the clashes ignored by Type B checking really are spurious, some genuine clashes may also be ignored. The latter, examples of which are given in Rules Applicable During Type B Checks, will be mostly due to design errors, many of which should have been diagnosed at an earlier stage by means of a data consistency check (refer to Data Consistency Checking).

The default check is the ACHECK option, since this is a fail-safe check for all potential clashes.


Example:
BRANCH B
BRANCH A

Command Syntax:

>--- BRANCh ---+--- Acheck ---.
| |
‘--- Bcheck ----+--->

Q CLASH OPTions

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.