1. ALMA Integrated Computing Team Coordination & Planning Meeting #1 Santiago, 17-19 April 2013 ICT Group planning: Scheduling Jorge Avarias ICT Scheduling Group Lead

2. Scheduling Group Overview People  Jorge Avarias (also participating in Control group)  In Practice 0.5 FTE  Eventually 1 FTE will be allocated Responsibility  Scheduling Group is in charge to develop the software.  Help to achieve optimizations.  DSO defines background (algorithms, training mechanisms, weather forecasting, calculation formulas, etc).

3. Scheduling software parts Scheduling Array online component  Online queue OMC Scheduling Panel  To queue SchedBlocks into an array  Check information related to ObsProject/SB Scheduling Updater  Converts APDM ObsProject/ObsProgram/SB into relational scheduling model. Dynamic Scheduling Algorithm (DSA) Planning Mode Simulator (APRC simulator)

4. Deliveries since 2012 Coordination Meeting Bookkeeping.  Scheduling writes to state archive the exec status for a SB observed. Check for calibrators and change status of the SchedBlocks accordingly.  Plug-in for the state system and Scheduling updater checker.  Still missing the python script to check in calibrator catalog. Cycle 1 version of Planning Mode Simulator. Refactoring of Scheduling Updater – performance improvements. 1-Day Planning Simulator.  DAO to access to the weather forecast from APEX. New Selectors for DSA.

5. Current Planning Process New features are mainly concentrated on DSA and simulators. Bi-weekly scheduling meeting is the main discussion point to decide priorities and planning.  DSO representatives participate in the meeting (Masao and occasionally Andreas and Baltasar)

6. Upcoming features “Recession” period:  Improvements in usability of the Scheduling Panel After “recession”:  DSA improvements  Simulator improvements  Receiver band management?

7. ICT-CPM1 17-19 April 2013 Current testing status Scheduling has unit tests covering ~30% of the written code for the online system.  This doesn't include DSA parts (selectors and scorers), APDM model conversion, DB connections. Unit Tests are run after every commit to subversion is done. Every new feature and change done to scheduling includes a new unit test, if possible. Integration and performance tests are run manually.

8. ICT-CPM1 17-19 April 2013 Current testing status