Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
Scottcal (talk | contribs)
No edit summary
Scottcal (talk | contribs)
No edit summary
 
(717 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Blue Waters:
*Modify CyberShake to work on RSQSim ruptures
**Worked on AWP-ODC-SGT helper scripts, found optimal core counts for pre-processing stages
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
**Ran RWG TEST V3.0.3 SGTs
*CyberShake training
*Stampede:
*Update CyberShake study wiki pages to point to SQLite files
**Finished configuring SGT workflow
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
**Helped debug Stampede GRAM install - looking good, but 6-minute lag time
*Performance review


== Today ==
== Project Backlog ==
*Blue Waters:
*Run CyberShake post-processing on RSQSim events, once DB is populated
**Finish testing AWP-ODC-SGT helper scripts, validate results
*Produce candidate site list for Bay Area CyberShake
**Run and validate RWG TEST V3.0.3 SGTs
*Investigate improved load-balancing for DirectSynth SGT handlers
*Stampede:
*Experiment with OMP parallelization for post-processing
**Try PP workflow
*Kraken:
**Validate RWG TEST V3.0.3 SGTs from BW
**Validate results from Stampede SGT workflow
**Select a rupture for forward simulation
*Come up with data and computational estimates for next set of production runs, targeting Blue Waters
*Find/update performance numbers for UCERF 3 with 1 Hz estimates for NICS meeting Tuesday
 
== Blocked ==
*No
 
== Follow-ups ==
*No
 
 
*Watch Morgan's AGU presentation
*Reply to TACC, NICS regarding authorized people
 
== 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