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
 
(105 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Ran mysql2sqlite convert script on data needed for Study 1.0 insertion; no errors
*Modify CyberShake to work on RSQSim ruptures
*Copied over condor config to new Condor version
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Verified Condor install is working with both Blue Waters and Titan
*CyberShake training
*Waiting on non-study peak amps query to finish on focal to verify reload on moment
*Update CyberShake study wiki pages to point to SQLite files
*Submitted command to add new index to production peak amps table; failed with temp table error
*Create wiki page for CyberShake RSQSim, and upload sample seismograms


== Today ==
== Project Backlog ==
*Insert old studies into sqlite DBs
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Change mysql tmpdir to larger disk, try again
*Produce candidate site list for Bay Area CyberShake
*Attempt test hazard curve at OSI with 1D model
*Investigate improved load-balancing for DirectSynth SGT handlers
*Construct sample volumes for sites at corners of Central CA box to get volume dimensions for Yifeng
*Experiment with OMP parallelization for post-processing
*Investigate which Study 16.8 sites include northern CA SAF events
*Verify non-study peak amps successfully reloaded
 
== Blocked ==
*No
 
== Follow-ups ==
*No
 
== Areas of Responsibilities ==
* CyberShake
* 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