...
- OCS Review - No coordination with Opsim has been requested. Kem and possibly Steve will attend next week.
- Developer HIre - No new information on an offer to the second candidate
- Mid-level planning - new draft was discussed and no pieces are missed
- Code development - this is the top priority - next steps are definition of the modules to break out into independent tools which will generate simulated telemetry & conditions to which the simulator and scheduler will subscribe, and defining the interfaces to the DDS for these. Also how to structure the scheduling logic so that both the simulator and schedulerSimulator and Scheduler can use the same unit of code (interfaces need to be defined). We discussed how we might utilize the upcoming engineering database. Coordination with OCS is needed to take planning to the next level, Kem has planned time with Francisco next week after the review to discuss; Francisco took and has an action item a few weeks ago to identify epic-level items for the next 6 months - 1 year. Documentati
- Cadence Studies - a summary of the verification and tuning studies has been collected and is being reviewed by Cathy & Kem. Remaining issues with the code should be resolved after next week and runs can continue after the v3.2 Release. Analysis would be facilitated if we could figure out how to query more than one DB at a time from one SQLite3 session (as is possible with MySQL).
- Analysis tools development - Lynne will send out a new link for the current "showMAF.py output; Cathy will review and give another iteration of feedback on what is needed to become a "workable replacement" for SSTAR. There was discussion about the workflow and interface with the community, and a concept for how the community contributions to MAF will be managed. Cathy will look into distributing standard sets of runs from OpSim-Tucson machines - this will require showMAF.py to run on opsimcvs.
- Documentation was discussed and Simon described the various tools that DM is using to address different levels of documentation. MAF is looking at doing their documentation in Sphinx, and is there are cookbook or recipe information that can be done in Confluence. Documentation of the newer Simulation/Scheduler code will be important so tools will need to be identified.
- Suggestions for Friday presentations
- Kem will be presenting results from the rolling-cadence simulations and the impact on uniformity.