Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Tutorial 2
TeLiTab and Objects

Learning goals

  1. Learn about the TeLiTab data format
  2. Using an object as a function 
  3. Creating a multiple case solution
Prior knowledge



1    Objective

In this tutorial, we'll create the shape of a ship's waterline in a table of frame numbers and dimensionless widths. The dataset containing variations of the main dimensions of a ship from tutorial 1 is stored in a data object Ships in the dataset of the knowledge base, so it can be easily used in further calculations. This dataset combined with the dimensionless width table is used to calculate the width at the waterline at frame number 2 for every variation.

...

The dataset of Quaestor can only containt objects on its top level (below the Dataset node). When you want to use the data in the Dataset, you can either select the object or define the object as database entry so that the Process manager will show it's content. @DBENTRY defines this entry point for selection of data by Quaestor (and thus in the process manager).

...

Try running the process manager without @DBOBJECT. It's now possible to select the cases within the Ships object, instead of the whole object (all cases). The reason is that Quaestor now expects there is only one relevant object, being the one specified as @DBENTRY, so only selections within this object are relevant to be shown in the process manager.

Please note that @DBOBJECT is  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  without @DBENTRY and  and as a result are able to select several or All Ships...).

...

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

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