Below are my comments/inputs for the TRACE L&EO Script

Pass #1
* Make disabling of RTS 12, 15, SPE deployment commands optional and only if arrays have been deployed and verified by team consensus (Mechanical/ACS/Systems Engineer)
 
Pass #2
* Stop/disable RTSs, SPE Deployment (if not already done)
* Dump VC1 data and verify safehold (trending)
* Note: No vc2 data will be present until instrument fully configured and taking pictures


Pass #3
* AOS 1125K
* Command to DSP
* Dump VC1 data and verify safehold (trending)

Pass #4 - Short pass
* AOS 1125K
* Load ATS with vector, magcals, AOS/LOS times
* Dump VC1 to verify DSP (trending)

Note:  Do not need to downlink table 66 to verify CMD status because no commands will have been executed to verify at this point.  This operation is not really necessary - it was a carry over from SAMPEX days.  If commands do not work, i.e. no passes, then we will dump it to debug.

Pass #5
* turn on NEB
* turn on DPU
* turn on decontamination heater bus
* set CCD bi-level heater level (TBD)
* Events/VC1 dump via ATS - verify DSP and magcals (trending)
* Patch load with improved vector to ATS A

Pass #6 (5:37)
* Load ATS B for day 2
* Events/VC1 dump via ATS - verify DSP (trending)

Pass #7 (9:29)
* ISP preview - wheels, gyros ON
* Events/VC1 dump via ATS - verify DSP (trending)

Pass #8 (7:31)
* Events/VC1 dump via ATS - verify ISP Preview
* Catchup??

Note: Any changes to the magnetic contamination matrix can be made anytime after the magcal data has been examined by ACS.  This will probably not be needed and probably does not need to be on you script - it scares/excites people.

End day one

Backup Shift
* Continue to dump VC1 and trend ISP Preview Data


Day 2

Pass #1
* Command Inertial Sunpoint
* Events/VC1 dump via ATS - verify ISP Preview

Note:  There are comments in your script about loading ATS B.  This was performed on Day 1.  At some time during the day you will reload ATS A.

Pass #2
* Control Computer thermal init, Instrument Operational Heaters ON
* DHC Initialization
* Instrument sequence loads to DHC on time available basis (probably won't be needed by time launch rolls around?)
* Events/VC1 dump via ATS - verify ISP (trending)

Pass #3
* CCD camera and mechanisms ON
* Mechanisms aliveness proc


More Notes:
1.  Launch script is cluttered with contingency notes.  Do not overplan this. The script should be a sequence of events with an order of execution based on what has previously been done.  Re-planning is inevitable so do it when the time comes but not before.