The trkNavigator is an interactive tool which allows to browse the tracker construction database and retrieve information about objects (modules, sensors etc.) and related tests on the basis of the object ID.

At startup a panel appears with three main areas: the object tree at the left, the object information area at the bottom and the test information area at the top. The panel is completed at the bottom by a text output area and, at the top, by the “Exit” button, the “Search” button, the search-input area, a combo-box and the "Customize" button.

The program works as follows: a set of objects (for example: all modules produced so far) is selected and appears in the tree-area at the left. Once the mouse is clicked on any of the objects in the tree, the related object information is shown in the object information area.

At start-up all modules produced so far are reported in the tree at the left. It is possible to change the objects appearing in the tree using the combo-box at the upper right corner and the Search button. For example, selecting “Sensors” in the combo-box and pressing the “Search” button at the left will select all sensors present in the database. If any number is typed in the search field, only objects whose ID contains that number are shown. For example, in order to select all sensors whose ID contains “12612”, we have to choose “Sensors” in the combo-box, type 12612 in the search field and press the Search button. If, instead, we want to retrieve the object whose ID is 30216630200126, it is enough to type 30216630200126 inside the search field, select “Any Object” in the combo box and press “Search”, to retrieve that aobject, discovering that it is actually a hybrid.

Other selectable choices presently available in the combo-box are: “hybrids”, “APVs”, “BondedModules” (to select modules with stored bonding information) and “BadSensors” (to select sensors with reference validation-test results different from :0:). There is also the tag "SensorBatch" which will be described later.

The object information is formatted in a two-column table, with the first column reporting the name of the variable and the second column the relative value.

If other objects are registered (in the object_assembly database table) to be contained by the examined object, red links related to these objects are displayed within the object information (typical example: sensors and hybrids contained inside modules). By clicking on those links the information about the related object is displayed. The links are displayed according to the order specified in the database by the "number_in_container" variable.

At the end of the object information are red links related to tests performed on the object and having (by default: see "customization" below)“reference” status. At the moment only the following tests are supported: validation (Validation_1_sen_ and Validation_2_sen_) for sensors, gantry validation (GANTRYVAL_1_MOD_), bonding (MODBOND_1_MOD_), validation (MODVALIDATION_1_MOD), long-term tests (MODULLTSUMMARY_1_MOD_, MODULLTFIRST_1_MOD_, MODULLTCOLD_1_MOD_ and MODULLTLAST_1_MOD_ ) for modules. Information related to module validation and long-term tests is presently searched in the “Test” database instead of the “Production” database. The text representing the tests in the table depends on the test status. The first time the object is shown the text is “??”, meaning that the application does not yet know whether the information related to that test is really present in the database. Once the link is clicked on, the application searches for the test in the database, and the text changes to “none” if no information is actually found, or to the test result value (like “:0:” for a successful test) if the test is actually found. In this case the test information is shown in the test information area at the top. The format is (again) a two-column table, with at the left the description of the variable and at the right its value. If the test shown is a composite test, red links relative to the sub-tests are present in the table.

In non-composite tests the value relative to each single measurement is shown in blue. By clicking on it the relative data is dumped in the output area at the bottom of the interface. This is useful when the values are too long to be shown in one raw of the table (typically, when the values are vectors). In this case, the “(click to print)” text is reported in the table. Values printed in the bottom area may be copied to the clipboard and pasted.

The "customize" button in the upper right corner will allow to customize the status of the Tests which are searched by the application. As explained above, by default the application looks only for tests with "reference" status. By clicking the "customize" button a frame with a slider appears, which allows to decrease the requested status from "reference" to "valid" down to "running". If, for example, "running" is selected, the application first looks at tests with "reference" status. If no such test is found, it will look to tests with "valid" status. If more tests are found, the most recent one is taken and displayed. If no test with "reference" status is found, the application looks for tests with "running" status and displays the most recent found. Since tests with "running" status have no defined result value, running tests are displayed in the table by the text "(running)". In any case, the application will show the test with higher status (in the order: running, valid, reference) existing in the database.

At the bottom of the table reporting composite-test information are green plot interfaces. By clicking on any of those interfaces a plot is displayed in an independent frame. Typical plot interfaces present for sensor validation tests are IV and CV curves, currents, Rpoly etc. Strip-dependent quantities are displayed either as a function of the strip number (scatter plot), either as an histogram.

By right clicking on the plot it is possible to change the plot properties and colors. In particular, by selecting “Print Plot ...” and “print to file” it is possible to save the plot in PostScript format; by selecting “Plot Properties” it is possible to change the axes parameters (range, log scale, text for the label) and the data representation (as an histogram or as data points, point sizes, colors etc.).

Each plot is available until its window is closed. It is possible to super-impose data from different plots. At the bottom of each plot is a combo-box reporting the names of all other available plots. By selecting the name of one target plot and pressing the "Attach To" button, the plot is sent to the target-plot and both are showed together in the target-plot window. A box with an (editable) legend appears. Through the " Plot Properties --> Data " menu is possible to re-adjust the data representation (colors, symbols etc.) for each plot represented. This way it is possible to make plots with several curves comparing (for example) IV from different sensors, noise from different modules, noise and raw noise together etc.

By clicking on the "WriteData" button in the frame of a scatter-plot, the data relative to the curves represented in the plot is written in the file "plot.txt" inside the directory where the application is running. The format is two columns for each curve (one for the x values and one for y values) spaced by tab characters, which can be easily opened and imported by Excel.

In the combo-box at the upper right corner of the interface is available the choice "SensorBatch". This will define the sample of all sensors whose ID is matching the number written in the search field. The purpose is to collect all sensor validation tests and all Process Quality Control tests performed on the sensors and on the test structures whose ID begins with the number written in the search field (thus defining a "batch"). The list of tests and of known physical sensors belonging to the batch is shown on the left (in place of the object tree) once the "Search" button is pressed. In order to access data for each single sensor, validation test or PQC test, click (as usual) on the red links appearing in the table. There is also (at the top of the table) a cyan button ("Retrieve Tests") which will retrieve all tests in one shot (just like each test was clicked on, one after the other). This may take some time, depending on the number of tests to be retrieved. In order to avoid too long queries, the number written in the Search field has to have at least 6 digits. In order to properly display the SensorBatch table, it may be necessary to enlarge the tree field by resizing the application window and dragging the splitting border (as shown in the picture).

trkNavigator Manual