11 Dec 2013 Meeting

Meeting Notes and Assigned Tasks

Meeting Announcement and Agenda

We will meet tomorrow, Wednesday to resume our weekly meetings at 9:30 PST / 10:30 MST.

Tucson Location:  LSST Conference Room

Videocom: IP 140.252.24.8 (Direct Dial)

Telecom: 1-866-330-1200 Participant Code 860-9352#

 Agenda and notes also published on Confluence:https://www.lsstcorp.org:8443/display/SIM/11+Dec+2013+Meeting

I am copying my to-do list from our meeting last week at the FDR that can serve as an agenda.

Tasks

• Abi - fill out and submit Review Plan
• Cathy - DataAccess Page - emily

OpSim v3.0

• OPSIM-7: Scheduler.conf and SchedulingData.conf key values not stored in the DB
• OPSIM-39: Edit default proposal files and parameters in LSST.conf
• Remove conf files that are obsolete; and parameters that are no longer used - recalcskycount, reuserankingcount in each prop ; leaving in Scheduler.conf; delete useLookAhead
• OPSIM-59: For sequence proposal DDcosmology1.conf (e.g. opsimblitz1.1053) number of visits only works for u , not grizy (deferred to v3.x)
• OPSIM-60: Materialize output tables in OpSim databases (defer)
• OPSIM-61: Clean up src directory tree removing unused python modules
• OPSIM-xx: Nested subsequences doesn't work (defered)
• OPSIM-xx: move important params from Universal configs bottom to top of file (defer)
• Testing - unit tests (complete?)
• Validation (should be encompassed by existing runs, but do one complete comparison run)
• Release OpSim v3.0 & install on production machines

SSTAR v4.0

• OPSIM-53: summaryreport SQL queries taking too long (defer to 4.x)
• complete nested sub-sequence run [Kem] (defer to 3.1)
• run SSTAR on that run [Srini]
• modify SSTAR code if necessary [Srini]
• modify OpSim code if necessary [Kem]
• repeat or move on to validation
• validate SSTAR v4.0 (include final v3.0 run) [Cathy]
• Release SSTAR v4.0 & install on production machines [Srini]

Documentation

• Simulator requirements [Francisco] (see below) Srini to send docushare link-
• Overview [Abi] **
  • overview of how we are doing what we are doing - overarching philosophy why a tool, why this form, why not someone else's code?
  • motivate scheduler AND simulator
  • Include or refer to requirements document [Francisco]
  • structure of how the models are broken out and
  • logical flowchart of decision making
  • point out various functions at different times of the project
• Simulator description ** - How does it actually work -  (technical journal article, refer SPIE paper - based on this and different in these ways…) [Francisco]
• Conceptual APIs for the for the Scheduler (interface with OCS)
  
  • but don't turn into a review of what it is going to become
  • framework in which we are going to test the new scheduling algorithms
  • API between simulated scheduler and actual scheduler
  • what streams and what information needs to be exchanged (not precise interfaces)
• Sphinx documentation on SSTAR *(how to install, run, what comes out) [Srini]
• Sphinx documentation on OpSim * (how to install, change parameters, output) [Srini]
  • overview incl Francisco how the code works reference
• Post-processing tools: SSTAR+ (explains) + other output (validates code; annotate sample SSTAR) [Srini]
• Post-processing tools: Metrics  (SSTAR+ doesn't do it all, need other science cases; give examples of 7- reshape PST) now need MAF so… [Steve/Srini]
• MAF design and development plan [Steve/Srini]  (Present the MAF code design for approval)
  • maybe just the requirements (or proposed requirements) (include Lynnes && Steves??)
  • use cases -
  • architectural design
  • maybe prototype class designs
  • need to have it done by may for workshop (June
• Validation v3.0 [Cathy]
• Cadence runs [Kem - defer to after review?]
• Baseline run like opsim3.61 - reference run? [Kem] -