Difference between revisions of "Maximum Score"
| Line 10: | Line 10: | ||
* If they get it wrong a third time, playback continues to the next action, and the user is awarded 0 points | * If they get it wrong a third time, playback continues to the next action, and the user is awarded 0 points | ||
| − | There is currently a flaw in this | + | There is currently a flaw in the calculation of this property. It is calculated based on the total number of [[Test mode]] ''actions'' in the simulation, but does not take into account any logic that may cause the user to execute less than all of the actions. For example, if there is a Branch that contains two actions (and the user has to execute one or the other), '''both''' macros within the Branch will be included in the calculation of the '''Maximum Score'''. Similarly, if there is a '''[[Jump to Step]]''' macro that branches around some actions in [[Test mode]], the omitted actions are still considered in the calculation. Thankfully it is only the calculation of the '''Maximum Score''' (and associated '''[[Required Score]]''') that is flawed. During execution, these property values are correctly calculated based on the number of actions the user was ''required'' to perform ''during the execution'', taking into account any branches, jumps, and so on. |
| − | The '''Maximum Score''' | + | The '''Maximum Score''' and '''[[Required Score]]''' are automatically recalculated whenever the '''[[Simulation]]''' is saved, but you can force a recalculation at any time, by clicking on the '''Update''' button at the top of the ''Properties pane'' for the '''[[Simulation Start]]''' macro. |
| + | |||
| + | There does not seem to be a way to adjust the number of attempts that the user can make; it appears to be hard-coded at '''3'''. | ||
<br clear=all /> | <br clear=all /> | ||
| + | |||
==See Also== | ==See Also== | ||
* '''[[Simulation]]''' content object > '''[[Simulation Start]]''' macro > '''[[Required Score]]''' property | * '''[[Simulation]]''' content object > '''[[Simulation Start]]''' macro > '''[[Required Score]]''' property | ||
Revision as of 14:12, 24 August 2019
Scope
- Simulation content object > Simulation Start macro > Maximum Score property
Purpose
The Maximum Score property defines the maximum number of 'points' a user can score if they complete the simulation in Test mode without making a single mistake. This value is calculated automatically as 3x the number of 'actions' in the simulation when it is played in Test mode. A value of '3x' is used because of the way the user is given multiple chances to complete an action:
- If they perform the action correctly on the first attempt, they are awarded 3 points
- If they get it wrong on the first attempt, they are prompted to try again, but can only earn a maximum of 2 points
- If they get it wrong a second time, they are prompted to try again, but can only earn 1 point
- If they get it wrong a third time, playback continues to the next action, and the user is awarded 0 points
There is currently a flaw in the calculation of this property. It is calculated based on the total number of Test mode actions in the simulation, but does not take into account any logic that may cause the user to execute less than all of the actions. For example, if there is a Branch that contains two actions (and the user has to execute one or the other), both macros within the Branch will be included in the calculation of the Maximum Score. Similarly, if there is a Jump to Step macro that branches around some actions in Test mode, the omitted actions are still considered in the calculation. Thankfully it is only the calculation of the Maximum Score (and associated Required Score) that is flawed. During execution, these property values are correctly calculated based on the number of actions the user was required to perform during the execution, taking into account any branches, jumps, and so on.
The Maximum Score and Required Score are automatically recalculated whenever the Simulation is saved, but you can force a recalculation at any time, by clicking on the Update button at the top of the Properties pane for the Simulation Start macro.
There does not seem to be a way to adjust the number of attempts that the user can make; it appears to be hard-coded at 3.
See Also
- Simulation content object > Simulation Start macro > Required Score property
- Settings > Playback Settings > General > Feedback > Feedback Handling category
