Page History

...

  In the class Geometry, create a new object called Hull. As we want to store static data in this object, make sure it is determined by Value from Object/Database (as described in tutorial 2). In the workbase, select the object Ships (underDataset). In the Knowledge Browser, right click the parameter Hull and select Parameter to Dataset (or drag it tot Ship). When you are asked how to add Hull to the Ships object, select the list and continue. The new object is now placed within Ships.

...

 In the solution Waterline in the tree of the Workbase, select the Waterline object (so the tree node in the solution),  right click  in the table of the Workbase and select All to clipboard (or F4). Paste the data (both Frame and Rel_B) in the objectHull (answer Yest to all for including the parameters in the Hull object).

...

  Run a solution for Intpol_Rel_B using the process manager and selecting the ship object. Make sure that Intpol_Rel_B is in the class Top Goals/Undefined to see it in the Process Manager. The process manager is crucial here, as static data from theShips object should be used (which contains the object Hull). For frame, enter 3.20.

...

To find out how accurate the interpolation is, we introduce an error. The interpolated parameter uses static data from the object Hull, but we also defined the relative width analytically (the parameter Rel_B).

...

First, we take a look at the arguments after Hull. Data within the object Hull will be used in the integration, but yet it only contains dimensionless frame numbers and dimensionless widths. By putting (@X, @B_Frame, Lpp, B) behind it, you ask Quaestor to calculate X and B_Frame using data from within Hull, using Lpp and B from outside Hull and add all these parameters to the object Hull. You do actually use the object Hull as a function to calculate other parameters. This is a very powerful ability of Quaestor (see also QuaestorSyntax).

...