SEAMCAT allows two options to generate two distinct log files. An automatic SEAMCAT log that monitors the behaviour of the application, and a user debug log to check how the computation is performed.
seamcat.log: This log file is automatically generated by SEAMCAT and is intended to be used to debug the Java application mainly in case of a crash of the application or when an exception in the code occurs. You can select/browse the filename and directory from the SEAMCAT options and also the log level.
Figure 43: SEAMCAT configuration
Figure 44: Seamcat.log log file automatically generated by SEAMCAT
Debug Mode: Running a simulation in “debug mode” Figure 44 is used for detailed check of the simulation process. Selecting this option, SEAMCAT will generate a log file where all interim results of simulations including what random values were generated for parameters defined as functions or distributions. This information is very useful for further inspection. The log file will be automatically stored in the sub-directory "Logfiles" of the main SEAMCAT directory. The debug option reduces the number of events to 5 events for the sake of limiting the size of log file. You may then review the generated log file using standard reading tools, such as Notepad, MS Windows, etc.
Figure 45: Selection of the debug mode
The output of the file (filename_date_number.log) is indicated at the bottom’s right corner of the SEAMCAT application window (see Figure 45) as well as in the first line of the log display as shown in Figure 106.
Figure 46: Filename and directory output for the debug log file
An example fragment of such a debug mode log file is shown in Figure 46. You may want to ammend the setting for generating the log file in the SEAMCAT configuration panel as described in ANNEX 20:.
Figure 47: Example of a debug mode log file