Flag from config text
The burn settings come from a config file, where every value is text. The file clearly says the burn is not a dry run, but the flight software simulates it anyway, and the real burn never happens.
Predict what the code prints, find out where the False got lost, fix it, then read settings that people type by hand.
Finish stage 1 to unlock this stage.
Don't run the code yet. Read it and decide what it will print. Write your guess in prediction, at the top, between the quotes. Then run it and compare.
Any guess passes this stage: the point is to think before you run. After you check, you'll see your prediction next to what Python printed.
The config says "False". Follow it through bool() and the if.
Finish stage 1 to unlock this stage.
Investigate. Find out what bool("False") and bool("") give and store the answers, True or False, in the two variables. Run them to check, and remove any lines you added before you check.
Modify. Work dry_run out by comparing the text with "True", so it is a real True or False. With the config saying "False" it must print:
Firing the main engine
Finish stage 2 to unlock this stage.
Operators edit this config by hand, so the telemetry setting can be yes, no, true or false, in any case and with stray spaces. Yes and true mean on; anything else means off. Print:
Telemetry: on Telemetry: off
Normalise the value first, as in "Normalise a command", then compare it with both words that mean on, joined by or. For " YES " it prints the first line.
Hints
If-else Statement
# If-else: two possible paths
fuel = 30
minimum = 50
if fuel >= minimum:
print("Status: CLEARED FOR LAUNCH")
print("Fuel sufficient")
else:
print("Status: HOLD LAUNCH")
print("Insufficient fuel!")
needed = minimum - fuel
print(f"Need {needed} more units")
# Crew access check
access_level = 2
if access_level >= 3:
print("Bridge access: GRANTED")
else:
print("Bridge access: DENIED")
Separate arguments with commas. They're passed on every Run as sys.argv[1:].