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
 
(396 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Modified RotD100 code
*Modify CyberShake to work on RSQSim ruptures
*Investigated seg faults with Gideon - might be out of memory, testing with more memory for system processes
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Found and fixed error in rupture generation code on Titan, retested, new error
*CyberShake training
*Update CyberShake study wiki pages to point to SQLite files
*Create wiki page for CyberShake RSQSim, and upload sample seismograms


== Today ==
== Project Backlog ==
*Continue modifying RotD100 code
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Fix and retry Titan workflow
*Produce candidate site list for Bay Area CyberShake
*Monitor increased memory test
*Investigate improved load-balancing for DirectSynth SGT handlers
 
*Experiment with OMP parallelization for post-processing
== Blocked ==
*No
 
== Follow-ups ==
*HighF, 11-11:30
*CyberShake, 11:30-12:30
*BBP Paper, 1:30-2
 
== 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