Difference between revisions of "Product Backlog - Scott"

From SCECpedia
Jump to navigationJump to search
 
(39 intermediate revisions by 2 users not shown)
Line 2: Line 2:
  
 
== Project/Product Backlog ==
 
== Project/Product Backlog ==
*Re-insert data into focal database after upgrade
+
*Add Vs30 insertion to CyberShake workflow + ERF 48
 
*Extract SQLite db for Study 17.3
 
*Extract SQLite db for Study 17.3
 +
*Point Xiaofeng to data used in paper
 +
*Help Rob troubleshoot mesh creation
 +
*Extract velocity values; see if they match Mei's
 +
*Prepare RSQSim ERF 48 for CyberShake curves
 +
*Generate CyberShake curves using new ERF
 +
*Try to check out and build Mei's UCVM dev branch
 +
*Use branch to recreate Central CA mesh
 +
*Modify workflow to use Scott's X509 Stampede2 certificate (rather than tera3d's)
 +
*Work on CSSI proposal
 +
*Update Pegasus and Condor on shock
 
*Integrate Harvard basin model into NorCal velocity model, resolving any outstanding issues with Science groups.
 
*Integrate Harvard basin model into NorCal velocity model, resolving any outstanding issues with Science groups.
 
*Train Kevin/Phil as alternative CyberShake operators
 
*Train Kevin/Phil as alternative CyberShake operators
*Generate hazard curve using RSQSim ruptures
 
 
*Investigate improved load-balancing for DirectSynth SGT handlers
 
*Investigate improved load-balancing for DirectSynth SGT handlers
 
*Experiment with OMP parallelization for post-processing
 
*Experiment with OMP parallelization for post-processing
 
*Modify CyberShake workflows to use Globus Online for file transfer
 
*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
 
*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 if inconsistent grid point spacing is a result of insufficient precision, or of mixing projections
 
*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.
 +
*Perform forward simulation(s) across model interface to look for reflection/refraction effects.
  
 
== Recently Finished Items ==
 
== 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]]

Latest revision as of 22:13, 8 May 2018

Scott Callaghan's Project/Product Backlog

Project/Product Backlog

  • Add Vs30 insertion to CyberShake workflow + ERF 48
  • Extract SQLite db for Study 17.3
  • Point Xiaofeng to data used in paper
  • Help Rob troubleshoot mesh creation
  • Extract velocity values; see if they match Mei's
  • Prepare RSQSim ERF 48 for CyberShake curves
  • Generate CyberShake curves using new ERF
  • Try to check out and build Mei's UCVM dev branch
  • Use branch to recreate Central CA mesh
  • Modify workflow to use Scott's X509 Stampede2 certificate (rather than tera3d's)
  • Work on CSSI proposal
  • Update Pegasus and Condor on shock
  • Integrate Harvard basin model into NorCal velocity model, resolving any outstanding issues with Science groups.
  • Train Kevin/Phil as alternative CyberShake operators
  • 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 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.
  • Perform forward simulation(s) across model interface to look for reflection/refraction effects.

Recently Finished Items

Related Entries