Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(850 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Started process of activating yubikey
+
*Modify CyberShake to work on RSQSim ruptures
*Worked on workflow talk for next week
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*IOprof run finished, looked at results - discovered I had no baseline for s351, submitted s512
+
*CyberShake training
*Stage out of all files results look good
+
*Update CyberShake study wiki pages to point to SQLite files
*CyberShake calls
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
  
== Today ==
+
== Project Backlog ==
*Look up mentees
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Parse s512 iprof results
+
*Produce candidate site list for Bay Area CyberShake
*Add step to delete individual files, archive zip files
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Submit runs to test optimization levels with RWG SGT code
+
*Experiment with OMP parallelization for post-processing
*Create new submission script to work with integrated DAX generator
 
*Test integrated DAX generator
 
 
 
== Blocked ==
 
*No
 
 
 
== Follow-ups ==
 
*No
 
 
 
 
 
*Sign up for Blue Waters acct
 
*Compare En-Jui's SGT results to AWP
 
 
 
 
 
== Areas of Responsibilities ==
 
* CyberShake 1.4
 
* Broadband CyberShake
 
* Code migration
 
 
 
*Create bio, work summary, abstract for EU-US summer school
 

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