Difference between revisions of "VSLMSM"

Revision as of 13:27, 24 July 2010

EATURE OBJECT ATTRIBUTES

Attribute: vessel's measurements

Acronym: VSLMSM Code:

Camel case: vesselsMeasurements

Attribute type: Complex

Definition:

Multitude of terms and definitions specifically related to ships. (http://en.wikipedia.org; 24 July 2010)

Sub-attribute	Camel Code Identifier	Multiplicity	Sequential
VSLCAR	vesselsCharacteristics	0..*	True
VSLVAL	vesselsCharacteristicsValue	0..*	True
COMPOP	ComparisonOperator	0..*	True

VSLVAL was been set to INTEGER assuming using 3 decimal like 10.000 m.

That would give the result:
1. VSLCAR=draught; VSLVAL=10500; COMPOP=(>=) the regulation applies for vsl of 10.5 m draught and above
2. VSLCAR=DWT; VSLVAL=200000; COMPOP=(=) the regulation applies for vsl of exactly 2000 DWT
3. VSLCAR=length; VSLVAL=15000; COMPOP=(<) the regulation applies for vsl of less than 150 m length

Using a further example
[VSLMSM [VSLCAR=length; VSLVAL=50000; COMPOP=(>)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m must use the PILBOP

If the example should work for tanker between 50 and 100 m length the coding is like this
[VSLMSM [VSLCAR=length; VSLVAL=50000; COMPOP=(>)], [VSLCAR=length; VSLVAL=100000; COMPOP=(<)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m and < 100.0 m must use the PILBOP

David	Raphael	others	Jens
DA Y/N	RMM Y/N	others Y/N	JSF Y/N

@@ Line 38: / Line 38: @@
-<br>VSLCAR (length, beam, draught, air draught, GT, NT, DWT, DPL ) is just an idea, depending on the result of the discussion, we can keep or bin it.<br>
+<br>VSLVAL was been set to INTEGER assuming using 3 decimal like 10.000 m.
-[[COMPOP]] has to be to developed and should provide various comparison operators; see http://de.wikipedia.org/wiki/Logische_Operatoren or the English version http://en.wikipedia.org/wiki/Logical_connective  <br>
-However, the German version provides the better symbols :) <br>
-The definition of LOGCOM must provide the relation between the value given in the model and the real ship's value.
 That would give the result: <br>
-. VSLCAR=draught; value=10.5; COMPOP=(>=)     the regulation applies for vsl of 10.5 m draught and above <br>
+. VSLCAR=draught; VSLVAL=10500; COMPOP=(>=)     the regulation applies for vsl of 10.5 m draught and above <br>
-. VSLCAR=DWT; Value=2000; COMPOP=(=)          the regulation applies for vsl of exactly 2000 DWT<br>
+. VSLCAR=DWT; VSLVAL=200000; COMPOP=(=)          the regulation applies for vsl of exactly 2000 DWT<br>
-. VSLCAR=length; value=150; COMPOP=(<)       the regulation applies for vsl of less than 150 m length<br>
+. VSLCAR=length; VSLVAL=15000; COMPOP=(<)       the regulation applies for vsl of less than 150 m length<br>
-Using your first example <br>
+Using a further example <br>
-[complex attribute [VSLCAR=length; value=50.0; COMPOP=(>)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m must use the PILBOP <br>
+[VSLMSM [VSLCAR=length; VSLVAL=50000; COMPOP=(>)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m must use the PILBOP <br>
 If the example should work for tanker between 50 and 100 m length the coding is like this<br>
-[complex attribute [VSLCAR=length; value=50.0; COMPOP=(>)], [VSLCAR=length; value=100.0; COMPOP=(<)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m and < 100.0 m must use the PILBOP
+[VSLMSM [VSLCAR=length; VSLVAL=50000; COMPOP=(>)], [VSLCAR=length; VSLVAL=100000; COMPOP=(<)]], CATVSL=3 (tanker), LOGCON=1 (and), LIMTYP=2 (required); associated to a PILBOP object: tankers with LOA > 50.0 m and < 100.0 m must use the PILBOP

Difference between revisions of "VSLMSM"

Revision as of 13:27, 24 July 2010

Navigation menu

Search