Difference between revisions of "Product Backlog - Scott"

From SCECpedia
Jump to navigationJump to search
Line 5: Line 5:
 
*Integrate Harvard basin model into NorCal velocity model, revolving any outstanding issues with Science groups.
 
*Integrate Harvard basin model into NorCal velocity model, revolving any outstanding issues with Science groups.
 
*Train Kevin/Phil as alternative CyberShake operators
 
*Train Kevin/Phil as alternative CyberShake operators
*Modify CyberShake to work on RSQSim ruptures
 
 
*Generate hazard curve using RSQSim ruptures
 
*Generate hazard curve using RSQSim ruptures
 
*Investigate improved load-balancing for DirectSynth SGT handlers
 
*Investigate improved load-balancing for DirectSynth SGT handlers
Line 16: Line 15:
 
*Investigate visualizing velocity meshes in paraview
 
*Investigate visualizing velocity meshes in paraview
 
*Reduce the runtime of the smoothing code.
 
*Reduce the runtime of the smoothing code.
 +
 +
== Recently Finished Items ==
 +
*Modify CyberShake to work on RSQSim ruptures (2/16/18)
  
 
== Related Entries ==
 
== Related Entries ==
 
*[[CME Software Staff]]
 
*[[CME Software Staff]]
 
*[[CME Project]]
 
*[[CME Project]]

Revision as of 21:57, 16 February 2018

Scott Callaghan's Project/Product Backlog

Project/Product Backlog

  • Re-insert data into focal database after upgrade
  • Integrate Harvard basin model into NorCal velocity model, revolving any outstanding issues with Science groups.
  • Train Kevin/Phil as alternative CyberShake operators
  • Generate hazard curve using RSQSim ruptures
  • Investigate improved load-balancing for DirectSynth SGT handlers
  • Experiment with OMP parallelization for post-processing
  • Modify CyberShake workflows to use Globus Online for file transfer
  • Create cross-sections from mesh generated with 1) USGS Bay Area; 2) CVM-S4.26.M01; 3) CCA-06; 4) 1D background; with 10 km smoothing
  • Spec Bay Area run with Vs min of 500 m/s and box extended to Cloverdale
  • Create hazard curves for overlapping sites using modified velocity model order
  • Investigate if inconsistent grid point spacing is a result of insufficient precision, or of mixing projections
  • Investigate visualizing velocity meshes in paraview
  • Reduce the runtime of the smoothing code.

Recently Finished Items

  • Modify CyberShake to work on RSQSim ruptures (2/16/18)

Related Entries