v0.7.1
The Completion Criteria field on an accomplishment represents the general type of action that is performed to complete the accomplishment. For example, an accomplishment called ObserveMitigation would require the trainee to monitor how their actions affect the overload. One way they could do this is by opening the Alarms window, so the accomplishment would have the OpenWindow criteria. It would also need to have a Requirement to specify exactly which window they must open, which in this case would simply be Alarms.
There are many different types of Completion Criteria, each of which has a different format for requirements. Each simulator plugin had its own completion criteria, but there are a few that are global to all simulators.
The Accomplishment criteria is met when another Accomplishment is completed.
Requirement structure: Accomplishment Name
Accomplishment Name: The name of the completed accomplishment.The Check criteria is met when a check is activated.
Requirement structure: Check Name
Check Name: The name of the activated check.The Communicate criteria is met when the trainee uses GOAT's Communication module to send a message to a contact.
Requirement structure: Contact Name - Communication Abbreviation
Contact Name: The name of the contact spoken to.Communication Abbreviation: The abbreviation representing exactly which message was selected.These values should correspond to a Communication in the scenario.
The CompleteScenario critera is met when the trainee clicks the Done button in GOAT. An instance of the FINISH accomplishment with this criteria is automatically created when starting GOAT. Other accomplishments generally should not use this criteria.
Requirement structure: <unsupported>
The None criteria means this accomplishment has no requirements for completion. It will be completed automatically as soon as its prerequisites are completed. This is generally not useful.
Requirement structure: <unsupported>