Skip to content

Home > User Interface > Results Processing > Structural Code Check Post-Processing > Running a code check study

Running a code check study

Once all the input data related to your code check study are defined, you may actually run the study computation either in interactive or in batch mode.

Interactive mode

The interactive mode may be launched by clicking the Launch button placed in the lower-right corner of the Structural Code Check study pane.

Batch mode

The user can launch a code check study in batch mode in two ways:

  • Launch an entire code check study over all analyses.
  • Launch in parallel as many code check computations than analyses.

The two modes can be used to create Batch Queue files (*DBQ) or Command file.

Messages concerning the progress of the calculation, in particular any errors detected, are produced in the file LOG_History.txt.

Launching code check study over all analyses

This way of launching consists of creating a DSC file. Once you have defined all the input data related to your study, click OK in the lower-right corner of the Structural Code Check study pane to validate all the settings. Right-click on the study name from the model tree, and select the Generate DSC batch file item from the contextual menu that displays, as illustrated next.

Then load the created DSC file in the Batch processing pane:

If you want to launch more code checks computations concurrently, you have to distribute the elements to be checked in several code check studies. Next, you must create as many DSC files as there are code checks studies and load these DSC files into the Batch processing pane. There will be as many calculations launched in parallel as the number of threads selected in the Batch processing options dialog box (8 in the example below).

Instead of using the Batch processing tool, it is possible to send batch command:

EXEC_FILE -console FILE_NAME.DSC

Launching code check computations by analysis

The second way consists of loading the DSK file in the Batch processing pane:

Choose in the toggle menu of the Job type, the Code check by analysis item. The user has to fill in the corresponding cells, the names of the study and the analysis.

To facilitate the filling of the Batch processing pane, you can create a Batch Queue file by selecting the item Generate Batch Jobs Queue (by analysis) in the contextual menu of a code check study:

The created file, with extension .dbq and name StudyName.dbq, can be loaded into the Batch processing pane instead of the DSK file. All the analyses selected in the study are listed in the Analysis column of the Batch processing table.

Unlike the previous method which consisted of distributing the elements into different studies, with this method, the code check computations are launched by analysis: the maximum code checks ratios will be determined by analysis and not overall the analyses. There are as many results files as analyses and each results file has a name of the form: StudyName_AnalysisName.csv

To obtain results over all analyses, an additional step is required : results by analysis must be merged by selecting the item Merge CSV Results Files by analysis in the contextual menu of a code check study:

This opens a pane which is described in section Merging CSV Results Files by analysis.

Result files by analysis in CSV format will be merged into a single file in CSV format whose results will be the same as those obtained by launching the study on all analyses interactively or in batch with the previous method, Launching code check study over all analyses.

Note

If the code checks computations are planned to be launched in parallel by analysis, it may be wise to reconsider the selected output types (for example, the listing output) since only files in CSV format are merged.

Instead of using the Batch processing tool, it is possible to send batch commands of the form:

EXEC_FILE -CCByAnalysis STUDY_NAME ANALYSIS_NAME FILE_NAME.DSK

These commands can be generated by clicking on the Export to Cmd button of the Batch processing pane.