Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(550 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Resolved BW remote job issues - they closed the ports
+
*Modify CyberShake to work on RSQSim ruptures
*Updated DAX generator to use single UCVM executable
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Submitted hazard curve with Pegasus RC and single UCVM executable on Stampede
+
*CyberShake training
*Resubmitted hazard curve on BW with CVM-SI26
+
*Update CyberShake study wiki pages to point to SQLite files
 +
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Rerun hazard curves with 1000m SGTs, 200m surfaces on BW
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Run hazard curve using SeisPSA_large_mem on Stampede
+
*Produce candidate site list for Bay Area CyberShake
*Rerun hazard curve for TEST site with CVM-SI26 on BW, delete old curve
+
*Investigate improved load-balancing for DirectSynth SGT handlers
 
+
*Experiment with OMP parallelization for post-processing
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*No
 
 
 
== Areas of Responsibilities ==
 
* CyberShake 1.4
 
* 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