Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
← Older edit
Scottcal (talk | contribs)
8,097 edits
No edit summary
Scottcal (talk | contribs)
8,097 edits
No edit summary
 
(197 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Looked over Pegasus blog entry, sent comments and list of people involved
*Modify CyberShake to work on RSQSim ruptures
*Emailed OLCF about geo015 purge
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Suspended Study 15.12
*CyberShake training
*Investigated Study 15.12 errors - new manifestation of old seismogram problem
*Update CyberShake study wiki pages to point to SQLite files
*CyberShake call
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Looked at insertion test results, much faster on test DB
*Dumped PeakAmplitudes table with 8 sites x 2 studies for Nenad


== Today ==
== Project Backlog ==
*Monitor Cori test - still waiting...
*Run CyberShake post-processing on RSQSim events, once DB is populated
*OK from Kevin, resume Study 15.12
*Produce candidate site list for Bay Area CyberShake
*Resolve seismogram problems with Study 15.12 sites
*Investigate improved load-balancing for DirectSynth SGT handlers
*AWP source files uploaded, set up and run forward simulation
*Experiment with OMP parallelization for post-processing
*Add wiki page for CyberShake 1.0, upload files
*Investigate getting DOI assigned to Study 15.4 dataset
*Review Blue Waters Graduate Fellowship apps
*Identify ruptures which match CyberShake validation criteria
 
== Blocked ==
*No
 
== Follow-ups ==
*IHPCSS mentoring call
*High-F call
 
== Areas of Responsibilities ==
* CyberShake
* Broadband CyberShake
* Code migration

Latest revision as of 17:56, 1 February 2018

Current Items

  • Modify CyberShake to work on RSQSim ruptures
    • Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
  • CyberShake training
  • Update CyberShake study wiki pages to point to SQLite files
  • Create wiki page for CyberShake RSQSim, and upload sample seismograms

Project Backlog

  • Run CyberShake post-processing on RSQSim events, once DB is populated
  • Produce candidate site list for Bay Area CyberShake
  • Investigate improved load-balancing for DirectSynth SGT handlers
  • Experiment with OMP parallelization for post-processing
Retrieved from "https://strike.scec.org/index.php?title=Staff_Priorities_-_Scott&oldid=19663"