Date
at 9:30am PST
Tucson Location: LSST Conference Room
Videocom: IP 140.252.24.8 (Direct Dial)
Call 1-866-330-1200, Participant Number 518-2287#
Attendees
Michael, Steve, Cathy, Kem, Peter, Lynne
Agenda & Notes
Refining the purpose of Friday Opsim meeting (Kem)
- often we are duplicating talk time with Wed sims meeting
- let's restrict to talking about specific issues: strategies for surveys and results, coding and design issues
- move to Mon, Tues, Thu, stand-up meetings - specific coding issues and move things along - TBD after next week
Review Opsim Spring goals (Kem)
- Jira items should reflect the goals on the Spring Work 2015 on confluence; next sprint will evaluate this.
- detailed review is postponed - will discuss goals
Computing and IT issues (Cathy & Kem)
- opsimcvs is an older machine; may not be able to install stack
- set up accounts for Kem and Cathy on "production" machines (or Lynne's machine)
- copy output files to there to serve with showMaf.py
- talk to Lynne about directory structure
Review new work flow (Cathy)
- review concerns about new states
Lingering JIRA issues (all)
- make "flagged" in its own column
- assignee issue
- how to track versions for opsim code and differentiate from other codebases.
- need version and roadmap features
Plans for meeting next week (Kem, Michael, Francisco, Cathy)
- lookahead
Plans for tagging releases (will there be more?) and v3.2.2 (Michael)
- policy for release - what do we do when we issue a new
- speak up if you want any changes in v3.2.2 - to be released soon because we are planning to freeze that version
AOB
Next week
- agenda
- primarily focus on developing skeleton of APIs for refactored opsim and scheduler (and classes)
- understand how system engineering and T&S will coordinate work
- document the plan in preparation for a more formal review
- MAF - split up sstarDriver.py into engineering and scicollabs reports
- room 78B