Log Event Types

When running the C3Fire system a session log file is generated. The session log file contains all events that occurred during the session. In the session log file all events have an event number, which make them unique, and they are sorted after time and the event number.
The event types of the C3Fire system are described below.

From the session log file it is possible to sort all event types into their own log file. This is done in the Log File Management tool of Analysis. In the event type description below these event type log files are described in the table cells with white background.

It is also possible to insert the event type data to a database. This is done in the Database tool of Analysis.
When inserting to the database each event type is given its own table. The database table is given a name based on the event type. Some table posts needed for the database management are added to the event information and in the database is also one additional table created, the Session Group table.
This database specific information is described in the table cells with green background. For the database tables is both information with white background and green background valid.



Event Types.

Session Control
Scenario Event

Unit State
Fire Event

Unit send Unit State to Role
Unit send observed Fire to Role
Unit send observed Object to Role
Unit send observed Unit to Role

Role send Mail
Role read Mail
Role copy text from mail-read to diary-edit
Role copy text from mail-read to mail-edit

Role insert diary text
Role read diary text
Role copy text from diary-view to diary-edit
Role copy text from diary-edit to mail-edit

Role insert unit intention on Role's map
Role insert unit pos on Role's map
Role insert fire on Role's map
Role insert mark on Role's map
Role insert object on Role's map

MapDB insert unit intention on Role's map
MapDB insert unit pos on Role's map
MapDB insert fire on Role's map
MapDB insert mark on Role's map
MapDB insert object on Role's map

Map Layer Quick Select


Tables in the database that is needed for the database management.

Session Groups



Scenario Event

A Scenario Event affects the dynamic characteristics of the session settings, at some specified time.

The scenario event log file is named scenario_event.txt and found in directory structure Measurements/LogFiles/ .

The scenario event database table is named scenario_event.

Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared.
Value example = "02:15:00"

Command

Events that effect the session.
Possible values = "SetTime", "SetWindDirection", "SetWindSpeed", "StartFire", "SendMail", "Pause", "End".



Fire Event

A Fire Event defines the fire state in one square on the map, which can have five states.

The log file event number are 11.
The fire event log file is named fire_event.txt and found in directory structure Measurements/LogFiles/ .
The fire event database table is named fire_event.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

State

The new state of the fire at the specified position.
1 - Clear, no fire is there.
2 - Fire, the area is burning, (red).
3 - ClosedOut, the area is no longer on fire due to fire fighting, (brown).
4 - BurnedOut, the area burned out by it self due to lack of fuel, (black).
5 - FireBreak, the area can not start to burn, (gray).

PosX

Horizontal position on the Map.

PosY

Vertical position the Map.



Unit State

A fire-fighting unit can move around in the environment and extinguish fire. A fire-fighting unit can be in five main activity states and is traditionally controlled by the user, but can also be controlled by a simulated agent.

The unit state event log file is named unit_state.txt and found in directory structure Measurements/LogFiles/ .

The unit state event database table is named unit_state.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Unit

The name of the unit.
Example: "F1"

Activity

A unit can be in ten main states:

1 - doing nothing
2 - moving
3 - mobilising
4 - fire-fighting
5 - demobilising
6 - refill water
7 - refill fuel
8 - tap water
9 - tap fuel
10 - creating fire break

PosX

Horizontal position on the Map.

PosY

Vertical position the Map.

IntentionX

Horizontal position on the map towards which the unit is heading.

IntentionY

Vertical position on the map towards which the unit is heading.

WaterLevel

The amount of water in the unit's water tank.

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.

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.

FuelLevel

The amount of fuel in the unit's fuel tank.

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.

FuelTapSpeed

The current speed with which the fuel level is taped from the fuel tank to a unit. The number of fuel levels moved every second.



Unit send Unit State to Role

The fire-fighting unit have ability to send information of its present activity state to a role. Which role the information is sent to is configured in session configuration.

The log file is named unit_send_unit_state_to_role.txt and found in directory structure Measurements/LogFiles/ .

The database table is named unit_send_unit_state_to_role.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

SenderUnit

The name of the unit.
Example: "F1"

ReceiverRole

The name of the role this unit sends information to. It is required in the session configuration.
Example: "X"

Activity

A fire-fighting unit can be in five main activity states:
doing nothing,
moving,
mobilising,
fire-fighting,
demobilising.

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.

IntentionX

Horizontal position on the map towards which the unit is heading.

IntentionY

Vertical position on the map towards which the unit is heading.

WaterLevel

The amount of water in the unit's water tank.

FuelLevel

The amount of fuel in the unit's fuel tank.



Unit send observed Object to Role

The fire-fighting unit have ability to send information about objects in its range of sight to a receiver role. Which role the information is sent to is configured in session configuration, as is the area of the units sight.
When sent, the object appears in the receiving roles map.

The log file is named unit_send_observed_object_to_role.txt and found in directory structure Measurements/LogFiles/ .

The database table is named unit_send_observed_object_to_role.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

SenderUnit

The name of the unit.
Example: "F1"

ReceiverRole

The name of the role this unit sends information to. It is required in the session configuration.
Example: "X"

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.

Object

The object this unit have in its range of sight.
Example: "pine", "house"



Unit send observed Fire to Role

The fire-fighting unit have ability to send information about fire in its range of sight to a receiver role. Which role the information is sent to is configured in session configuration, as is the area of the units sight.
When sent the fire appears in the receiving roles map.

The log file is named unit_send_observed_fire_to_role.txt and found in directory structure Measurements/LogFiles/ .

The database table is named unit_send_observed_fire_to_role.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

SenderUnit

The name of the unit.
Example: "F1"

ReceiverRole

The name of the role this unit sends information to. It is required in the session configuration.
Example: "X"

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.

Fire

The state of the fire.



Unit send observed Unit to Role

The fire-fighting unit have ability to send information about a unit, that enters its range of sight or changes its position in it, to a receiver role.
Which role the information is sent to is configured in session configuration, as is the area of the fire-fighting units sight.
When sent the observed unit appears in the receiving roles map.

The log file is named unit_send_observed_unit_to_role.txt and found in directory structure Measurements/LogFiles/ .

The database table is named unit_send_observed_unit_to_role.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

SenderUnit

The name of the unit.
Example: "F1"

ReceiverRole

The name of the role this unit sends information to.
Example: "X"

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.

Unit

The observed unit.
Example: "F4"

InVisible

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.



Role insert fire on Role's map

A role can insert fire on its own map.
This insertion does not affect the simulation.

The log file is named role_insert_fire_on_roles_map.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_insert_fire_on_roles_map.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role.
Example: "X"

Fire

The state of the inserted fire.
Clear, no fire is there.
Fire, the area is burning, (red).
ClosedOut, the area is no longer on fire due to fire fighting, (brown).
BurnedOut, the area burned out by it self due to lack of fuel, (black).

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.



Role insert object on Role's map

A role can insert an object on its own map.
Which object that shall be possible to insert is configured in the session configuration.
<ObjectType IDNr = "0" IDName = "Normal" FireSpeed = "1" />
<ObjectType IDNr = "1" IDName = "Pine" FireSpeed = "0.5" />
<ObjectType IDNr = "2" IDName = "Birch" FireSpeed = "1.5" />
<ObjectType IDNr = "3" IDName = "House" FireSpeed = "1" />

This insertion does not affect the simulation.

The log file is named role_insert_object_on_roles_map.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_insert_object_on_roles_map.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role.
Example: "X"

Object

The IDNr of the type of object inserted.
Example: IDNr = "0"

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.



Role insert unit pos on Role's map

A role can insert a unit on its own map.
If the inserted unit is controlled by another role will this insertion not affect the simulation.
If the inserted unit is controlled by this role then it will affect the simulation .

The log file is named role_insert_unit_pos_on_roles_map.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_insert_unit_pos_on_roles_map.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role.
Example: "X"

Unit

The name of the unit.
Example: "F1"

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.



Role insert unit intention on Role's map

A role can insert a units intention on its own map.
The unit must be controlled by this role and it will affect the simulation .

The log file is named role_insert_unit_intention_on_roles_map.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_insert_unit_intention_on_roles_map.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role.
Example: "X"

Unit

The name of the unit.
Example: "F1"

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.



Role insert Mark on Role's map

A role can insert a mark on its own map.
This will not affect the simulation .

The log file is named role_insert_mark_on_roles_map.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_insert_mark_on_roles_map .


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role.
Example: "X"

Mark

The name of the unit.
Example: "F1"

MarkType

The name of the unit.
Example: "F1"

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.

MarkEventType

The name of the unit.
Example: "F1"



MapDB insert fire on Role's map

The mapDB synchronization in C3Fire system inserts fire on roles map.

The log file is named mapdb_insert_fire_on_roles_map.txt and found in directory structure Measurements/LogFiles/ .

The database table is named mapdb_insert_fire_on_roles_map.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role on whos map fire is inserted.
Example: "X"

Fire

The state of the inserted fire.
Clear, no fire is there.
Fire, the area is burning, (red).
ClosedOut, the area is no longer on fire due to fire fighting, (brown).
BurnedOut, the area burned out by it self due to lack of fuel, (black).

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.



MapDB insert object on Role's map

The mapDB synchronization in C3Fire system inserts object on roles map. Which object that shall be possible to insert is configured in the session configuration.
<ObjectType IDNr = "0" IDName = "Normal" FireSpeed = "1" />
<ObjectType IDNr = "1" IDName = "Pine" FireSpeed = "0.5" />
<ObjectType IDNr = "2" IDName = "Birch" FireSpeed = "1.5" />
<ObjectType IDNr = "3" IDName = "House" FireSpeed = "1" />



The log file is named mapdb_insert_object_on_roles_map.txt and found in directory structure Measurements/LogFiles/ .

The database table is named mapdb_insert_object_on_roles_map.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role on whos map an object is inserted.
Example: "X"

Object

The IDNr of the type of object inserted.
Example: IDNr = "0"

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.



MapDB insert unit pos on Role's map

The mapDB synchronization in C3Fire system inserts unit position on roles map.

The log file is named mapdb_insert_unit_pos_on_roles_map.txt and found in directory structure Measurements/LogFiles/ .

The database table is named mapdb_insert_unit_pos_on_roles_map.

Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role on whos map a units position is inserted.
Example: "X"

Unit

The inserted units name. Example: "F1"

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.



MapDB insert unit intention on Role's map

The mapDB synchronization in C3Fire system inserts unit intention on roles map.

The log file is named mapdb_insert_unit_intention_on_roles_map.txt and found in directory structure Measurements/LogFiles/ .

The database table is named mapdb_insert_unit_intention_on_roles_map.

Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role on whos map a units intention is inserted.
Example: "X"

Unit

The name of the unit whos intention was inserted. Example: "F1"

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.



MapDB insert mark on Role's map





The log file is named mapdb_insert_mark_on_roles_map.txt and found in directory structure Measurements/LogFiles/ .

The database table is named mapdb_insert_mark_on_roles_map.

Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role on whos map a units intention is inserted.
Example: "X"

Mark

T

MarkType

T

PosX

Horizontal position on the Map.

PosY

Vertical position on the Map.

MarkEventType

T



Role send Mail

During a session the role have possibility to send regular text mail to other participants of the session.

The log file is named role_send_mail.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_send_mail.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

From

The name of the role.
Example: "X"

To

The name of the receiving role.
Example: "Y"

Text

Example: "Move 2 to (8,13)"



Role read Mail

During a session the role have possibility to read regular text mail from other participants of the session.

The log file is named role_read_mail.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_read_mail.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the reading role.
Example: "X"

CreateTime

The time when the mail was created. Value example = "02:33:00"

From

The name of the sending role.
Example: "Y"

To

The name of the receiving roles.
Example: "X, A and B"

Text

Example: "Fire in 10, 11"



Role copy text from mail-read to diary-edit

The role could copy a received mail and paste it into the diary panel.

The log file is named role_copy_text_from_mail_read_to_diary_edit.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_copy_text_from_mail_read_to_diary_edit.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role moving the mail to diary edit.
Example: "X"

CreateTime

The time when the mail was created. Value example = "02:33:00"

From

The name of the role that sent the mail.
Example: "Y"

To

The name of the roles that received the mail.
Example: "X, A and B"

Text

Example: "Fire in 10, 11"



Role copy text from mail-read to mail-edit

The role could copy a received mail and paste it into the diary panel.

The log file is named role_copy_text_from_mail_read_to_mail_edit.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_copy_text_from_mail_read_to_mail_edit.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role moving the mail to mail edit.
Example: "X"

CreateTime

The time when the mail was created. Value example = "02:33:00"

From

The name of the role that sent the mail.
Example: "Y"

To

The name of the roles that received the mail.
Example: "X, A and B"

Text

Example: "Fire in 10, 11"



Role insert diary text

The role have a possibility to insert text to diary panel.

The log file is named role_insert_diary_text.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_insert_diary_text.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role inserting text to diary edit.
Example: "X"

DiaryIDNr

Identification number for this inset to diary.

Text

Text inserted to diary edit. Example: "Unit extinguished fire in 10, 11"



Role read diary text

The role may read an inset from diary.

The log file is named role_read_diary_text.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_read_diary_text.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role reading diary text.
Example: "Y"

DiaryIDNr

Identification number for the read inset in diary.

CreationTime

Time for when the inset where created.

Creator

The name of the role once creating this diary inset.
Example: "X"

Text

Text of inset in diary. Example: "Unit extinguished fire in 10, 11"



Role copy text from diary-view to diary-edit

The role may copy an inset from diary view to diary edit.

The log file is named role_copy_text_from_diary_view_to_diary_edit.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_copy_text_from_diary_view_to_diary_edit.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role moving an inset from diary view to diary edit.
Example: "Y"

DiaryIDNr

Identification nr of the moved diary inset.

CreationTime

Time for when the inset where created.

Creator

The name of the role once creating this diary edit inset.
Example: "X"

Text

Text of moved inset in diary edit. Example: "Unit extinguished fire in 10, 11"



Role copy text from diary-edit to mail-edit

The role may copy an inset from diary edit to mail edit.

The log file is named role_copy_text_from_diary_edit_to_mail_edit.txt and found in directory structure Measurements/LogFiles/ .

The database table is named role_copy_text_from_diary_edit_to_mail_edit.


Database table specific properties

Signification

GroupNumber

This events group nr.
Example: 5

SessionNumber

This events session nr.
Example: 12

Event properties

Signification

EventNumber

As an event appears in the session it will acquire a number. First event acquire number 0 , next gets number 1, and so on.

Time

The session time for when the event appeared. Value example = "02:15:00"

Role

The name of the role moving an inset from diary view to diary edit.
Example: "Y"

Text

Text of moved inset in diary edit. Example: "Unit extinguished fire in 10, 11"



Session Groups

This is not an event table. This is a table for keeping group numbers in order.

All tables with event information in your database have as first column GroupNumber.
In this table, session_groups, is the group number stored in the first column called number. The second column, name contains the name for respective number. The third column, member of group, gives what group this group is part of.

The database table is named session_groups.


Database table specific properties

Signification

Number

The number of a group.
Example: "3", "4"

Name

The name of a group.
Example: "set2.uug5", "set2.uug5.uug5g"

MemberOfGroup

Which group this group is part of.
Example: "2", "3"