1 Orbit Packing Changes for Cycle 12 Tom Donaldson

2 Overview Orbit Packing Today Orbit Packing in APT Orbit Packing in Cycle 12 Ops  Retransing Cycle 12 Proposals  Retransing Earlier Proposals Dependencies Wrap-Up

3 Orbit Packing Today Exposure specifications are defined in “.prop” files using PED or text editor. Trans expands the exposure specifications into the actual exposures. User has no control over individual expanded exposures.

4 Orbit Packing Today (cont’d) Trans assigns expanded exposures to orbits, adjusting their durations to “optimize” the orbit packing. The DG displays orbit packing results. Viewing the effects of changes to a proposal requires rerunning the entire proposal through the Preprocessor and Trans.

5 Expand exposure specs into actual exposures. Compute default durations of expanded exposures. Adjust expanded exposure durations for instrument constraints. Adjust expanded exposure durations for orbit packing. Assign expanded exposures to orbits. Orbit Packing Actions S/W PED/emacs Use “.prop” file. PP Trans RPS2 DG PMDB PLIB PC Toolbox Syntax check. Define exposure specifications. User View orbit packing. Orbit Packing Today – PC’s and PI’s Repeat process as needed.

6 Orbit Packing in APT APT will replace RPS2 in cycle 12. Exposure specifications will be defined in “.xml” files using APT, not text editor. User will be able to specify duration and orbit for expanded exposures. Trans will not adjust expanded exposure durations for orbit packing. Orbit Planner will display orbit packing results. Viewing the effects of changes to a proposal requires only a partial run through Trans.

7 Expand exposure specs into actual exposures. Compute default durations of expanded exposures. Adjust expanded exposure durations for instrument constraints. Adjust expanded exposure durations for orbit packing. Assign expanded exposures to orbits. Orbit Packing Actions S/W Trans APT Syntax check. Define exposure specifications. User View orbit packing. Orbit Packing in APT Repeat process as needed. Orbit Planner APT Proposal Editor Use “.xml” file.

8 Orbit Packing in Cycle 12 Ops APT will not replace PC Toolbox in cycle 12. “.xml” file will be primary proposal representation, but will be converted to “.prop” for use in Ops. “.prop” files will contain duration and orbit number for expanded exposures. Changes to proposal need to be made in APT, not PED or text editor.

9 Orbit Packing in Cycle 12 Ops (cont’d) Trans will adjust expanded exposure durations up to 20% to optimize orbit packing (available mid cycle 12).

10 Expand exposure specs into actual exposures. Compute default durations of expanded exposures. (As specified in APT) Adjust expanded exposure durations for instrument constraints. Adjust expanded exposure durations for orbit packing. (Optional) Assign expanded exposures to orbits. (As specified in APT) Orbit Packing Actions S/W APT Use “.xml” file. PLIB and PP Trans DG PMDB PC Toolbox Syntax check. Define exposure specifications. User View orbit packing. Orbit Packing in Cycle 12 Ops Repeat process as needed.

11 Retransing Cycle 12 Proposals To minimize manual effort needed to retrans proposals, Operational Trans will adjust expanded exposure durations up to 20% to optimize orbit packing.

12 Retransing Earlier Proposals Proposal created prior to cycle 12 will not have orbit assignments for expanded exposures. Without those orbit specifications, Trans cannot be guaranteed to recreate the same orbit structure it had when the last time it was processed. We address this with two plans…

13 Retransing Earlier Proposals – Plan A Allow Trans to recompute the orbit packing. If we don’t like the orbit packing it created, we could:  Live with using APT to edit the proposal to create a better packing.  When the packing is acceptable except for exceeding the orbit allocation, allow the extra orbit(s). During development, analyze new Trans orbit packing to see how much it matches old Trans.

14 Retransing Earlier Proposals – Plan B (if analysis shows new Trans orbit packing differs greatly from that of old Trans) Trans could be configured to write a report detailing the orbit packing. All outstanding proposals could be run through that version of Trans to create a record of the “correct” orbit packing. That record could then be fed to Trans whenever one of those proposals was retransed.

15 Dependencies This new operational flow depends on development in:  Orbit Planner  APT infrastructure  Trans  RPS2  PC Toolbox Most work to complete by mid summer,  Currently on schedule.  Allows time to react if problems come up. Operational integration in 4 th quarter, 2002.

16 Wrap-Up The transition to APT will cause significant changes to the operational work flow. Development and testing will be coordinated with the Trans team and the PC team. This document is available off the orbit planner web page:

17 Orbit Planner Schedule