Naming and Storage of Profiles
- Last UpdatedJan 31, 2023
- 1 minute read
Naming of profiles can either be made freely by the user of in an automatic way. When using the automatic way of naming, the name will be built up as described below:
<Proj><Block No.>-0<Auto. number>/S<rno><SB/PS information>
|
<Proj> |
Project ID from fetched form SB_PROJECT |
|
<Block No.> |
Block number fetched from the initial form of this function (see below). |
|
- |
Separator (minus sign). |
|
0 |
Identifier for coded profiles. |
|
<Auto. number> |
Automatically generated number. The number is generated in a similar way as when using automatic naming in the module for Profile Nesting. |
|
/ |
Separator (slash). |
|
<rno> |
Running number. Starting from one. In case of individual storage, equal profiles regarding parameters and geometry will be stored with increasing running number. |
|
<SB/PS information> |
P is used for portside profiles and S is used for starboard profiles. |
Automatic naming is used when the logical SBH_PROFILE_NAMES is assigned to a file used for generation of automatic numbers.
When retrieving and storing profiles on the profile data bank, this can be done using a data type different from the one normally used for profiles. If this is done, also the Edit and Delete subfunctions will be restricted to this object type. The system manager will by this have a possibility to prevent editing or deletion of profiles generated from the model. If a data type different from the default is to be used (default is 90), this can be set by the use of a restriction file (see section 1.5).