Date

Mar 12, 2014 @ at 10:30a PDT (10:30a MST).

 

Tucson Location:  LSST Conference Room

Videocom: IP 140.252.24.8 (Direct Dial)

Call 1-866-330-1200, Participant Number 860-9352#

Attendees

Agenda

  1. MAF Test installs 
  2. OpSim Dev:  Rolling Cadence / Speed Improvements
  3. New Document set: Scheduler Objectives, Scheduler Development Plan, Scheduler Requirements, etc - Steve
  4. SPIE preparations? - Steve
  5. Cadence Workshop Planning document update - Steve
  6. JIRA Agile - Abi/Cathy
    1. Sprint 2 closing
    2. Sprint 3 assign activity for the coming week

Discussion Items

TimeItemWhoNotes
35min1Iain

MAF: Iain is installing MAF on opsimblitz2, but is having some issues with the installation of healpy. DM is moving away from providing python and is recommending anaconda because it comes with other commonly used packages. We talked around how MAF is intended to work and options for installing. Iain will continue installing as a single user, then attempt to install (using permissions guidelines we just set up) in the multi-user /lsst/maf location; Cathy will run some tests. We will have to develop a convention for the location of output files (probably in individual directories) as there are many different options that can be set in the configuration file.

  Srinisummaryreport.py: Working on reproducing 17.5 hour execution time on opsimblitz1 to troubleshoot summaryreport.py. Will work with Kem to isolate issue.
  SriniHPC: Working with Richard DuBois at SLAC to get an account on HPC cluster. Will install opsim codebase and benchmark and compare with current machines and possible purchase of new machines. Will explore feasibility of parallelizing code to gain speed and document recommendations.
20min2Francisco

OpSim v3.0: looking for easy way for speed improvements; making some code changes but can check into git. Cathy will check on status of CVS -> git.

Rolling Cadence: Initial document has been produced. Kem will work with Francisco to document the implementation and code changes needed for discussion at next week's meeting (or week after). This will provide a venue for input on the functionality before coding begins.

15min3Steve/George

Abi is composing a Response to the Review Committee and creating outlines for the new Scheduler Objectives and Scheduler Development Plan. The Scheduler Requirements and OCS Inputs documents together (long with the Simulator Requirements document) will specify the fixed set of specifications for Construction. The OCS Workshop in April will be an opportunity to plan out dovetailing of work for next 1-2 years.

 4SteveDeferred - no action needed
 5SteveWorkshop planning in progress; documents and websites in development.
2min6CathyWill contact members individually to set up this week's sprint.

Old Action Items