Date
at 10:30am MST/PDT
Tucson Location: LSST Conference Room
Videocom: IP 140.252.24.8 (Direct Dial)
Call 1-866-330-1200, Participant Number 860-9352#
Attendees
- Lynne, Peter, Simon, Kem, Srini, Steve, Chuck, George, Cathy
Agenda
Scheduling Workshop (Kem)
- target date is the week of Nov 17
- considering others to invite
- ACTION Srini has two suggestions from UA that have worked with LSST and will send to the email list
Developer Hire Update
- negotiations are in progress
- probably won't move to Tucson right away but can travel regularly
- Kem suggested he travel to Chile for a week to work with Francisco to start getting up to speed on code
• Development planning (do we need to review the mid-level plan to make it official?)
• Design Review documents (we said we would do the review next week- Oct 1 – do we need more than the 1 hour Opsim meeting?)
• MySQL v SQLite - discussion scheduled for Oct 15 (who are interested parties outside lsst-opsim that should be notified?)
• AAS Posters? Drafts for Friday Sims meeting
• JIRA Status and Blockers
• Review assignments from last Fri’s Development Plan (capture issues for JIRA; the below is copied for reference)
All
Write up the simulation framework codes into papers: papers will be based off the SPIE versions (ie expanded). This would provide a set of refereed papers for opsim, catsim, maf that people can cite.
Cathy
Finalize what functionality needs to be in MAF to replace SSTAR
Learn to write metrics and implement any required metrics for opsim in MAF
Implement new plots in MAF required for evaluation of Tier 1 runs
Francisco
Generate a breakdown of tasks for the refactoring of opsim to produce telemetry data and to modularize the scheduler component
Produce a design for the OCS/Opsim framework and submit for design review (including libraries, data structures, api and methodology for the communication)
Start the refactoring
Kem
LSE-190, Scheduler Requirements.
Scheduler experts workshop
Evaluate Tier 1 and rerun if necessary
Additional MAF dev: Anything more needs to be developed?
• Kem - tabular completeness data? Lynne - in summary stats
• do people will want access to the table? Peter - could provide link to data in tables
• can't do side by side plots currently (do it with tabs)
• Put link to data on the plotting page
• Another layer of grouping on page of opsim runs (have categories of the analysis: sstar/cadence etc)
• Srini - this is classified in the run log
• add sort by date (maf and opsim)
• all filters in one histogram (different colors per line)
How do we make this persist (opsim serves the data). Will it just be a big list
• question for opsim to discuss at future meetings
• You can create multiple tracking databases and browser plots using different ports