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
 
(307 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*HighF call
*Modify CyberShake to work on RSQSim ruptures
*Queued up RotD insert
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Tested/debugged restart capability in DirectSynth
*CyberShake training
*Monitored 2 Hz source run
*Update CyberShake study wiki pages to point to SQLite files
*Opened ticket with BW regarding exec issue
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Added DirectSynth to workflow tools


== Today ==
== Project Backlog ==
*Monitor 2 Hz source run - should finish today
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Work on Study 15.3 wiki entry
*Produce candidate site list for Bay Area CyberShake
*Verify results calculated using DirectSynth with restart
*Investigate improved load-balancing for DirectSynth SGT handlers
*Respond to Mayssa
*Experiment with OMP parallelization for post-processing
 
== Blocked ==
*No
 
== Follow-ups ==
*CyberShake calls
 
== 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