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
 
(479 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yesterday ==
== Current Items ==
*Worked on 200m TEST hazard curve (until file systems went down)
*Modify CyberShake to work on RSQSim ruptures
*Outlined plan for reducing temporary data for 1 Hz
**Modify PreSGT step to determine list of points to save SGTs for from RSQSim rupture files
*Emailed Gideon about locality preferences
*CyberShake training
*Revised DAX generator to group output by source
*Update CyberShake study wiki pages to point to SQLite files
*Create wiki page for CyberShake RSQSim, and upload sample seismograms


== Today ==
== Project Backlog ==
*Start implementing plan to reduce temp data
*Run CyberShake post-processing on RSQSim events, once DB is populated
*Respond to Gideon
*Produce candidate site list for Bay Area CyberShake
*Work on draft abstract for extreme scaling workshop
*Investigate improved load-balancing for DirectSynth SGT handlers
*Catch up on signals course
*Experiment with OMP parallelization for post-processing
*Find nearest CyberShake locations to Nico's points
 
== Blocked ==
*200m TEST curve, tests of group-output-by-source until file systems return
 
== Follow-ups ==
*Summer school call
*HighF call
*CyberShake calls
 
 
*Try out SeedMe so I can respond to Amit
*Start drafting abstract for extreme scaling
 
 
 
== 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