Data use and management
In the article Image management (In de Quaestor Knowledge de Quaestor Knowledge Browser: Quaestor>Topics>Technical documentation) and QBinaries, it is described how to create, maintain and access a collection of images or documents that are presented when a particular parameter or value is in focus in the Knowledge Browser or Workbase. In this article we will depart from this mechanisms and zoom in on the possibility to create (binary) databases and use them (by performing selections) during the modeling process.
...
HullForm$ is determined by means of a relation:HullForm$ = HULLDATA#.HullForm$
HULLDATA# is the selected input set for the calculation and is defined by an |OPTIONS| script represented as a Telitab set in its data slot of the parameter:Available parent ships:
|OPTIONS|
8
"CAPTION1" "Ship type"
"CAPTION2" "Project number"
"CAPTION3" "Loading condition"
"OPTION1" "SHIPTYPE$"
"OPTION2" "PROJECT$"
"OPTION3" "CONDITION$"
"HullForm$" ""
"DATA#" "ParentShips"
|
Let us explain what you see in more detail:
...
As alternative method to select data, in stead of making a reference to an object as done with "DATA#" "ParentShips", you can include the data in the |OPTIONS|….| script of the parameter. This is done in the following example@SUMMARY
@PICTURE
Required options for xxxx method
|OPTIONS|
12
"CAPTION1" "Type of ship:"
"CAPTION2" "Type of superstructure:"
"CAPTION3" "Trial loading condition:"
"CAPTION4" "CX table:"
"OPTION1" "SHIPTYP"
"OPTION2" "SUPERSTR"
"OPTION3" "LOAD"
"SUMMARY" "Selected combination of ship type, loading condition and superstructure on trial"
"SUMMARY1" "Selected ship type:"
"SUMMARY3" "Selected loading condition on trial:"
"SUMMARY2" "Selected type of superstructure on trial:"
"SUMMARY4" "Selected wind table on trial:"
5 "OPTION" "SHIPTYP" "SUPERSTR" "LOAD" "OPTION4"
"1" 01060134 1 6 1 "table 1:twind1"
"2" 01070135 1 7 1 "table 2:twind2"
"3" 01080336 1 8 3 "table 3:twind3"
"4" 01090337 1 9 3 "table 4:twind4"
"5" 23090945 23 5 9 "table 12:twind12"
"6" 24090946 24 5 9 "table 13:twind13"
"7" 25050138 25 5 1 "table 5:twind5"
"8" 25050339 25 5 3 "table 6:twind6"
"9" 26050340 26 5 3 "table 7:twind7"
"10" 27050941 27 5 9 "table 8:twind8"
"11" 28100942 28 10 9 "table 9:twind9"
"12" 28110943 28 11 9 "table 10:twind10"
"13" 28120944 28 12 9 "table 11:twind11"
|
Let us explain what you see in more detail:
...
Quaestor employs an internal database selection mechanism that can be defined through an |OPTION| script. In the following we will briefly explain its principles. In order to enable the selection of a hullform, the following |OPTION| script is included in the data slot of the parameter ComponentFile$:@LOCAL 'parameter is local to object
@SUMMARY 'generates a summary after the selection
|OPTIONS| 'Tag voor selectie script
6
"CAPTION1" "Give Component Type" 'Caption of first selection list
"CAPTION2" "Give Component name" 'Caption of second selection list
"OPTION1" "Type$" 'Type denominator of component
"OPTION2" "Name$" 'parameter with first selection key
"OPTION" "Component$" 'parameter with second selection key
"DATA#" "RhinoComponents" 'Reference to object containing data
|
Note: The text after ' is comment please do not use it in the knowledge base.
...
Overview
Content Tools