Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
← Older edit
Scottcal (talk | contribs)
8,097 edits
No edit summary
Scottcal (talk | contribs)
8,097 edits
No edit summary
 
(683 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Blue Waters:
*Modify CyberShake to work on RSQSim ruptures
**Tested RunManager integration, qsub dependencies, looks good, long queue times for SimSgt jobs
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Stampede:
*CyberShake training
**Started post-processing on first set of WNGC SGTs
*Update CyberShake study wiki pages to point to SQLite files
*Reworked run scripts on shock and DAX generator to support post-processing the same site with multiple runs simultaneously
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
*Calculated peak amplitudes for Rob and emailed
*CyberShake calls


== Today ==
== Project Backlog ==
*Blue Waters:
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Test data movement, monitor run
*Produce candidate site list for Bay Area CyberShake
**Sort out some issues with the Run Manager changing job status to Error prematurely
*Investigate improved load-balancing for DirectSynth SGT handlers
**Set up SSH keys to add jobs to pending.txt on shock when SGT run finishes
*Experiment with OMP parallelization for post-processing
*Stampede:
**Post-process 3 sets of WNGC SGTs
**Watch JM killer
*Create wiki entry for Study 2.2 data products (with links to maps, curves, Feng's analysis, seismograms)
*Start DB population
 
== Blocked ==
*No
 
== Follow-ups ==
*SEISM call at 11
 
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
Retrieved from "https://strike.scec.org/index.php?title=Staff_Priorities_-_Scott&oldid=19663"