Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(672 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Yesterday ==
+
== Current Items ==
−
*Blue Waters:
+
*Modify CyberShake to work on RSQSim ruptures
−
**Debugged issue with Python job - infinite loop
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
−
**Found some bugs in job specifications
+
*CyberShake training
−
*Stampede:
+
*Update CyberShake study wiki pages to point to SQLite files
−
**Crashing node problem - turns out there are nonsense characters from PMC runs - started on 2/26
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
−
*John installed newer verion of GUC on shock
 
−
*Got info from Andrew Hart about OODT
 
−
*Finished evaluating applicants for Summer School
 
  
−
== Today ==
+
== Project Backlog ==
−
*Blue Waters:
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
−
**Transfer PAS files to Stampede testing with new version of GUC on shock (to use different certs)
+
*Produce candidate site list for Bay Area CyberShake
−
*Stampede:
+
*Investigate improved load-balancing for DirectSynth SGT handlers
−
**GRAM staff starting to look at JM issues - support
+
*Experiment with OMP parallelization for post-processing
−
**Recompile and relink PMC, see if that fixes problem
 
−
*Start forward simulations for a San Andreas and mountain events
 
−
 
 
−
== Blocked ==
 
−
*No
 
−
 
 
−
== Follow-ups ==
 
−
*No
 
−
 
 
−
Finish wiki entries for Stampede and Blue Waters validation
 
−
Think about readiness review
 
−
Think about access to CyberShake data
 
−
 
 
−
== 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