This is my action item from the Visit Planner meeting. I am attempting to organize all the PI modifiable aspects of an observation that effect scheduling. There are two reports: the first one lists the things that can be changed, the second attempts to break those down by which Spike constraint they effect. Please read (and even comment) before our next meeting. - Karla p.s. You will want to print this in landscape mode. ------------------------------------------------------------------------- 1) Going through the current RPS2 syntax and listing features that can be tweaked to effect scheduling: Target specification Fixed target specification Target Position Moving target specification Target Position (Level 1,2,3 or Ephem) MT Windows Pattern specification Number_of_Points Point_Spacing Pattern_Orient Visit specification Visit_Requirements PCS Mode Guiding Tolerance Drop to Gyro if Necessary Orient Orient From (another visit) Same Orient As (visit) CVZ Sched Notrack After (a date) After (a visit) Before (a date) Between (two dates) Group (some visits) Within (some time) Sequence (some visits) Within (some time) Exposure specification How they under or over fill orbits Special_Requirements Position Target Pattern RT Analysis Requires Ephem Correction Low-Sky Shadow Phase Save/Use Offset PC modifiable: GSPair Exp PCS Mode GS Acquisition Scenario ------------------------------------------------------------------------- 2) Per Jesse's suggestion and with Drew's help I have attempted to list all the constraints that are graphed in RPS2 and what HST requirement and/or User specification effect that constraint. HST Req User Control "Physical Constraints": ------- ------------ Sun Sun Angle Target Position Moon Moon Angle Target Position Guide Stars Guiding stars Target Position, (GS Acq Scenario), Pos Targs, Pattern, Orient, Drop to gyro, PCS Mode, Guiding Tolerance, Ephem Corr, Notrack, (Exp PCS Mode), (GS Pair) Target Visibility Earth Limb Angles Target Position, How orbits filled, Sched, CVZ, Shadow Moving Target Target Position, MT Windows "Absolute User Constraints": Between Between (two dates) After After (date) Before Before (date) Phase Phase Low Sky Low-Sky Absolute Orient Solar Panel Angles Orient "Relative User Constraints": Timing Link After (visit), Group Within, Seq Within Save/Use Offset Save/Use Offset (implies an After link), RT Analysis Orient From Orient From (visit) Same Orient Same Orient As (visit) Ephemeris Correction Req Ephem Corr (if used in multiple visits implies a Same Orient link)