Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
Scottcal (talk | contribs)
No edit summary
Scottcal (talk | contribs)
No edit summary
 
(224 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Monitored Study 15.12, 62%
*Modify CyberShake to work on RSQSim ruptures
*Plotted velocity smoothing results, found issues, made code revisions
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Looked at server for DB test, asked John to mount SCEC disks
*CyberShake training
*Installed, built CyberShake codebase dependencies on Cori
*Update CyberShake study wiki pages to point to SQLite files
*Create wiki page for CyberShake RSQSim, and upload sample seismograms


== Today ==
== Project Backlog ==
*Update Pegasus to 4.6 on shock
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Build CyberShake codebase on Cori
*Produce candidate site list for Bay Area CyberShake
*Review SI2 poster, add additional images if necessary
*Investigate improved load-balancing for DirectSynth SGT handlers
 
*Experiment with OMP parallelization for post-processing
== Blocked ==
*No progress on velocity smoothing, Titan down
 
== Follow-ups ==
*No
 
== 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