...
We discussed and agreed on option 4.
- This means (maybe) we will have a separate database file for every sessionID (recorded in a tracking DB) whether it is MySQL or SQLite**.
...
- OpSim will most likely continue to use the MySQL option internally
...
- The conversion tool to produce an SQLite file for distribution when needed
...
- will be included in OpSim to phase
...
- out to keep things simple and less prone to bugs if schemas get out of sync.
- There will be both internally (v3.2) and externally facing repositories (externally facing will use SQLite).
These are the tasks and time estimates to (TBD) to implement this plan:
- Add code to choose whether to run on SQLite or MySQL (database agnostic)
- itemize the steps needed here
- continued
- **Reassess for MySQL whether creating a single DB for all sessionIDs v. creating a single DB for each sessionID is a good decision
- this has ramifications for MAF which doesn't operate on the first but can operate on the second
- in planning to execute many runs, a single DB for all sessionIDs will get quite large and performing joins could get cumbersome.
- Make changes in DB schema make schema changes in DB (make sure SQLite and MySQL match)
- needs wfd tag - implemented in simulator
- conversion tool changes to use wfd tag
- MAF will need a layer to interact with single MySQL files (??)
- ; moving conversion tool inside of OpSim instead of a stand alone tool
- Add "universal" tag to Proposal table (already added to Config table in v3.2)
- Eliminate need to manually adjust visitTime and visitExpTime
- Create create master script to run entire pipeline with no manual intervention needed (simulator, standard maf output, relocate files to repository)
- production Production and testing needed for translation layer Set up internal repository (plan and/or implement external repository)layer (not sure what this means as far as tasks)
- Internal repository was set up in v3.2; plan and implement external repository for v3.3
- Update Sphinx documentation with differences in function as well as installation if applicable