Skip to main content

Tabular view

The iterative file contains the database of combinations of input variables and function values of each evaluated sample used by the Core Solver. It holds this info together with names of input variables, boundaries of the domain, etc. The .itr file is updated when the whole batch of samples required by the Core Solver is computed and able to be loaded as the DataProcessOut.txt file. The iterative file is created in the process of Uncertainty Quantification and Preliminary Analysis method.

In the Tabular view feature one can verify the function value of each sample used by the Core Solver and, if necessary, make corrections. This in particular is important in cases when the connected external program fails during its part of the computation. Running the Core Solver one more time with the modified iterative file database will repair the created model and/or statistical analysis without the need to acquire the other already existing data from the external source again.

How to use the interface#

Data from the iterative file are presented in the form of a spreadsheet, as shown in Figure 1. It is possible to change the sorting of the sheet (ascending or descending, where ascending is the default) by clicking on the row number, input variable, or output labels.

Figure 1: Result Postprocess - Tabular view of Iterative file

Changing values in spreadsheet cells is done the same way as in any type of spreadsheet editor. Only numbers are allowed in cells of the iterative file. It is possible to undo all changes with the Reset unsaved changes button above the sheet. The Export to CSV button starts the file dialogue for saving the sheet into a separate .csv file. Saving all changes done in the database and updating the source .itr file is done by clicking the Save changes button.

Save the data before export

The source for the database export into a .csv file is the state of the data as it was loaded from the .itr file. Therefore, to include all changes done in the spreadsheet into .csv first the user needs to save changes in the database to the .itr file