Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When the knowledgebase node is expanded, the classes classes within the knowledgebase are visible. Classes are used to organise your parameters, and put them in a practicable structure. The Top Goals/Undefined class is part of the knowledge base by default. Here, the goal parameters of your calculation (Top Goals) can be stored, as well as other parameters that don't belong to other classes (Undefined).

...

 Select the class Main Dimensions in the right-hand side of the knowledge browser, and select New Parameter/Function(Ctrl+I), see figure 3. Note that the last parameter in focus will be shown in the input field (most probably QKnowledgebaseVersion). Delete this parameter, type Lpp and click the Value button. Repeat these actions for the parameters B and T.

...

In the larger area of the Frame Viewer, a reference reference can be assigned to the parameter. A proper reference is important, as users of the knowledgebase may not be certain of the exact meaning of the parameter. Please also read Documentation of knowledge for more details.

...

This qualification can be provided in the Slots & Properties window.

 Select the parameter LPP. In the Slots & Properties window, scroll down to the Determined by row. Change the value to VR: User only, as the parameter LPP is input (instead of defined by a relation), see figure 5.

...

In order to define the loading capacity of the ship, it’s important to know the kind of water (Salt or Fresh) the ship will sail in. Therefore, we will add some relations relations and constraints, and make sure the user can select the watertype.

...

Note that when you enter a relation, Quaestor provides as much help as possible by means of the Help Checker. This checker shows what to expect (in this case a Value or an Expression, ValExp).  After saving a relation, the Help Checker will check the syntax for possible errors, and shows a warning message when something is wrong.

...

The two relations for the density of the water are only valid for their corresponding watertype. Therefore, a constraint constraint is added to each relation. A constraint is simply a restriction for the validity of the relation.

...

The constraint is now added, and a parameter named Watertype$ has been created. The $ at the end of the parameter name makes sure Quaestor recognizes it as a String String value, and the dimension Str is automatically assigned (see also Quaestor syntax. We have to assign a determined by value to make it a valid parameter.

...

Let's perform our first Quaestor calculation. A solution is always determined by one or more Top Goals. A top goal is a parameter (or object) that is your final calculation target, in this tutorial it's the displacement of the ship. 

...

Calculations and solutions are managed in the workbase. Here, solutions can be created, redone (with different data), examined and deleted. 

...

As mentioned in the objective, we'd like to create a dataset of systematically varied ships. We could of course perform several calculations with different input data by hand, but it's much easier to use the ability of Quaestor to create multiple case solutions. To keep the complexity of this example within reason, we will only vary the breadth and length of the vessel. Please note that due to some important conceptual reasons the latest Quaestor release can only perform calculations on ranges of parameters when you alreade have created a solution.

...

The new solution is now created. The fixed values are again shown in the right hand side of the workbase. The varying parameters (B and Lpp) and the corresponding solution for DISP are shown in the lower part. Each row is a different case, identified by a case number(#1, #2, etc.), see figure 16.

...

A lot of cases in our solution don't meet the design criteria: a displacement between 2000 and 3000 ton. We could have fixed this by adding a constraint to DISP, but another way is to use a filter filter in the solution table.

   In the workbase, select the last (multiple case) DISP solution, and click the   or "Filter" button. The filter window shows. For DISP, select Range as filter, fill in 2000 for Lower bound and 3000 for upper bound (figure 18). Click the Apply button.

...