...
Mass Hull
, Mass Decks
and Mass Bulkheads
as children of Light Ship Weight
. All three are singular obligatory.Light Ship Weight
: Mass
, COGX
, COGY
, COGZ
, MOMX
, MOMY
, and MOMZ
.Light Ship Weight
.QEntityData
.Mass Hull
...
Parameter name | Dimension | Determined by | Reference | In Class |
| [t/m^3] | USR: User or system/equation | Weight factor per volume | Mass calculation |
...
Volume = ENTITY#(13).Volume
Mass Decks
...
Decks | child of “Mass Decks” | Entity Type: singular obligatory |
...
Decks
as child of entity Mass Decks
.Mass Decks
: Mass
, COGX
, COGY
, COGZ
, MOMX
, MOMY
, and MOMZ
....
...
...
Mass Decks
(This is again the same list as at the top of this page):Mass = SUM(@QEntity, 1, @Mass)
COGX = MOMX/Mass
COGY = MOMY/Mass
COGZ = MOMZ/Mass
MOMX = SUM(@QEntity, 1, @MOMX)
...
MOMY = SUM(@QEntity, 1, @MOMY)
MOMZ = SUM(@QEntity, 1, @MOMZ)
Include the following parameters in Entity “Decks“ (Child of entity “Mass Decks”): “Nr”, “Name$”, “Area”, “Weight_area_factor”, “Mass”, “COGX”, “COGY”, “COGZ”, “MOMX”, “MOMY”, “MOMZ and “QEntityData”.
QEntityData
.In entity Decks
, below entity Mass Decks
, you can In Entity “Decks”, below Entity “Mass Decks” we want to present a table that contains a copy of parameters (Name$ and AreaName$
and Area
) of all decks that are defined by the user in Entity “Decks” as child of Entity “entity Decks
below Lay out
”. In addition, the centre of gravity and mass of each deck will can be calculated in Entity “Decks”, below Entity “Mass Decks”.Take care that, with exception of parameter “Nr”, all parameters are placed within the table view (instantiate here.
Decks
below Mass Decks
: Name$
, Nr
, Area
, Mass
, COGX
, COGY
, COGZ
, MOMX
, MOMY
, MOMZ
and Weight_area_factor
.Nr
, put all parameters in the table view (localize (instantiate) parameter and provide attribute @MULTVAL...
...
Info |
---|
After the first parameter has been put in the table view with the attribute @MULTVAL, you can drag the other needed parameters directly to the table view from the Knowledge Browser. |
The number of cases is equal to the number of defined decks by the user in the “Lay out” Entity. We are going to get this information.
...
Mass Decks->Decks
(here, 10 is the entity ID of Layout->Decks
)Nr = ENTITY#(
...
10).Nr
...
The first column/case of the table should contain data (Name$
and Area
) from the first defined Deck in Entity “entity Deck
. The second column contains data from the second defined deck, etc.
...
Mass Decks->Decks
(here, 16 is the entity ID of Layout->Decks->Deck
)Name$ = ENTITY#(
...
16, ORCA(1)).Name$
Area = ENTITY#(
...
16, ORCA(1)).Area
...
When you want refer to a multiple Entityentity, you also have to indicate the QEntityIndexthe QEntityIndex. Quaestor automatically provides an index value in the Quaestor parameter QEntityIndex QEntityIndex
for each multiple Entityentity. So ENTITY#
(xx, 3) refers to the third defined Entity “entity Deck
”. The function ORCA(1) returns the current case number which is now being executed. So for the second column/case in a table, the value of ORCA(1) = 2. When we combine the index with the ORCA() function, like in Area = ENTITY#(xx, ORCA(1)).Area, the Area
relation above, the second column of the current table will refer to the area from the second defined deck, etc.Next create
...
Mass Decks->Decks
(here, 16 is the entity ID of Layout->Decks->Deck
):COGX = ENTITY#(
...
16, ORCA(1.X_front) + (ENTITY#(
...
16, ORCA(1)).X_aft))/2
...
COGY = 0
COGZ = ENTITY#(
...
16, ORCA(1)).Z
...
MOMX = COGX*Mass
MOMY = COGY*Mass
MOMZ = COGZ*Mass
Mass = Weight_area_factor*Area
QEntityData
.As already discussed in the “Deck
” Entity entity, the Weight_area_factor
is a bit special. What we you want is, that this property is connected to the original value in Deck
(of which the value is hidden) but, when modified by the user, the modified value should be used in both the present Mass
Decks>Decks Entity Decks->Decks
entity AND the original Entity (Decks>Deck).entity Decks->Deck
. This is done by means of the @SAVEINSOURCE attribute.
Weight_area_factor = ENTITY#(16, ORCA(1)).Weight_area_factor
Weight_area_factor
“ parameter:Figure 80: Data slot of "Weight_area_factor"
When a user add adds or remove removes a deck, or change properties changes values of an existing defined deck, these adaptations will automatically propagated to the “Mass Decks
” Entity entity.
...
Mass Bulkheads
Bulkheads
as child of ...
Mass Bulkheads
.Mass Bulkheads
: Mass
, COGX
, COGY
, COGZ
, MOMX
, MOMY
, and MOMZ
.Include Entity:
Bulkheads | child of “Mass Bulkheads” | Entity Type: singular obligatory |
...
...
...
...
Mass Bulkheads
...
Mass = SUM(@QEntity, 1, @Mass)
COGX = MOMX/Mass
COGY = MOMY/Mass
COGZ = MOMZ/Mass
MOMX = SUM(@QEntity, 1, @MOMX)
...
MOMY = SUM(@QEntity, 1, @MOMY)
MOMZ = SUM(@QEntity, 1, @MOMZ)
QEntityData
....
Take care that with exception of parameter “Nr” all parameters are placed within the table view (instantiate parameters and provide attribute @MULTVAL in Data Slot).
...
Bulkheads
below Mass Bulkheads
: Name$
, Nr
, Area
, Mass
, COGX
, COGY
, COGZ
, MOMX
, MOMY
, MOMZ
and Weight_area_factor
.Nr
, put all parameters in the table view (localize (instantiate) parameter and provide attribute @MULTVAL in its Data Slot).Mass Bulheads->Bulkheads
as in Mass Decks->Decks
above (here, 17 refers to Layout->Bulkheads->Bulkheads
):Nr = ENTITY#(
...
17).Nr
Area = ENTITY#(
...
17).Area.ORCA(1)
Name$ = ENTITY#(
...
17).Name$.ORCA(1)
...
TODO: dit levert een foutmelding in Quaestor
COGX = ENTITY#(
...
17).X.ORCA(1)
COGY = 0
COGZ = (ENTITY#(
...
17).Z_bottom.ORCA(1) + ENTITY#(
...
17).Z_top.ORCA(1))/2
MOMX = COGX*Mass
MOMY = COGY*Mass
MOMZ = COGZ*Mass
Mass = Weight_area_factor*Area
...
This is done by means of the @SAVEINSOURCE attribute. Create the following relation:
Weight_area_factor = ENTITY#(
...
17).Weight_area_factor.ORCA(1)
Weight_area_factor
“ parameter:...
Please note the difference with the previous paragraphsection, in which a table was created referring to values within multiple entities. For the bulkheads we have created one table and refer to values within the table of another singular Entity
Figure 82: Entity "Bulkheads" as child of Entity "Mass Bulkheads"
...
!
Include Entity:
Cargoes | child of “Mass Cargoes” | Entity Type: singular obligatory |
...