Endcut Table Input

The customer control of endcut takes place via the endcut table, created and updated in the structure data bank (SB_OGDB) via the hull utility inithull. To become available to the application programs the name of the endcut table should be assigned to the environment variable SB_ECUT.

It is possible to have project dependent endcut tables. Since only those endcut types/codes can be used which are available in the currently used endcut table it is possible to restrict the use of endcuts by removing them from the table. for example, a certain project may use only a subset of the total endcut standard of the yard. It is also possible to change the in-built parameters between project (for example, a small ship may require smaller notch radii than a big one). A customer may add new endcut codes as long as the numbering rules are adhered to.

The input file for creation of the endcut table is currently a text file organized in simple record types. A standard input file containing examples of all existing endcut types is included in each delivery of AVEVA Marine.

The input consists of three record types only and it is organized in the following way:

<record type 600>

<record type 601> (1 …. )

<record type 602>User defined endcut name

Thus it must start with a record of type 600 to be followed by any number of records of type 601 and 602.

The record type 600 simply contains the name of the endcut table to be assigned to SB_ECUT. It has the following simple format:

600 '<endcut table name>'

Each record type 601 defines a row of the table. It has the following layout:

601 < type > < npar > < par1 > < par2 > .... < par<npar> >

There are two types of type 601 records: selection rows and parameter rows.

The record type 602 contains the name of the user defined endcut name. There may be several rows of type 602.

602 < user defined endcut name >