xops-pat/examples/STS-134_EVA1/egress.yml

Procedure generator for on space operations

# Title and expected duration of the task
title: EGRESS/SETUP
duration: 25

steps:

  # First steps in IV column (first column)
  - IV:
    - step: Record PET start time ____:____ (Pwr to Batt)
    - step: Start WVS Recorders

  # FIXME: how to handle the "initial configuration" heading. Do we even do that
  #        in procedures anymore?

  # Steps in EV1 column (second column)
  - simo:
    EV1:
    - step: "{{CHECK}} All gates closed & hooks locked"
      checkboxes:
        - R Waist Tether to EV2 Blank hook
        - Red hook on L D-ring ext
        - Yellow hook on Green ERCM
        - Green hook on Red ERCM
        - Blank hook on MWS
    EV2:
    - step: "{{CHECKMARK}} All gates closed & hooks locked"
      checkboxes:
        - All gates closed & hooks locked
        - R Waist Tether to A/L D-ring ext
        - Red hook on L D-ring ext
        - Yellow hook on Green ERCM
        - Green hook on Red ERCM
        - Blank hook to EV1 R Waist Tether

  # FIXME: How to handle "EGRESS/SETUP" header after initial configuration.

  # EV1's step "open thermal cover" should really drive the IV's step to start a
  # clock. The steps below show the YAML equivalent to the STS-134 procedure.
  - EV1: Open hatch thermal cover
  - IV: "Start Hatch thermal cover clock PET (30 min) ____:____"

  # The next step is an ALTERNATE to the EV1 and IV steps above that merges
  # these into a single block (since one drives the other).
  - IV + EV1:
    - step: "EV1 open thermal cover. IV start clock (30 min) ____:____"

  # And here's another alternate. This would indicate that one step has a step
  # in another column that must follow it.
  - EV1: Open hatch thermal cover
    causes:
    - IV: "Start Hatch Thermal Cover clock PET (30 min) ____:____"

  # # # End of alternate methods # # #

  - EV1: Egress A/L

  - EV1 + EV2:
    - step: Transfer EWC ORU Bag to EV1
      checkboxes:
        - Position CETA ORU bag near hatch

  - EV2: Egress A/L


  # FIXME: Perhaps this should be a "simo" block. Two essentially identical sets
  #        of steps, one in each column, performed at the same time. How to
  #        visually indicate "simo" in the display format (not in YAML)?
  - EV1 + EV2:
    - step: Perform buddy checks
      checkboxes:
        - MWS tabs up
        - BRT tab up
        - tether configs
    - step: Verify SAFER config
      checkboxes:
        - {{CHECKMARK}}L handle down (MAN ISOL Vlv - Open)
        - {{CHECKMARK}}R handle down (HCM - Closed)
    - step: {{CHECKMARK}}WVS - Green LED


  - simo:
    IV:
    - step: "Post crew egress, WVS Software:"
      substeps:
      - step: select page - RF camera.
      - step: Sel 'Advanced Controls'
      # I'm not sure about the indenting on this one in the real procedure. We
      # don't do all these steps anymore.
      - step: S-Band Level (two) - Max
    EV1:
    - step: Perform buddy checks
      checkboxes:
        - MWS tabs up
        - BRT tab up
        - tether configs
    - step: Verify SAFER config
      checkboxes:
        - {{CHECKMARK}}L handle down (MAN ISOL Vlv - Open)
        - {{CHECKMARK}}R handle down (HCM - Closed)
    - step: {{CHECKMARK}}WVS - Green LED
    # EV2's steps are a copy/paste of EV1.
    EV2:
    - step: Perform buddy checks
      checkboxes:
        - MWS tabs up
        - BRT tab up
        - tether configs
    - step: Verify SAFER config
      checkboxes:
        - {{CHECKMARK}}L handle down (MAN ISOL Vlv - Open)
        - {{CHECKMARK}}R handle down (HCM - Closed)
    - step: {{CHECKMARK}}WVS - Green LED



  # FIXME: Add alternate view to EV1 + EV2 above?


  # SIMO steps
  #
  # Minimal formatting: Below I do '''BLANK''' to bold the words. This is
  # MediaWiki (e.g. Wikipedia) syntax for bolding. People are generally familiar
  # with this syntax in our organization, so it's preferable. It's also probably
  # a lot harder to find an existing library that does this, whereas finding one
  # that does Markdown formatting is probably easy. So: do MediaWiki if you can,
  # but Markdown is fine as long as you make it fairly easy to drop in a
  # MediaWiki formatter in place later.
  - Simo:
    EV1:
    - step: Translate to S0 Port Struts
    - step: Attach EV1 '''BLANK''' hook to port-outboard strut
      checkboxes:
      - {{CHECKMARK}} Gat closed, hook locked, reels unlocked, release RET
    - step: Attach EV2 '''BLANK''' hook to port-inboard strut
      checkboxes:
      - {{CHECKMARK}} Gate closed, hook locked
    - step: Release EV1 R Waist Tether from EV2 '''BLANK''' hook
    EV2:
    - step: Retrieve CETA ORU bag, stow on BRT with RET

  # This corresponds to page 7-20, EV1 step 12 and EV2 step 8. I've re-written
  # it to be one step in a shared (merged) column.
  - EV1 + EV2:
    - step: On '''EV1 GO''', EV2 release right Waist Tether from Airlock internal D-Ring

  - Simo:
    EV1:
    - step: Translate forward along Lab.
    # "HR" means "handrail". At some point in the future it may be cool to use
    # some sort of template here like: "on Lab HR {{HR|0260}}, {{HR|0259}} ..."
    # that allows us to generate links to our CAD/VR model of the space station.
    # This way people who are reading along and thinking "where is HR 0260" can
    # just click a link and see in the model (assuming they're viewing in an
    # HTML, not printed, version).
    - step: Stow EWC ORU bag on Lab HR 0260, 0259 with hinge ISS aft
    - step: Translate to S1 Face 1, zenith - MISSE 7 Retrieve
    EV2:
    - step: Close hatch thermal cover
    # best here would be to add IV's step using "causes".
    # causes:
    # - IV: "Stop Hatch Thermal Cover clock PET (30 min) ____:____"
    - step: Perform translation adaptation
    - step: Translate to S1 Face 1, nadir - MISSE 7 Retrieve
    # If not able to do the "causes" block above, do this:
    IV:
    - step: "Stop Hatch Thermal Cover clock PET (30 min) ____:____"