Skip to content

Commit

Permalink
[meltdown-mitigation] Be super explicit (#3501)
Browse files Browse the repository at this point in the history
* [meltdown-mitigation] Be super explicit

It seems a few people get stuck on this (maybe because the sentence is quite long and for non-native speakers it's tough to parse - e.g. "plus or minus 10%" could feel confusing maybe?) so I thought maybe we become SUPER explicit.

* Update exercises/concept/meltdown-mitigation/.docs/instructions.md

---------

Co-authored-by: BethanyG <BethanyG@users.noreply.github.com>
  • Loading branch information
iHiD and BethanyG authored Sep 11, 2023
1 parent 49cc1ec commit 418e5d2
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions exercises/concept/meltdown-mitigation/.docs/instructions.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,9 +61,7 @@ Implement the function called `fail_safe()`, which takes 3 parameters: `temperat
- If `temperature * neutrons_produced_per_second` < 90% of `threshold`, output a status code of 'LOW'
indicating that control rods must be removed to produce power.

- If `temperature * neutrons_produced_per_second` are within plus or minus 10% of the `threshold`
the reactor is in _criticality_ and the status code of 'NORMAL' should be output, indicating that the
reactor is in optimum condition and control rods are in an ideal position.
- If the value `temperature * neutrons_produced_per_second` is within 10% of the `threshold` (so either 0-10% less than the threshold, at the threshold, or 0-10% greater than the threshold), the reactor is in _criticality_ and the status code of 'NORMAL' should be output, indicating that the reactor is in optimum condition and control rods are in an ideal position.

- If `temperature * neutrons_produced_per_second` is not in the above-stated ranges, the reactor is
going into meltdown and a status code of 'DANGER' must be passed to immediately shut down the reactor.
Expand Down

0 comments on commit 418e5d2

Please sign in to comment.