User Options for Calibration: Calibration Scenario Editor Tab
To go to this tab, click the User Options
button and select the Experiment
tab. On the Experiment tab, double-click in the
Value field of the Calibration
option, then select the Calibration Scenario Editor
tab.
The settings in this tab are applied as default values to all newly added calibration scenarios; they have no influence on existing calibration scenarios.
The behavior of the Calibration Scenario Editor when working with Calibration scenarios and configurations can be defined with the following settings:
File format for new scenario
Defines the file format to be used for new calibration scenarios. The following file formats are supported:
- CVX (default)
- DCM
- CDF V2.0
- PaCo
Fill empty scenario cells with original WP values
To add an already created scenario, one or more calibration variables can be left blank at first. Newly created scenarios do not receive any concrete values for calibration variables either. With this option, you define if blank calibration variables (those without any concrete parameter values) should be automatically filled with the original value on the working page when reading or creating a scenario.
Yes
Blank calibration variables are filled with the original value of the calibration variable on the working page (default setting).
No
Blank calibration variables stay blank. To identify calibration variables without any parameter values, the characters -- are displayed in the corresponding table cell.
Copy original WP values to WP at closing time
When you activate a scenario, the values of the calibration variables are written to the working page and thereby immediately activated. With this option you can define if the original values on the working page that were created when the page was opened should be restored when the editor is closed.
Yes
When closing the editor, the values are used on the working page that applied when the editor was opened.
No
When closing the editor, the values of the scenario that was last activated are used on the working page.
User Confirmation
When closing the editor, you are asked if you would like to use the original values on the working page or the values of the last activated scenario in the experiment (default setting).
Use RP and original scenario as emergency button
Defines if you can switch directly to the corresponding file by simply clicking on the column with the values of the reference page or the original scenario (emergency switch). In this manner, you are able to ensure that the data can be immediately restored to a saved version in response to unwanted behavior.
WARNING
Changes in the calibration variables have an effect upon the behavior of the vehicle and can lead to undesired behavior. When you perform calibration actions while driving, always select the setting Yes to be able to immediately switch to a saved data state in dangerous situations!
Yes
When you click on the column of the reference page or original scenario, the data is directly switched to the corresponding version (default setting).
No
It is possible to click on the column of the reference page or original scenario, without the data being directly switched to the corresponding version.
WARNING
Select this option only if you are performing calibration actions in a secure environment (e.g. on the test bench).
Save scenario files at closing time
Defines if changes to the calibration variables of the individual scenarios should be saved automatically without any confirmation in the scenario files when the editor is closed.
Note
Changes to the values of the calibration variables themselves are saved only in the scenario files, but not in the scenario configuration. The configuration saves higher ranking information, such as which scenarios belong to the configuration and what calibration variables must be considered, but not their values.
Yes
The current values of the calibration variables of the scenarios are automatically saved in the scenario files when the editor is closed (default setting).
No
Changes to the calibration variables of the scenarios are discarded when the editor is closed.
User Confirmation
If scenarios contain modified calibration values when the editor is closed, you will be asked if you would like to save the changes in the scenario files.
Save Calibration Scenario Editor at closing time
Defines if changes to the calibration scenario configuration (i.e. changes to the contained scenarios and calibration variables or to the options) should be saved automatically without any confirmation to the INCA database when the editor is closed.
Note
This does not concern changes to the parameter values of the individual scenarios; they are not saved in the configuration, but in a separate file by scenario.
Yes
The configuration is automatically saved when the editor is closed (default setting).
No
Changes to the configuration that you have not explicitly saved are discarded when the editor window is closed.
User Confirmation
If the configuration contains unsaved changes when the editor window is closed, you will be asked if you would like to save them.
Activate incomplete scenarios
It is possible that some or all calibration values of a scenario are blank, e.g. because a new scenario was created that does not yet contain any values, or because individual values were explicitly deleted. With this option you can define if scenarios with blank calibration values (i.e. without any explicitly entered parameter value) or of an inappropriate file type can be activated.
Yes
Incomplete scenarios can be activated. For the blank calibration variables (i.e. fields without any explicitly entered value), the current values of the working page are used, i.e. for this calibration value, the value in the column AS value is not overwritten.
No
It is not possible to switch to incomplete scenarios (default setting). Before you can activate such a scenario, you must ensure that all listed calibration variables contain valid values.
Calibration Scenario Editor output directory
It defines the path in which the external scenario files should be stored.
See