Agenda

  1. SPIE (present v3.0 or MAF?)
  2. AAS – booth presentation, other
  3. Documents List & Dates
    1. Docs for team review - Nov 30, 2013
    2. Internal reviewing of docs - week of Dec 23, 2013
    3. OpSim Dry Run - week of Jan 20, 2014
    4. OpSim External Review - week of Feb 3, 2014
  4. Release of OpSim v3.0 & SSTAR v4.0
    1. Remaining issues?
    2. JIRA management
  5. Metric Analysis FrameWork Design – 
    1. update
    2. git layout
  6. The Dreaded Monthly Report

Closed Action Items

  • All - Monthly Report draft will be circulated tomorrow - submit your content
  • All - Outlines for all documents to be reviewed at the meeting next week
  • Abi - Draft 2 day agenda for Technical Review to meet Charge
  • All - Add your travel to the Workspace calendar

=====================

OpSim Team Weekly Meeting

Attendees:  Srini, Cathy, George, Kem, Francisco, Andy

Notable

SPIE

AAS – present at booth if time allows - defer for now

Release of OpSim v3.0 & SSTAR v4.0

  • Francisco and Srini to manage JIRA issue status
  • Francisco to add remaining items in JIRA as issues
  • Remaining items to be done Nov 30 for both codebases
  • Validation can continue as there is no functional difference between beta and remaining changes
  • Defer altering the proposal class names to v3.1
  • Put in git after the review - have a planning session to discuss tagging with an open source license (slalib)
  • Andy wants to discuss slalib alternatives at Friday's ImSim meeting - will arrange for Francisco to be there or reschedule meeting; Srini will also be attending regularly
  • Andy will check with Lynne and Peter for a more optimal time to meet for OpSim

Metric Analysis FrameWork Design

  • Progress on design is continuing; while email communication is good it will be better to start keeping a record of minutes and meetings on a page on confluence so late-comers can view the history and it's all in one place.
  • git repository structure will look like:
  • sims/operations/opsim - for Simulator
  • sims/operations/maf - for Metrics Framework
  • sims/operations/sstar - for Standard Report
  • These code bases may or may NOT be the versions released at the Community meetings next year
  • Higher level directories may contain certain models that are project wide and commonly used between groups

 Technical Review

  • Documents:  outlines should be uploaded to Collection -3288
  • We may need to set a specific time to discuss content and cross over between documents
  • Presentations should open with which item from the Charge will be addressed
  • A mock-up of an agenda was discussed and Cathy will post to the confluence page for the Technical Review
  •  (https://www.lsstcorp.org:8443/display/SIM/OpSim+Technical+Review)

Point

Editors

Item/Component

Srini

Cathy

Release SSTAR v4.0

Document: SSTAR Codebase Description

Srini

Steve

Metrics Analysis Framework

Steve

Srini

Document: Metrics

Abi

Kem, Steve

Document: Path to the Scheduler (incl. budget)

Francisco

Kem, Abi

V3.0 remaining clean up & release (Nov 30)

Document: Simulator Requirements

Document: Simulator Description

Kem

Abi, Steve

Document: Reference Run Package for CCB

 

Cathy

Kem, Francisco

Document: Validation

The Dreaded Monthly Report

  • Not discussed but will be submitted as is

Action Items

  • Kem - submit a request on the Change Control Board website (Cathy will create a collection: Coll-3290)
  • Francisco - Add remaining v3.0 issues to JIRA
  • Francisco - Work with Andy to attend Friday ImSim meeting to discuss slalib - or find a new ImSim time
  • Andy - Ask Lynne & Peter if they can attend current OpSim meeting time or propose a new time.
  • Srini – write up the plan for switching bug/tracking software from Mantis to JIRA, with a solution for the Run Log.
  • Cathy - work with Kem and Iain to backup old machines and relocate data to newer machines.
  • Srini - SSTAR histograms don't get created on opsimblitz1;  SSTAR doesn't run on Steve's machine

 

 

  • No labels

1 Comment

  1. For the git layout:

     - the proposal is to have a structure the looks like

    sims/operations/sstar

    sims/operations/opsim

    sims/operations/maf