procedure for Ascent/Entry ES1

[mdbernard]

Create a fine-grained procedure for ES1 (references this comment). Add as a markdown file in proc/ascent-entry/ES1.md. Reference RPOD ES4 Procedure.

[cadojo]

@mdbernard Can you clarify the ES1 and TO1 terminology in the comments you referenced?

I'm guessing...

• TO1 --> Take-Over Point 1

• ES1 --> Event Sequence 1

Are Event Sequences specific to each team (e.g. ascent-entry has an ES1, rpod has an ES1, etc.), or are Event Sequences unique mission-wide?

[mdbernard]

@cadojo Yes, you've got those right. TO = Take-Over Point, ES = Event Sequence, HO = Hand-Over Point. Is it clunky terminology? Yes. Does it fully describe what's happening? Also yes 😅. I'll make sure to bring this up at our next team meeting.

Event sequence numbers start at 1 for each team. If you look in src/sequence_controllers, you can see there's another number near the start of those filenames which defines the execution order for the mission. The event sequence numbers are effectively just a tool to help chunk up each team's timeline to make things feel more manageable.

[cadojo]

Preliminary design outlined in PR#60.