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
 
(670 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Stampede:
*Modify CyberShake to work on RSQSim ruptures
**Sent logs to Joe to help debug JM issues
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
**Various tests to debug bad I/O problem - issue with pipe forwarding, working on minimal test case
*CyberShake training
**Got blocked and reenabled in queue
*Update CyberShake study wiki pages to point to SQLite files
*Kraken:
*Create wiki page for CyberShake RSQSim, and upload sample seismograms
**Got codes and input files together for NICS to do CyberShake PP benchmarking on test system
*Tested new version of GUC on shock - still not doing what I want, so changed default scottcal group on Stampede
== Today ==
*Blue Waters:
**Transfer PAS files to Stampede
*Stampede:
**Continue debugging bad I/O problem
**Continue supporting Joe's work on JM
*Kraken:
**Create scripts and reference solutions for NICS
**Start forward simulations for a San Andreas and mountain events
*Respond to Sanaz about GMPEs in DB
*Evaluate more HPC Summer School applicants


== Blocked ==
== Project Backlog ==
*No
*Run CyberShake post-processing on RSQSim events, once DB is populated
 
*Produce candidate site list for Bay Area CyberShake
== Follow-ups ==
*Investigate improved load-balancing for DirectSynth SGT handlers
*CyberShake calls
*Experiment with OMP parallelization for post-processing
 
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"