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
 
(708 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Blue Waters:
*Modify CyberShake to work on RSQSim ruptures
**Committed AWP helper scripts to SVN
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
**Continued testing AWP helper scripts - found and fixed bug in media code, rerunning AWP SGTs
*CyberShake training
**Worked on workflow generating scripts
*Update CyberShake study wiki pages to point to SQLite files
*Stampede:
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
**Run s351 PP with timing numbers to get performance comparison with Kraken - wow!
*Kraken:
**Selected a rupture for forward simulation - source 7, rupture 6
*Produced site list + KML for CS Study 2.3, uploaded to wiki
*UCERF3 meeting
*Replied re: Stampede space


== Today ==
== Project Backlog ==
*Blue Waters:
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Run post-AWP scripts when SGTs are complete
*Produce candidate site list for Bay Area CyberShake
**Continue work on workflow-generating scripts
*Investigate improved load-balancing for DirectSynth SGT handlers
*Stampede:
*Experiment with OMP parallelization for post-processing
**Install and test AWP helper scripts
**Test AWP SGT generation
**Continue testing PP
*Kraken:
**Validate AWP WNGC SGTs when omplete
**Configure forward RWG simulation
*Add AWP helper scripts to DAX generator
*Update Pegasus to get new output-dir
*Email cybershake list to notify about CS Study 2.3 site list
 
== Blocked ==
*No
 
== Follow-ups ==
*Phil re: Jessica and Jim Brune's request, helping out Nico
 
== 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"