Clarification on Restaurant Decision

Group Phase Specification
1

Hi,

I’m looking for some clarification on how to implement the restaurant decision phase, as the specification has two distinct rules that seem to conflict regarding when groups actually decide.

In Section 2.3.2 (Serving Phase - Restaurant Decision), the simulation order is defined as a tick-by-tick loop:

“Each tick starts with the customer groups deciding on their restaurant in order of group type (EVENT, CASUAL) and then ascending group id.”

However, Section 2.2 (Customer Groups) specifies strict, separate timeframes for these decisions:

  • EVENT groups: “They reserve 3 evenings before the event occurs in the first tick of that evening…”

    So should they reserve in their visiting tick or in the first tick???!!!

2

Hi, check this adjustment: https://forum.se.cs.uni-saarland.de:51443/t/specification-adjustments/16/14
which means they reserve in the first tick of the visiting evening.

1 Like