The following table provides an overview of the differences between result sets and single runs.
|
Function | Single run | Result set |
|---|---|---|
| For archiving purposes, the master processing method is copied into the sirslt folder. The linked method is the master method, which is stored in the Methods path. The Methods path is configured in the project. | The master processing method is copied into the rslt folder. The master processing method is usually being closed. It only remains open if it is also linked to a loaded single run. The method in the rslt folder is referred to as the result set method. The linked method is the result set method. | |
|
The injection is processed. The current version of the master method is copied into the sirslt folder when the data are saved. | The result set is processed. | |
not supported |
supported | |
not supported |
supported | |
not supported |
supported | |
| Selected single runs are exported. | The entire result set is exported. | |
|
The master processing method is not included, but the copy that was saved to the sirslt folder will be available. In order to work with this method, copy it to the Methods path of your project, and link it manually. | If a method has been linked in the exported data, the method is also included in the import. | |
|
Calibration | The linked master method is never updated by calibration. |
The linked result set method may be updated by calibration. |
|
Function is not available as you are already working with the master method. | Function is available to update a master method with a result set method. | |
Function is available in systems with central data storage. | Function is available in systems with central data storage. | |
Manual integration corrections are saved to the master method | Manual integration corrections are saved to the result set method |