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
 
(311 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Monitored RotD insertions
*Modify CyberShake to work on RSQSim ruptures
*DirectSynth job completed, calculated comparison curves, emailed out
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Modified workflow to support having md5sums no longer in the critical path
*CyberShake training
*CyberShake calls
*Update CyberShake study wiki pages to point to SQLite files
*Added 3rd type of SGT pilot job to Titan
*Create wiki page for CyberShake RSQSim, and upload sample seismograms


== Today ==
== Project Backlog ==
*Add restart capability to DirectSynth
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Monitor 2 Hz source job
*Produce candidate site list for Bay Area CyberShake
*Queue up SBSM 1 Hz run on Titan to test pilot jobs, BW interface
*Investigate improved load-balancing for DirectSynth SGT handlers
 
*Experiment with OMP parallelization for post-processing
== Blocked ==
*No
 
== 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