3.10 Rerun functionality
In the report, in the Meta Data and in the Summary sections, a Rerun all button can be used to quickly rerun Code Checker for MATLAB using the settings that were used to create the report you are currently viewing. This is very useful to check if the changes you made after viewing the report result in improved rule compliance. It can also be useful if the configuration file has changed.
Remarks
-
The settings used for the rerun are stored in Code Checker for MATLAB and not in the report. This has the following consequences:
-
Clicking the Rerun all button in an older report could result in using different settings for the rerun than were used for the initial run that resulted in the report. It is therefore recommended to use the rerun functionality from the most recently created report.
-
Clearing the Code Checker for MATLAB code or calling clear all, clear classes, clear functions or clear java causes the stored inputs to be lost. Clicking the Rerun all button will then result in an error.
-
MATLAB sessions in which no Code Checker for MATLAB report was created yet will trigger an error when a report is opened and the Rerun all button is clicked.
-
The rerun functionality does not directly use a list of files to check. Instead, it uses the settings used during the last run. This has to be kept in mind in the following situations:
-
If you checked a folder before, the folder will be checked again and any newly added files will be checked as well.
-
If you checked the MATLAB file that was opened in the editor, the rerun function will run the checks on the file that is open in the editor at the time of clicking the Rerun all button.
-
If you selected the option to check only the files changed with respect to a SubVersion repository, the list of files may change when you edit other files or commit your changes.
-
If no new Code Checker for MATLAB run was started for over 72 hours within the same MATLAB session, you will be required to do so before being able to use the rerun functionality.