Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Hull and Outfitting

Panel Modelling

  • Last UpdatedDec 08, 2025
  • 7 minute read

ATTACH_COPY = <action>

  • Controls the handling of attachments on panel component groups when the groups are copied or regenerated. Attachments are not part of the core definition or the scheme language and thus require special handling. It can for example, be user-defined attributes.

  • The possible values of <action> are:

    NONE

    The attachments are removed when the components are copied or regenerated.

    ALL_MATCH

    The attachments are copied or preserved at regeneration if all the components identities match within the group.

    MATCH

    The attachments are copied and preserved at regeneration for the components with identities that match.

    MATCH_COPY

    As MATCH but if no matching identity is found for a component it gets the attachments of the last component.

ATTACH_COPY_MSG = <action>

  • Controls the warning message level when attachments are handled.

  • The possible values of <action> are:

    NO

    Never warn.

    NCOMP

    Warn only when the number of components do not match.

    MATCH

    As NCOMP but also warn when the component identities do not match.

    YES

    Always warn when attachments are copied/preserved.

AUTO_TAG

  • If AUTO_TAG is defined, then the stiffener dialog will include an automatic suggestion for tag numbers.

BOU_HL_COL = <colour>

  • When a panel is currently modelled, it is highlighted in the Planar Hull Modelling views by an enlarged boundary. The color of this can be controlled by this parameter.

  • The possible values are: GREEN, BLACK, CYAN, BLUE, MAGENTA, RED, YELLOW, WHITE and NONE.

BRIDGE_WIDTH = <width>

  • The default width for the bridge of a bridged hole.

  • Default value is 100.

BRIDGE_RADIUS = <radius>

  • The default radius for the bridge corners of a bridged hole.

  • Default value is 15.

CHAMFER_ADJUST=<dist>

  • If not given (or < 0) no consideration to chamfer in bounding panels is taken even if the bevel set-up would indicate that there should be.

  • <dist> = 99 means that any chamfer in the connection point between bounding panels will be considered as specified in the bevel set-up. If a bevel definition file is available this setting is strongly recommended.

  • Otherwise, <dist> >=0 means that <dist> is a real number, defining the slope of the chamfer (that means, using the number 3 denotes the slope 1:3) in case there should be any. If the number is not between 0.5 and 10, the slope 1:4 will be used as default.

CHAMFER_STEP=<thick-diff>

  • This parameter controls the minimum plate thickness step between abutting bounding panels that is required in order for chamfer to be applied. that means, if the thickness difference exceeds this value a "chamfer slope" will be created between the two panels with a slope as defined by CHAMFER_ADJUST.

  • If not given, the default 3 mm will be used.

  • If CHAMFER_ADJUST = 99 then this parameter is irrelevant

CHECK_BUILD = <act>

  • When sister ships are built, schemes may be copied between the different projects. To ensure that the correct scheme is run in the correct project, a keyword BUI can be given in the panel statement. CHECK_BUILD is an activity that can be set to either warn if the scheme is in the correct project or to reject the scheme in case the scheme is not updated for the current project.

  • The strings that are compared is the string in the keyword BUI (in the panel statement) and the project name set in the Structure Reference Object (in Inithull).

    0

    No check.

    1

    Check only if keyword BUI is set in panel statement. If so it must be equal to project in current ship.

    2

    Always check. BUI must be set in panel statement and must be equal to project in current ship.

COM_KNU_SELECT = <action>

  • Controls the selection of knuckled panel, COM_KNU_SELECT will default be set to MAIN.

  • The possible values of <action> are:

    MAIN

    When activating a knuckled panel the main panel will be activated.

    SUB

    When activating a knuckled panel the indicated sub panel will be active.

    ASK

    When activating a knuckled panel user will be prompted by a multiple choice dialog, where user either can choose Main panel or Sub panel.

CORNER_NOTCH_CHECK = <action>

  • When defined, each new defined corner notch will be checked against already defined corner notches to verify that there is no duplicate definition.

  • Possible values of <action> are:

    YES

    Check

    NO

    No check

DEF_QUAL_OUT

  • IF set, the default quality code will be written into the scheme Default: Not set

EARLY_DESIGN

  • Used in the early design phase to suppress warning messages, for example, when a new panel is generated with a name coinciding with an existing panel or, when no endcut date is given for stiffeners.

GEN_VIEW = <view>

  • Controlling whether a single view or all views are used when drawing a panel generation receipt picture.

  • Possible values of <view> are:

    SINGLE

    Draw only in single view selected by the user

    ALL

    Draw in all relevant views

HOOK_GAP = <gap>

  • The default gap for the hook of a hooked hole.

  • Default value is 25.

HOOK_RADIUS = <radius>

  • The default radius for the hooks of a hooked hole.

  • Default value is 15.

POSNO_PREFIX

POSNO_SUFFIX

PROF_BUNDLE

EXTENSION = <view>

  • This parameter controls the handling of input schemes.

  • Default file type for input schemes.

LSTSCH

  • This parameter controls the handling result lists.

  • When given, the receipt list from panel modelling will be stored in the same directory as the input schemes.

NO_OF_ANG_DEC

  • 0-9 (default 9).

  • Enables the user to control the number of decimals for angles in the scheme.

NO_OF_COORD_DEC

  • 0-9 (default 9).

  • Enables the user to control the number of decimals for coordinates in the scheme.

NOLOCK

  • Do not set. For educational purposes only.

PANPOS_VIEW

  • When panel location is to be fetched from an existing view the panel location will be set to the same as the view definition. Normal cases is that for principle axis definition and the "Looking" is set as For, SB or Top, the panel location will be defined with full definition that means, with ORI, UAX and VAX.

  • If PANPOS_VIEW is set to YES, this will be overridden and the panel location will, if possible, be set to the principle plane (X, Y or Z).

REDUCE_HOOKS

  • When a panel section is used as a boundary of another panel the resulting section contour(s) are extended outside the actual panel by "hooks" in order to ensure intersections with neighboring boundaries also in cases with complicated geometry and especially when two panel boundaries are parallel to each other.

  • These hooks are added automatically unless CHAMFER_ADJUST = 99.

  • When REDUCE_HOOKS is given the hooks will be added only when really needed, that means, when two adjacent panel boundaries are parallel (or close to parallel). In all other cases the hooks will be replaced by extensions of the boundary contours in the direction of the end tangent. The length of this extension is 1000 mm.

  • REDUCE_HOOKS is irrelevant when CHAMFER_ADJUST = 99 (see above) since then no hooks have been added.

SCH_CREATE

  • When given, and the function "Panel Store" is used, the input scheme will be created from the panel. This is only done if the panel has been changed without having the scheme updated.

SCH_DELETE

  • When given, and the function "Panel Delete on DB" is used, the input scheme is also deleted together with the panel.

SEAM_NOTCH_CHECK = <action>

  • When defined, each new defined notch that is referring a seam will be checked that there is no duplicate definition.

  • Possible values of <action> are:

    YES

    Check

    NO

    No check

SHORT_SCH_NAME

  • Affects the storing of the input scheme file name in the generated hull panels. If given, only that part of the file name explicitly given is stored, contrary to the full file specification if not given.

SHRINK_OBJ= <object>

  • Defines the name of the shrinkage object in SB_OGDB.

SPIGOT

  • This parameter controls whether spigot plates on holes should be possible to set.

  • It is a stand alone keyword and if set, it is possible to define spigot plates.

STORE_FR

  • When a coordinate along the X axis is given by a frame, this coordinate is translated to a pure number before storing it. This means that if the frame table is then changed, this number will translate back to another frame number. To avoid this, STORE_FR can be used to actually store the frame number. This will make the panel definition follow changes in the frame table.

STORE_LP

  • As for STORE_FR but valid for the Y and Z axis and the corresponding longitudinal tables.

STD_CLIP_TCODE

  • Controls the storing of clips as plate parts.

    1

    The in-built clips will be treated as individual parts. The part will get a position number and will be stored as a plate part.

    0

    These clips will be handled as standard parts (that means, they will not be stored as plate parts and will not be assigned position numbers (also when STD_CLIP_TCODE is left out)).

STI_CALC_POS

  • In cross-sections of a stiffener, the stiffener position is always calculated at the cross-section view. If the stiffener is defined in the material side of a panel, there might be different plate thickness along the stiffener trace which may give the wrong result.

  • This default keyword is used to tell the system how the user would like to treat the position of the stiffener in such case.

  • It can have two values: TRUE or DEFINED.

    TRUE

    Calculation of profile cross-section will be done at the true position (that means, take the plate of where the cross-section is in consideration). This is the default setting if STI_CALC_POS is missing.

    DEFINED

    Use the stiffener definition point (midpoint) to fetch the plate thickness to consider (that means, it will always find the midpoint of the stiffener and use that plate for all calculations).

USER_TAG_UNIQUE

  • If USER_TAG_UNIQUE is defined, it is not possible to insert stiffeners with already existing tag for the given plate.

Related Links
TitleResults for “How to create a CRG?”Also Available in