Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
 
(673 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
+
== Current Items ==
*Blue Waters:
+
*Modify CyberShake to work on RSQSim ruptures
**Python job seems to start but nothing happens
+
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
**Contacted BW staff, worked with them to ID problem
+
*CyberShake training
*Stampede:
+
*Update CyberShake study wiki pages to point to SQLite files
**Errors in WNGC jobs
+
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
**Path error manifested as held job
 
*Finished wiki entry for Study 2.2 data products
 
*Worked on evaluating applicants for Summer School
 
*Responded to David on monitord script
 
  
== Today ==
+
== Project Backlog ==
*Blue Waters:
+
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Debug issue with Python job
+
*Produce candidate site list for Bay Area CyberShake
**Transfer PAS files to Stampede once guc is upgraded on shock (to use different certs)
+
*Investigate improved load-balancing for DirectSynth SGT handlers
*Stampede:
+
*Experiment with OMP parallelization for post-processing
**Resolve issues in WNGC jobs
 
**Start up PAS workflows
 
**Crashing node problem
 
**Support debugging job-manager issues if GRAM staff is available
 
*Contact Andrew Hart for overview of OODT
 
*Start forward simulations for a San Andreas and mountain events
 
*Finish evaluating applicants for Summer School
 
 
 
== 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