Worldstates

Graph
full2
The worldstate with full knowledge of the scenario as it existed in Year 2. In practice, this worldstate was taken from a Year 2 release (ST10: st/Schedules/main+.stp)
main2-
The worldstate with certain information removed. In practice, this worldstate was received from Jordan.
games2+
The worldstate after year 2 wargames were run with main2- as the input. In practice, this worldstate was received from Jordan.
full3
The worldstate with full knowledge of the scenario as understood for Year 3. In practice, this worldstate has been laboriously constructed from several sources (full2, the information website, the GBCF) by Steve.
main3-
The full3 worldstate with selected information removed.
games3+
The main3- worldstate with the results of simulated wargames introduced, including (presumably) poor scheduling decisions made by the human operator.
main3+
The games3+ worldstate with the initial schedule (i.e. from main3-) reinstated.
full3c
The full3 worldstate with crisis information added.
Y2 Forgetting
The set of changes which took place to transform full2 into main2-. The delta was created by a human procedure, so in practice the delta must be recovered from the input and output of the procedure (i.e. full2 and main2- respectively).
Y2 Wargames
The set of changes which took place to transform main2- into games2+. Since wargames involved a human operator, the results must be recovered by comparing the input and output of year 2 wargames.
forget
This process recreates the changes of Y2 Forgetting and applies them to the full3 worldstate, yielding the main3- worldstate.
sim wargames
This process recreates (sim-ulates) the changes introduces by Y2 Wargaming and applies them to the main3- worldstate, yielding the games3+ worldstate.
merge
This process merges the initial, presumably good schedule from main3- and the learned properties from games3+, yielding the main3+ worldstate.

the forget process

Inputs

  1. full2
  2. main2-
  3. full3

Output

main3-

Parameters

  1. removeMeals (boolean, defaults to false) Whether or not the process should remove information about meal preferences

Mechanism

The forget process copies all properties of all nodes from full3 into main3-, except when any of the following criteria obtain:

  1. the property was specified in full2 and was left unspecified in main2-
  2. the property was specified as a PUD in main2-
  3. the property was the PerHourCost of a room leaf node
  4. removeMeals is set to true and the property was the requestedCateringService property of a room node
  5. removeMeals is set to true and the property was the requested*Meals property of a room node

When any of the above criteria obtain, the property is omitted from main2- (representing no knowledge about that property for the given node).

Questions

  1. What about properties which did not exist in the year 2 worldstate? For example, PosterM1 is known (in full3) to have requested 1 laser pointer (as per the GBCF); this knowledge is carried over into main3- with the current algorithm.

the sim wargames process

Inputs

  1. main2-
  2. games2+
  3. main3-

Output

games3+

Mechanism

The sim wargames process copies all properties of all nodes from main3- into games3+, except when any of the following criteria obtain:

  1. the property was left unspecified in main2- and was specified in games2+ (i.e. it was learned during wargames)
  2. the property had a different value in main2- than in games2+ (i.e. it was changed during wargames)

When any of the above criteria obtain, the property value is copied from games2+ (instead of main3-) into games3+.

the merge process

Inputs

  1. main3-
  2. games3+

Output

main3+

Mechanism

The sim wargames process copies all properties of all nodes from games3+ into main3+, except when any of the following criteria obtain:

  1. the property is a schedule edge (fixTo, assignTo)
  2. the property is a startPref property

When any of the above criteria obtain, the property value is copied from main3- (instead of games3+) into main3+