Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(657 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Yesterday ==
+
== Current Items ==
−
*Blue Waters
+
*Modify CyberShake to work on RSQSim ruptures
−
**Got single output file GPU SGT code working
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
−
**Partitioned CVM-S mesh
+
*CyberShake training
−
**Generated X and Y component SGTs
+
*Update CyberShake study wiki pages to point to SQLite files
−
**Tested cronjob to capture number of running jobs and cores
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
−
*Added new SGT_Variation_ID to DB
 
−
*aftershock disk filled up, halted monitord population;  John will add more space today
 
−
*Response from Rob - cleared Study 13.4
 
−
*Applied for ORNL Titan access
 
  
−
== Today ==
+
== Project Backlog ==
−
*Blue Waters
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
−
**Continue working on coscheduling
+
*Produce candidate site list for Bay Area CyberShake
−
*Stampede
+
*Investigate improved load-balancing for DirectSynth SGT handlers
−
**Post-process SGT GPU results, evaluate resulting curve
+
*Experiment with OMP parallelization for post-processing
−
*Generate new data products for Rob to understand velocity differences
 
−
*Identify directories used in 2011-12 CyberShake runs and zip
 
−
*Email Rob, ask about high SBSM ground motions
 
−
 
 
−
== Blocked ==
 
−
*No
 
−
 
 
−
== Follow-ups ==
 
−
*GB call?
 
−
*Call with Omar (12-1)
 
−
 
 
−
Check on SA forward sim
 
−
Email Stampede staff, let them know about node crashing solution
 
−
Finish wiki entries for Stampede and Blue Waters validation
 
−
 
 
−
== 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