LOGS (procedures) - Revision history

Thatdoctorperson at 22:57, 27 November 2015

2015-11-27T22:57:03Z

Jared Kelly at 19:58, 26 April 2013

2013-04-26T19:58:02Z

Naue2000 at 20:19, 3 June 2010

2010-06-03T20:19:42Z

Stefanido: MC-LOGS Procedures moved to LOGS (procedures)

2010-04-20T16:33:18Z

MC-LOGS Procedures moved to LOGS (procedures)

Stefanido at 17:17, 6 April 2010

2010-04-06T17:17:21Z

Darth Wombat: made to comply with order, added procedures template

2010-04-03T05:53:32Z

made to comply with order, added procedures template

Stefanido: /* Example MC Shift Monitoring */

2010-03-29T18:27:21Z

‎Example MC Shift Monitoring

Stefanido at 18:26, 29 March 2010

2010-03-29T18:26:15Z

Stefanido at 18:19, 29 March 2010

2010-03-29T18:19:01Z

Stefanido at 18:17, 29 March 2010

2010-03-29T18:17:47Z

@@ Line 47: / Line 47: @@
                  Position      Name           Status
                  FLIGHT        Ramclam        Green
-                 CAPCOM        Storey         Green
+                 CAPCOM        Evans          Green
                  AUXCOM        stand-by       stand-by
                  EECOM         Pelletier      Red

@@ Line 1: / Line 1: @@
-==1.9 MC-LOGS Procedures==
+== MC-LOGS Procedures==
-===1.9.1 Job Description===
+=== Job Description===
 LOGS must record, with timestamp, all interesting occurances during the mission, especially those pertaining to [[Mission Control]] and plans to control the mission.
 Because there is often a chatlog from [[AUXCOM]], LOGS is not required to contain all the details of the current situation, and should be considered a minute by minute summary.
-===1.9.2 Log Worthy Events===
+=== Log Worthy Events===
 This list is not exhaustive:
 *Launch
@@ Line 15: / Line 15: @@
 *Shift change outside of normal procedure
-===1.9.3 Unworthy Events===
+=== Unworthy Events===
 This list is not exhaustive:
 *Any events relating to [[Time Acceleration]] - Note: Time Acceleration should be noted in the [[Unofficial Logs]] in accordance with Unofficial Logs procedures.
-===1.9.4 LOG Header===
+=== LOG Header===
 The top of each log file should contain the following template, filled out appropriately by the first person to man LOGS.
 <pre>
@@ Line 38: / Line 38: @@
 Note that the [[Simulator Commander]]'s full name should be appended to the LOG on a line indicated by "SimCom:" after the mission is completed. This delay is to preserve mission integrity.
-===1.9.5 Stations Check===
+=== Stations Check===
 ====Mission Control Check====
 It is the responsibility of MC LOGS to remind the [[Flight Director]] at 20 minute intervals to verify that each station in [[Mission Control]] is manned by an appropriate staff member, and that all stations report green.
@@ Line 71: / Line 71: @@
 It is the responsibility of MC LOGS to remind the [[Flight Director]] at 30 minute intervals to verify that all stations in the [[Habitat]] are manned by an appropriate [[Astronaut]]. In addition, during this check, each piece of software should be tested to ensure that [[Mission Control]] is receiving the correct telemetry from the [[Habitat]]. Testing the software consists of verifying that all software reads the same time as all the software in the habitat with accounting for the 5s lag in updates.
-===1.9.6 Logging Best Practices===
+=== Logging Best Practices===
 At the start of a new day on Earth, the log should read
 <pre>
@@ Line 111: / Line 111: @@
 </pre>
-===1.9.7 Unofficial Logs===
+=== Unofficial Logs===
 It is also the job of LOGS to record unofficial occurrences in the [[unofficial logs]]. This includes such things as unprofessional behaviour that is particularly amusing, events relating to time acceleration, or anything noteworthy that in some way impinges on [[Mission Integrity]].
 {{Procedure|PrevTopic=GNC Procedures|NextTopic=Observer Procedures}}

@@ Line 17: / Line 17: @@
 ===1.9.3 Unworthy Events===
 This list is not exhaustive:
-*Any events relating to [[Time Acceleration]] - Note: Time Acceleration should be noted in the [[Unofficial Log]]s in accordance with Unofficial Logs procedures.
+*Any events relating to [[Time Acceleration]] - Note: Time Acceleration should be noted in the [[Unofficial Logs]] in accordance with Unofficial Logs procedures.
 ===1.9.4 LOG Header===

@@ Line 115: / Line 115: @@
-{{Procedure|PrevTopic=GNC Procedures
+{{Procedure|PrevTopic=GNC Procedures|NextTopic=Observer Procedures}}
-|PrevNum=1.8
-|ThisTopic='''MC-LOGS Procedures'''
-|ThisNum=1.9
-|NextTopic=SURGEON Procedures
-|NextNum=1.10}}

@@ Line 1: / Line 1: @@
-==1.7 MC-LOGS Procedures==
+==1.9 MC-LOGS Procedures==
-===1.7.1 Job Description===
+===1.9.1 Job Description===
 LOGS must record, with timestamp, all interesting occurances during the mission, especially those pertaining to [[Mission Control]] and plans to control the mission.
 Because there is often a chatlog from [[AUXCOM]], LOGS is not required to contain all the details of the current situation, and should be considered a minute by minute summary.
-===1.7.2 Log Worthy Events===
+===1.9.2 Log Worthy Events===
 This list is not exhaustive:
 *Launch
@@ Line 15: / Line 15: @@
 *Shift change outside of normal procedure
-===1.7.3 Unworthy Events===
+===1.9.3 Unworthy Events===
 This list is not exhaustive:
 *Any events relating to [[Time Acceleration]] - Note: Time Acceleration should be noted in the [[Unofficial Log]]s in accordance with Unofficial Logs procedures.
-===1.7.4 LOG Header===
+===1.9.4 LOG Header===
 The top of each log file should contain the following template, filled out appropriately by the first person to man LOGS.
 <pre>
@@ Line 38: / Line 38: @@
 Note that the [[Simulator Commander]]'s full name should be appended to the LOG on a line indicated by "SimCom:" after the mission is completed. This delay is to preserve mission integrity.
-===1.7.5 Stations Check===
+===1.9.5 Stations Check===
 ====Mission Control Check====
 It is the responsibility of MC LOGS to remind the [[Flight Director]] at 20 minute intervals to verify that each station in [[Mission Control]] is manned by an appropriate staff member, and that all stations report green.
@@ Line 71: / Line 71: @@
 It is the responsibility of MC LOGS to remind the [[Flight Director]] at 30 minute intervals to verify that all stations in the [[Habitat]] are manned by an appropriate [[Astronaut]]. In addition, during this check, each piece of software should be tested to ensure that [[Mission Control]] is receiving the correct telemetry from the [[Habitat]]. Testing the software consists of verifying that all software reads the same time as all the software in the habitat with accounting for the 5s lag in updates.
-===1.7.6 Logging Best Practices===
+===1.9.6 Logging Best Practices===
 At the start of a new day on Earth, the log should read
 <pre>
@@ Line 111: / Line 111: @@
 </pre>
-===1.7.7 Unofficial Logs===
+===1.9.7 Unofficial Logs===
 It is also the job of LOGS to record unofficial occurrences in the [[unofficial logs]]. This includes such things as unprofessional behaviour that is particularly amusing, events relating to time acceleration, or anything noteworthy that in some way impinges on [[Mission Integrity]].

← Older revision	Revision as of 16:33, 20 April 2010
(No difference)

@@ Line 44: / Line 44: @@
 ====Example MC Shift Monitoring====
 <pre>
-- LOGS reminds flight to perform station check.
+- LOGS reminds FLIGHT to perform station check.
                  Position      Name           Status
                  FLIGHT        Ramclam        Green

@@ Line 20: / Line 20: @@
 ===1.7.4 Stations Check===
 It is the responsibility of MC LOGS to remind the [[Flight Director]] at 20 minute intervals to verify that each station in [[Mission Control]] is manned by an appropriate staff member, and that all stations report green.
@@ Line 48: / Line 49: @@
 ***Stand-by: This station is not being monitored, or is not able to report their status.
 It is the responsibility of MC LOGS to remind the [[Flight Director]] at 30 minute intervals to verify that all stations in the [[Habitat]] are manned by an appropriate [[Astronaut]]. In addition, during this check, each piece of software should be tested to ensure that [[Mission Control]] is receiving the correct telemetry from the [[Habitat]]. Testing the software consists of verifying that all software reads the same time as all the software in the habitat with accounting for the 5s lag in updates.