AUTO_PRIORITY Statement

The AUTO_SELECT statement specifies the bevel types that should be selected within a certain set and range as the connection angle varies. It might then happen that along one contour the angle varies in such a way that the contour should be divided into intervals with different bevel codes. Suppose that the following AUTO_SELECT statements have been defined for one range within one set:

AUTO_SELECT /BEVEL=111/ INT=( 0,15), ....;
AUTO_SELECT /BEVEL=222/ INT=(15,30), ....;
AUTO_SELECT /BEVEL=333/ INT=(30,90), ....;

Further suppose that the connection angle varies between 0 and 45 degrees.

The contour should then have been divided into bevel intervals as indicated by the figure below

Figure 1:57. Bevels according to variation of connection angle.

However, currently AVEVA Marine has no support for automatic partition of an "unbroken" contour into intervals with different bevels.

(If, on the other hand, the contour is "broken" into pieces by for example, notches and cutouts, then these pieces are treated as independent intervals. If, in the example above, the contour would have been interrupted by notches the result might have become as shown in the figure below

Figure 1:58. Actually selected bevels in case with notches.

Another alternative is also to define different bevel intervals already in the initial bevel definition in the modelling function.)

We now return to the initial situation in the first figure above. Since AVEVA Marine currently does not divide the contour into intervals - which bevel code will then be selected? The default rule for selection is that the bevel code will be selected which covers the largest angle interval along the contour (however, if one of the bevel codes results from a gap selection, this bevel code will never be selected).

(The result of the bevel selection may be that the connection angle in the whole interval may exceed the allowed limits for the bevel code and that is where the MIN/MAX attributes of the AUTO_SELECT statement will become useful.)

However, the customer may set up rules to control the selected bevel code, and that is done by the AUTO_PRIORITY statement which is described below.

Syntax:

SET and RANGE must be given if there is more than one of them.

The "cases" (<case_1>,<case_2>, ) are those, optionally defined in the AUTO_SELECT statement. If a combination of cases according to the list in the statement above has been found along one contour interval then the first of the given cases, that means, <case_1> will be used. The number of cases may vary in the range 2 to 5. For a certain case to be selected there must be a "hit" on all cases in the same statement, otherwise the default rule above will be applied. The order of the "cases" in the statement is arbitrary (apart from the first one). Any number of AUTO_PRIORITY statements may be given, covering all possible combinations of "cases".