C3Fire:Doc/Analysis/Log File Structure

Log Events

When the C3Fire server is running a session it creates a session event log. The session log file contains all events that occur in the session. The contents in the log depends on the configuration and on the activated modules.
The event log contain all information on what happened during a session, and it is possible to analyse the session and make a reply on what did happen in the session based on the information in the event log.

All events belongs to a specific event type. The event types in C3Fire are described below.

Log File Management
The Log File Management tool in C3Fire analysis can be used to sort all events in the session log file to separate log files, one log file for each event type. In the event type description below the content of each event type log file are described in the table cells with white background.

Database Support
In version 4.2.x.x the database connection is disabled!

It is also possible to insert all events to a database. This is done in the Database tool in C3Fire analysis. The database will contain a table for each event type. The database tables are given a name based on the event type. Database specific information is described in the table cells with green background.

Identification numbers

Role ID Numbers

The role id number are defined in the xml element <RoleIDNrs> in the event log file main xml element <C3FireLog>.

Example

<RoleIDNrs>
  <Role IdNr = "0" IdName = "Ground Chief A" />
  <Role IdNr = "1" IdName = "Ground Chief B" />
  <Role IdNr = "2" IdName = "Ground Chief C" />
  <Role IdNr = "3" IdName = "Ground Chief D" />
</RoleIDNrs>

Unit ID Numbers

The unit id numbers are defined in the xml element <UnitIDNrs> in the event log file main xml element <C3FireLog>.

Example

<UnitIDNrs>
  <Unit IdNr = "0" IdName = "F1" />
  <Unit IdNr = "1" IdName = "F2" />
  <Unit IdNr = "2" IdName = "F3" />
  <Unit IdNr = "3" IdName = "F4" />
  <Unit IdNr = "4" IdName = "L5" />
  <Unit IdNr = "5" IdName = "L6" />
  <Unit IdNr = "6" IdName = "R7" />
  <Unit IdNr = "7" IdName = "R8" />
  <Unit IdNr = "8" IdName = "D9" />
</UnitIDNrs>

Unit Activity ID Numbers

The possible unit activity depends on the configuration and activated modules. The possible units events are described in the xml element <LogEventInfo> whitch is the second xml element in the event log file.

Example

Unit Activity  0 = Not Defined
Unit Activity  1 = Inactive
Unit Activity  2 = Moving
Unit Activity  3 = Mobilizing
Unit Activity  4 = Fire Fighting
Unit Activity  5 = De Mobilizing
Unit Activity  6 = Refill Water
Unit Activity  7 = Refill Fule
Unit Activity  8 = Tap Water
Unit Activity  9 = Tap Fule
Unit Activity 10 = Hover
Unit Activity 11 = Refill People
Unit Activity 12 = Tap People

Fire State ID Numbers

The fire state id numbers  are defined in the xml element <FireTypeIDNrs> in the event log file main xml element <C3FireLog>.

Example

<FireTypeIDNrs>
  <FireType IdNr = "1" IdName = "Clear" />
  <FireType IdNr = "2" IdName = "Fire" />
  <FireType IdNr = "3" IdName = "ClosedOut" />
  <FireType IdNr = "4" IdName = "BurnedOut" />
</FireTypeIDNrs>

Object Type ID Numbers

The object type id number are defined in the xml element <ObjectTypeIDNrs> in the event log file main xml element <C3FireLog>.

Example

<ObjectTypeIDNrs>
  <ObjectType IdNr = "0" IdName = "Normal" />
  <ObjectType IdNr = "1" IdName = "Pine" />
  <ObjectType IdNr = "2" IdName = "Birch" />
  <ObjectType IdNr = "3" IdName = "House" />
  <ObjectType IdNr = "4" IdName = "Water" />
  <ObjectType IdNr = "5" IdName = "Fuel" />
  <ObjectType IdNr = "6" IdName = "People" />
  <ObjectType IdNr = "7" IdName = "Tent" />
  <ObjectType IdNr = "8" IdName = "MedicalTransitPoint" />
  <ObjectType IdNr = "9" IdName = "UAVBaseNW" />
  <ObjectType IdNr = "10" IdName = "UAVBaseN" />
  <ObjectType IdNr = "11" IdName = "UAVBaseNE" />
  <ObjectType IdNr = "12" IdName = "UAVBaseW" />
  <ObjectType IdNr = "13" IdName = "UAVBaseC" />
  <ObjectType IdNr = "14" IdName = "UAVBaseE" />
  <ObjectType IdNr = "15" IdName = "UAVBaseSW" />
  <ObjectType IdNr = "16" IdName = "UAVBaseS" />
  <ObjectType IdNr = "17" IdName = "UAVBaseSE" />
</ObjectTypeIDNrs>

Person Type ID Numbers

The person type id number are defined in the xml element <PersonTypeIDNrs> in the event log file main xml element <C3FireLog>.

Example

<PersonTypeIDNrs>
  <PersonType IdNr = "0" IdName = "Adult" />
  <PersonType IdNr = "1" IdName = "Child" />
</PersonTypeIDNrs>

Event Types

Scenario Event

A scenario event is a time stamped event that is done in the simulation, at some specified time.

The event type id number are 10.

The event type file that contain all scenario events are named scenario_event.txt.
The database table that contain all scenario events are named scenario_event.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description
EventNumber	When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. The value is an integer. Example: 625
Time	The session time when the event did occur. The value is a string "HH:MM:SS". Value example = "02:15:00"
Command	Events that effect the session. The value is a string. Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".

Fire Event

A Fire Event defines the fire state in one specific position on the map.

The event type id number are 11. 
The information that is written in the fire state events are described in the xml element <LogEventInfo>.
Example

11   = "Fire Event  : State PosX PosY"

The event type file that contain all fire events are named fire_event.txt.
The database table that contain all fire events are named fire_event.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description
EventNumber	When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. The value is an integer. Example: 625
Time	The session time when the event did occur. The value is a string "HH:MM:SS". Value example = "02:15:00"
State	The state of the fire at the specified position.  The value is an integer. Example: 2. See Fire State ID Numbers for what the number represent.
PosX	Horizontal position on the Map.
PosY	Vertical position the Map.

Unit State

When a unit perform some action an event is inserted in the log file. What information inserted in a unit state events depends on the configuration and the activated modules.

The event type id number are 12. 
The information that is written in the unit state events are described in the xml element <LogEventInfo>.
Example

12   = "Unit State : Unit Activity PosX PosY IntentionX IntentionY WaterLevel WaterRefillSpeed WaterTapSpeed FuelLevel FuelRefillSpeed FuelTapSpeed PeopleTransportNrOfPeople PeopleTransportEnterTime PeopleTransportLeaveTime"

The event type file that contain all unit state events are named unit_state.txt.
The database table that contain all unit state events are named unit_state.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description	Module
EventNumber	When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. The value is an integer. Example: 625
Time	The session time when the event did occur. The value is a string "HH:MM:SS". Value example = "02:15:00"
Unit	The id number for the unit. The value is an integer. Example: 1 See Unit ID Numbers for what the unit numbers represent.
Activity	The activity the unit currently are doing. The value is an integer. Example: 1 See Unit Activity ID Numbers for what the activity numbers represent.
PosX	Current horizontal position on the Map. The value is an integer. Example: 5
PosY	Current vertical position the Map. The value is an integer. Example: 6
IntentionX	Horizontal position on the map towards which the unit is heading. The value is an integer. Example: 22
IntentionY	Vertical position on the map towards which the unit is heading. The value is an integer. Example: 37
WaterLevel	The amount of water in the unit's water tank. The value is an integer. Example: 34	WaterLogistic
WaterRefillSpeed	The current speed with which the water level is refilled from a water tank unit or a water tank station. The number of water levels moved every second. The value is a decimal number. Example 3.5	WaterLogistic
WaterTapSpeed	The current speed with which the water level is taped from the water to a unit. The number of water levels moved every second. The value is a decimal number. Example 5.5	WaterLogistic
FuelLevel	The amount of fuel in the unit's fuel tank. The value is a decimal number. Example 55.4	FuelLogistic
FuelRefillSpeed	The current speed with which the fuel level is refilled from a fuel tank unit or a fuel tank station. The number of fuel levels moved every second. The value is a decimal number. Example 3.5	FuelLogistic
FuelTapSpeed	The current speed with which the fuel level is taped from the fuel to a unit. The amount of fuel moved every second. The value is a decimal number. Example 4.2	FuelLogistic
PeopleTransportNrOfPeople	The number of people in unit. The value is an integer. Example 2	People
PeopleTransportEnterTime	The current speed with which the people is enter the unit. The number of seconds it takes for one person to enter the unit. The value is a decimal number. Example 10.5	People
PeopleTransportLeaveTime	The current speed with which the people leave the unit.  The number of seconds it takes for one person to leave the unit. The value is a decimal number. Example 6.0	People

Unit send Unit State to Role

The units have ability to send information of its current activity and state to any role (player). Which role the information should be sent to is defined in the session configuration. When the state is send to a role an log event is created.

The event type id number are 13.
The information that is written in the send unit state events are described in the xml element <LogEventInfo>.
Example

13   = "Unit send Unit State to Role   : SenderUnit ReceiverRole Activity PosX PosY IntentionX IntentionY WaterLevel FuelLevel PeopleTransportNrOfPeople"

The event type file that contain all send unit state events are named unit_send_unit_state_to_role.txt.
The database table that contain all send unit state events are named unit_send_unit_state_to_role.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description	Module
EventNumber	When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. The value is an integer. Example: 625
Time	The session time when the event did occur. The value is a string "HH:MM:SS". Value example = "02:15:00"
Unit	The ID number for the unit. The value is an integer. Example: 1 See Unit ID Numbers for what the unit numbers represent.
ReceiverRole	The ID number for the role that the information is send to. The value is an integer. Example: 1 See Role ID Numbers for what the role numbers represent.
Activity	The activity the unit currently are doing. The value is an integer. Example: 1 See Unit Activity ID Numbers for what the activity numbers represent.
PosX	Current horizontal position on the Map. The value is an integer. Example: 5
PosY	Current vertical position the Map. The value is an integer. Example: 6
IntentionX	Horizontal position on the map towards which the unit is heading. The value is an integer. Example: 22
IntentionY	Vertical position on the map towards which the unit is heading. The value is an integer. Example: 37
WaterLevel	The amount of water in the unit's water tank. The value is an integer. Example: 34	WaterLogistic
FuelLevel	The amount of fuel in the unit's fuel tank. The value is a decimal number. Example 55.4	FuelLogistic
PeopleTransportNrOfPeople	The number of people in the unit. The value is an integer. Example 2	People

Unit send observed Object to Role

The units have ability to send information about objects in its range of sight to any role (player). Which role the information is sent to is configured in session configuration. When sent, the object appears in the receiving roles map.

The event type id number are 14.
The information that is written in the send observed object events are described in the xml element <LogEventInfo>.
Example

14   = "Unit send observed Object to Role   : SenderUnit ReceiverRole PosX PosY Object"

The event type file that contain all send observed objects events are named unit_send_observed_object_to_role.txt.
The database table that contain all send observed objects events are named unit_send_observed_object_to_role.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description	Module
EventNumber	When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. The value is an integer. Example: 625
Time	The session time when the event did occur. The value is a string "HH:MM:SS". Value example = "02:15:00"
Unit	The id number for the unit. The value is an integer. Example: 1 See Unit ID Numbers for what the unit numbers represent.
ReceiverRole	The ID number for the role that the information is send to. The value is an integer. Example: 1 See Role ID Numbers for what the role numbers represent.
PosX	Current horizontal position on the Map. The value is an integer. Example: 6
PosY	Current vertical position the Map. The value is an integer. Example: 5
Object	The ID number for the object this unit have in its range of sight. The value is an integer. Example: 5 See Object Type ID Numbers for what the object ID numbers represent.

Unit send observed Fire to Role

The units have ability to send information about fire in its range of sight to any role (player). Which role the information is sent to is configured in session configuration. When sent, the fire appears in the receiving roles map.

The event type id number are 15.
The information that is written in the send observed fire events are described in the xml element <LogEventInfo>.
Example

15   = "Unit send observed Fire to Role  : SenderUnit ReceiverRole PosX PosY Fire"

The event type file that contain all send observed fire events are named unit_send_observed_fire_to_role.txt.
The database table that contain all send observed fire events are named unit_send_observed_fire_to_role.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description	Module
EventNumber	When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. The value is an integer. Example: 625
Time	The session time when the event did occur. The value is a string "HH:MM:SS". Value example = "02:15:00"
Unit	The id number for the unit. The value is an integer. Example: 1 See Unit ID Numbers for what the unit numbers represent.
ReceiverRole	The ID number for the role that the information is send to. The value is an integer. Example: 1 See Role ID Numbers for what the role numbers represent.
PosX	Current horizontal position on the Map. The value is an integer. Example: 6
PosY	Current vertical position the Map. The value is an integer. Example: 5
Fire	The ID number for the fire type this unit have in its range of sight. The value is an integer. Example: 5 See Fire State ID Numbers for what the fire type ID numbers represent.

Unit send observed Unit to Role

The units have ability to send information about the units that is in its range of sight to any role (player). Which role the information is sent to is configured in session configuration. When sent, the unit will appears in the receiving roles map.

The event type id number are 16.
The information that is written in the send observed unit events are described in the xml element <LogEventInfo>.
Example

16   = "Unit send observed Unit to Role  : SenderUnit ReceiverRole PosX PosY Unit IsVisible"

The event type file that contain all send observed unit events are named unit_send_observed_unit_to_role.txt.
The database table that contain all send observed unit events are named unit_send_observed_unit_to_role.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description	Module
EventNumber	When an event occur in the session it will get a unique identification number. First event get 0 , next get 1, and so on. The value is an integer. Example: 625
Time	The session time when the event did occur. The value is a string "HH:MM:SS". Value example = "02:15:00"
SenderUnit	The id number for the unit. The value is an integer. Example: 1 See Unit ID Numbers for what the unit numbers represent.
ReceiverRole	The ID number for the role that the information is send to. The value is an integer. Example: 1 See Role ID Numbers for what the role numbers represent.
PosX	Current horizontal position on the Map. The value is an integer. Example: 6
PosY	Current vertical position the Map. The value is an integer. Example: 5
Unit (observed)	The ID number for the unit this unit have in its range of sight. The value is an integer. Example: 5 See Unit ID Numbers for what the unit ID numbers represent.
IsVisible	If the unit is visible or not. The false value is used to tell the role that it no longer can see the unit.  Possible values : "false", "true" in log file and "0", "1" in the database.

Person Move From To Unit or Pos Event

A Person Move From To Unit or Pos Event defines the movement of a person from and to a Unit or position on the map. This event type covers the full range of ways in which a civilian person can be moved:

• A Player loads a person from a position to a Unit
• A Player unloads a person from a Unit to a position
• A Manager or Player moves a person from a position to another position
  

The event type id number is 51.
The information that is written to the Person Move From To Unit or Pos Event is described in the xml element <LogEventInfo>.

Example

51   = "Person Move From To Unit or Pos : Person PersonType MoveType Unit1 Unit2 Pos1X Pos1Y Pos2X Pos2Y"

The event type file that contains all Person Move From To Unit or Pos Events is named person_move_from_to_unit_or_pos.txt.
The database table that contains all Person Move From To Unit or Pos Events is named person_move_from_to_unit_or_pos.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description	Module
EventNumber	When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. The value is an integer. Example: 625
Time	The session time when the event occurred. The value is a string "HH:MM:SS". Value example = "02:15:00"
Person	The ID number for the person. The value is an integer. Example: 1 The number is generated from the order of the persons in the <Persons> ... <Persons> configuration, 0 is the first person in the list.
PersonType	The ID for the type of person. The value is an integer. Example: 1 See Person Type ID Numbers for what the person ID numbers represent.
MoveType	The type of person movement. The value is an integer. Example: 6 1 Move from Pos to Unit, argument Pos1 and Unit1 are used. 2 Move from Unit to Pos, argument Unit1 and Pos1 are used. 5 Move from Pos to Pos, argument Pos1 (from) and Pos2 (to) are used.
Unit1	The ID number for the unit that the person was moved from. If the person was moved from a location, this value is -1. The value is an string. Example: R9
Unit2	The ID number for the unit that the person was moved to. If the person was moved to a location, this value is -1. The value is an string. Example: R9
Pos1X	The horizontal position on the map that the person was moved from. If the person is loaded from a Unit, this value is -1. The value is an integer. Example: 6
Pos1Y	The vertical position the map that the person was moved from. If the person is loaded from a Unit, this value is -1. The value is an integer. Example: 5
Pos2X	The horizontal position on the map that the person was moved to. If the person is loaded to a Unit, this value is -1. The value is an integer. Example: 10
Pos2Y	The vertical position the map that the person was moved to. If the person is loaded to a Unit, this value is -1. The value is an integer. Example: 12

Manager or player change Role Control Unit Event

A Manager or player change Role Control Unit Event defines the change of Role configuration, specifically the control of Units by a Role.

The event type id number is 60.
The information that is written to the Manager or player change Role Control Unit Event is described in the xml element <LogEventInfo>.

Example

60   = "Manager or player change Role Control Unit           : Changer Role Units"

The event type file that contains all Manager or player change Role Control Unit Events is named manager_or_player_change_role_control_unit.txt.
The database table that contains all Manager or player change Role Control Unit Events is named manager_or_player_change_role_control_unit.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description	Module
EventNumber	When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. The value is an integer. Example: 625
Time	The session time when the event occurred. The value is a string "HH:MM:SS". Value example = "02:15:00"
Changer	The ID for the Manager or Player that made the configuration change. The value is an integer. Example: -1 The ID of a Manager is -1. This is the only possible value for this property at the moment.
Role	The ID for the Role that has been configured. The value is an string. Example: A
Units	The IDs for all Units that are under control of the Role following the configuration event. The value is an string. Example: F1,F2,F3,F4

Manager or player change Unit Send Info To Role Event

A Manager or player change Unit Send Info To Role Event defines the change of Unit configuration, specifically which Roles a Unit sends information (within its observation area) to.

The event type id number is 61.
The information that is written to the Manager or player change Unit Send Info To Role Event is described in the xml element <LogEventInfo>.

Example

61   = "Manager or player change Unit Send Info To Role      : Changer Unit Roles"

The event type file that contains all Manager or player change Unit Send Info To Role Events is named manager_or_player_change_unit_send_info_to_role.txt.
The database table that contains all Manager or player change Unit Send Info To Role Events is named manager_or_player_change_role_control_unit.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description	Module
EventNumber	When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. The value is an integer. Example: 625
Time	The session time when the event occurred. The value is a string "HH:MM:SS". Value example = "02:15:00"
Changer	The ID for the Manager or Player that made the configuration change. The value is an integer. Example: -1 The ID of a Manager is -1. This is the only possible value for this property at the moment.
Unit	The ID for the Unit that has been configured. The value is an string. Example: F1 The Unit ID numbers correspond to the Units in the configuration files being used in the session.
Roles	The IDs for all Roles that the Unit sends information (within its observation area) to. The value is an string. Example: A,B,C

Manager or player change Role Can Send Mail To Role Event

A Manager or player change Role Can Send Mail To Role Event defines the change of Role configuration, specifically which Roles and Mail Groups a Role can send mail to.

The event type id number is 62.
The information that is written to the Manager or player change Role Can Send Mail To Role Event is described in the xml element <LogEventInfo>.

Example

62   = "Manager or player change Role Can Send Mail To Role  : Changer Role Roles"

The event type file that contains all Manager or player change Role Can Send Mail To Role Events is named manager_or_player_change_role_can_send_mail_to_role.txt.
The database table that contains all Manager or player change Role Can Send Mail To Role Events is named manager_or_player_change_role_can_send_mail_to_role.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description	Module
EventNumber	When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. The value is an integer. Example: 625
Time	The session time when the event occurred. The value is a string "HH:MM:SS". Value example = "02:15:00"
Changer	The ID for the Manager or Player that made the configuration change. The value is an integer. Example: -1 The ID of a Manager is -1. This is the only possible value for this property at the moment.
Role	The ID for the Role that has been configured. The value is an string. Example: A
Roles	The IDs for all Roles and Mail Groups that the Role can send mail to. The value is an string. Example: B,C,All

Manager or player change Mail Group Members Event

A Manager or player change Mail Group Members Event defines the change of Mail Group configuration, specifically which Roles are included in the Mail Group.

The event type id number is 63.
The information that is written to the Manager or player change Mail Group Members Event is described in the xml element <LogEventInfo>.

Example

63   = "Manager or player change Mail Group Members          : Changer MailGroup Members"

The event type file that contains all Manager or player change Mail Group Members Events is named manager_or_player_change_mail_group_members.txt.
The database table that contains all Manager or player change Mail Group Members Events is named mmanager_or_player_change_mail_group_members.

Database table specific properties	Description
GroupNumber	This events group nr. The value is an integer. Example: 5
SessionNumber	This events session nr. The value is an integer. Example: 12
Event properties	Description	Module
EventNumber	When an events occurs in the session it is given a unique identification number. The first event is numbered 0 , the next is numbered 1, and so on. The value is an integer. Example: 625
Time	The session time when the event occurred. The value is a string "HH:MM:SS". Value example = "02:15:00"
Changer	The ID for the Manager or Player that made the configuration change. The value is an integer. Example: -1 The ID of a Manager is -1. This is the only possible value for this property at the moment.
MailGroup	The ID for the Mail Group that has been configured. The value is an string. Example: All The Unit ID numbers correspond to the Mail Groups in the configuration files being used in the session.
Members	The IDs for all Roles included in the Mail Group. The value is an string. Example: A,B,C