You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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

  • ACTION Cathy will work with Kem to update the plan spreadsheet (which will define epics in JIRA) to take into account the latest developments

Design Review (week of Oct 1)

  • This is to be a Conceptual Design Review of documents presented by Francisco which will map out the steps needed to formulate a design in time for a Design Review in mid-Dec
  • ACTION Cathy will send out doodle poll to set up a time separate from Opsim meeting (preferred to be earlier in the morning for Europeans but later in the morning for those with kids)

MySQL v SQLite

  • We held an extended discussion about the various issues that are connected to this.
  • ACTION Srini will create a confluence page with a proposal for how to move forward, capturing these issues, especially ones Simon brought up
  • We will likely hold a follow-up discussion Oct 15 (we should make sure to notify other interested parties)

AAS Posters (Drafts for Friday Sims meeting)

  • Kem suggested that OpSim-UW consider putting together a poster that would summarize and explain MAF to the community - encouraging involvement
  • ACTION Lynne will consider this and talk to OpSim-UW

JIRA Status and Blockers

  • Kem - reviewing final change on transient fix (blocking commit)
  • Cathy - trying to install MAF on opsimcvs with little success (Lynne and Simon are available for questions)
  • Cathy - can't read tusken.astro.washington.edu:8888 from outside NOAO_ will diagnose
  • ACTION - Cathy will work with Kem to commit new default config files as well as new downtime file.

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

  • No labels