...

In order to create the geometry of your ship, you will need an object that contains frame numbers and relative, dimensionless widths. To keep the knowledgebase arranged logically, we will create a new class: “Geometry”.

• In the Knowledge Browser, create a new class named Geometry directly below Top Goals/Undefined.

...

In this paragraph, an object is created that will be given contents later on. We will create the object Ships.:

• In the Knowledge Browser, select the class Top Goals/Undefined. In the right hand side, right-click and select New Parameter/Function (or press Ctrl+I). Name the Object Ships and select the type: Object.

...

Ships is now a valid object in the knowledge base, but is not yet present in the dataset in the Workbase. WeYou'll have to add it.

• Drag the Ships parameter in the Knowledge Browser to the Dataset node in the Workbase.

...

Our data object should contain all the ship variations produced in tutorial 1. Therefore, we will you are going to copy the results of the DISP  solution (with the variations) to the object Ships using the clipboard.

...

This function states that the width of the ship at a certain frame number equals the relative width at that frame number multiplied with the total width of the ship. Notice that the frame number is no direct input in this relation, but Quaestor will still ask for it in a solution as Rel_B depends on that parameter.
We'll use
There is an alternative way of creating solutions. First we will , you need to add some attributes to the Ships object. Attributes are used to direct the behaviour of Quaestor in solutions. All available attributes are described here. We will apply two attributesTwo attributes are needed: @DBENTRY and @DBOBJECT.

...

The main procedure to create solutions with an existing dataset is through the use of the Process Manager. In the Process Manager, datasets and top goals can be selected to create new solutions. Furthermore, existing solutions, macros or scenarios (these terms will be explained in another tutorial) can be restarted. First, we'll make sure our the top goal B_Frame can be selected in the Process Manager.

• In the Knowledge Browser, drag the parameter B_Frame to the class Top Goals/Undefined.

...

The Process Manager starts. The left hand side shows all available datasets, in this case only our your Ships object. The right hand side shows the available tasks. The parameters in the Top Goals class are shown here, as well as existing solutions.

...

• In the Process Manager, select Ships:#1 as dataset and B_Frame as task. Click the Compute B_Frame button. A solution B_Frame[Ships: #1] is created.
• Because you can only give a range when you recalculated a solution, first provide one value for Frame and click Next. Press
• until the warning goes away.

However, we do want to create a case matrix (calculate all possible combinations, see tutorial 1), and continue with the calculation. Therefore, after the solution is finished, restart in and provide a range for Frame: 0(2)20. The result of the calculation is a table with B_Frame for every ship of the dataset over the full length (frame 0 to 20).

The process manager can also be used to just select a dataset, and top goals can be selected in the knowledge browser. We will start the same solution, but add the displacement to the table. 

Image Removed In the Process Manager, just select Ships:#1. Click the Select Ships button. In the class Main Dimensions of the Knowledge Browser, double click the parameter Disp to make it a top goal. In the class Top Goals/undefined also double click the parameter B_Frame (remember that multiple top goals are possible in Quaestor). Start a solution. Accept all proposed values (by pressing enter), for Frame first give a value and continue. Restart the solution and provide for Frame 0(2)20. Make a case matrix again and continue.

Now, the parameter Disp is shown in the output table too, together with its case depending parameter Lpp.

10 Creating a case matrix

The purpose of all this is to create a table with values of B_Frame for every ship in the dataset over the full length (Frame 0 to 20). For a first run of a solution, no range use is allowed, except when you specifically tell Quaestor that it is.

• In the Knowledge Browser, select the Top Goals/Undefined class.
• Select the parameter B and in the Properties window, select the Parameter tab. In the Data field, enter: @RANGEALLOWED.
• Do the same for the Frame parameter.
• In the Workbase, for B, enter as value 9(0.5)11 and for Frame, enter as value: 0(2)20, then click Next. Answer Yes to the question about the case matrix.

The result of the calculation is a table with B_Frame for every ship of the dataset over the full length (frames 0 to 20).

11 @DBENTRY, @DBOBJECT and the dataset 

Finally, let's explain the attributes used. The @DBENTRY and @DBOBJECT are used to configure access to the Dataset containing objects. This is best experience experienced by the difference in behaviour of the process manager.

...

Please note that @DBOBJECT is an addition to @DBENTRY. So @DBENTRY should always be in the multi case object you want to use as entry point for your data in combination with @DBOBJECT. 
Furthermore, at this moment it is not possible to do calculations for serveral multi case objects at once (this behaviour is suggested in earlier Quaestor version in situation where you use @DBOBJECT without @DBENTRY and as a result are able to select several or All Ships...).

...

12 Check 

You can verify your results by comparing it to [Tutorial 2 Finished] 

<< Back to tutorial 1 – Continue with tutorial 3 >>