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 518-2287#

Attendees

  • Kem, Andy, Francisco, Srini, Lynne, Cathy, Simon - who else??

Agenda

update scheduling workshop

  • additions to Andy’s list:  Srini profs, Phil Pinto

details on developer hire (he is!)

 Status

  • JIRA handoff status
  • LSE-190 status
  • palpy conversion
  • config file updates

 Planning

  • when release opsin 3.2 (what is still needed?)

 MEAT of the meeting:

  • Mysql vs Sqlite  report from Srini (should be on Confluence, but couldn’t check just now—Confluence seems to be down, getting '504 Gateway Time-out’)

 Discussion

 JIRA-=Updates, Blockers and new Sprint

Notes

Workshop attendees so far are

• Mark Johnson (SPIKE, JPL)
• Tony Barrett (JPL)
• A. I. Gomez de Castro (Madrid, GTC)
• Sotiria Lampoudi (UCSB, LCOGT)
• Eric Saunders (LCOGT)
• Bob Vanderbei (Princeton)

Release of v3.2 - Will include

  • no DB changes - except to make sure schema is the same between mysql and sqlite
  • palpy instead of slalib
  • conversion tool - MySQL to SQLite
  • add tags to Config table ("Universal" or "WFD"??)

ACTION - Kem will set up a confluence page and he, Srini and Francisco will itemize the features that will be included and the tasks still to be done.

changes for v3.3

  • ACTION - write up task plan and estimates (Srini?)

On track to deliver a way to run both the simulator and MAF in one stroke for next summer.

MySQL v SQLite

There are four options for moving forward:

  1. continue as now: run opsim on mysql,, post process to yield a sqlite file, run maf on sqlite
  2. run opsim on mysql but directly generate sqlite file, run maf on sqlite
  3. run opsim on sqlite solely
  4. convert opsim to be ‘database agnostic’

We discussed and agreed on option 4.  This means we will have a separate database file for every sessionID (recorded in a tracking DB) whether it is MySQL or SQLite.  OpSim will use the MySQL option internally, and will use the conversion tool to produce an SQLite file for distribution when needed, but we would like to phase this out to keep things simple and less prone to bugs if schemas get out of sync.

Here are some things that will be needed to implement this plan (which will be completed not for v3.2 but possibly for v3.3)

  1. make schema changes in DB (make sure SQLite and MySQL match)
  2. needs wfd tag - implemented in simulator
  3. conversion tool changes to use wfd tag
  4. MAF will need a layer to interact with single MySQL files (??)
  5. create master script to run entire pipeline (simulator, standard maf output, relocate files to repository)
  6. production and testing needed for translation layer 

ACTION: A confluence page will be set up to itemize what needs to be done (Cathy), along with estimates for the work (Srini) so we can forecast a release date.

 

  • No labels