Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(691 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Yesterday ==
+
== Current Items ==
−
*Blue Waters:
+
*Modify CyberShake to work on RSQSim ruptures
−
**Continued working through workflow creator
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
−
*Stampede:
+
*CyberShake training
−
**Ran using jobmanager-slurm, still found issue, think I put incorrect hypothesis to rest for good
+
*Update CyberShake study wiki pages to point to SQLite files
−
*Kraken:
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
−
**Added rotation to seismogram extraction, compared, found issue, Rob set me straight
 
−
*Emailed CyberShake list to announce Study 2.2 completion
 
  
−
== Today ==
+
== Project Backlog ==
−
*Blue Waters:
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
−
**Continue working through workflow creator
+
*Produce candidate site list for Bay Area CyberShake
−
*Stampede:
+
*Investigate improved load-balancing for DirectSynth SGT handlers
−
**Support GRAM staff investigation of Perl script hanging
+
*Experiment with OMP parallelization for post-processing
−
*Kraken:
 
−
**Filesystem is very slow - try to redo seismogram extraction, perhaps move to shock
 
−
*Add support for multiple runs with same site in RunManager
 
−
*Email ISI to ask about gathering metrics from Study 2.2
 
−
*Wiki entries for Blue Waters and Stampede validation
 
−
*Think about readiness review
 
−
*Think about access to CyberShake data
 
−
 
 
−
== 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