Skip to content

Monitoring Message Dictionary

Sebastien Denvil edited this page Jun 5, 2015 · 43 revisions

The set of supported Simulation Monitoring message types are defined below. The message codes are defined within a controlled vocabulary.

Standard Fields are included in every message below.

0000 - Simulation initialisation

0100 - Simulation ends

1000 - Computing job starts

1100 - Computing job ends

2000 - Post-processing job starts

2100 - Post-processing job ends

2900 - Post-processing job fails

3000 - Post-processing from checker job starts

3100 - Post-processing from checker job ends

4000 - PushStack - a command has been placed upon the active command's stack

4100 - PopStack - a command has been removed from the active command's stack

4900 - PopStack Failure - an error occurred whilst executing a command

7000 - Environment Metrics

7100 - Simulation Metrics

8888 - Cleanup

9999 - FATAL - simulation has been stopped due to an error

Custom fields associated with specific message:

#### 0000 - Simulation initialisation (FirstInitialize)
Custom Fields
Attachments
  • config card - the simulation .ini configuration file
#### 0100 - Simulation end
Custom Fields
#### 1000 - Computing job starts
Custom Fields
#### 1100 - Computing job ends
Custom Fields
#### 2000 - Post-processing job starts #### 2100 - Post-processing job ends #### 2900 - Post-processing job fails #### 3000 - Post-processing from checker job starts #### 3100 - Post-processing from checker job ends #### 4000 - PushStack - a command has been placed upon the active command's stack
Custom Fields
#### 4100 - PopStack - a command has been executed and removed from the active command's stack
Custom Fields
#### 4900 - PopStack Failure - an error occurred whilst executing a command
Custom Fields
#### 7000 - Environment metrics
Custom Fields
#### 7100 - Simulation metrics
Attachments
  • json files -
#### 8888 - CleanUp #### 9999 - FATAL - simulation has been stopped due to an error
Custom Fields

Clone this wiki locally