Difference between revisions of "Product Backlog - Scott"
From SCECpedia
Jump to navigationJump to searchLine 2: | Line 2: | ||
== Project/Product Backlog == | == Project/Product Backlog == | ||
+ | *Modify workflow to use Scott's X509 Stampede2 certificate (rather than tera3d's) | ||
*Reply to Rob on projections | *Reply to Rob on projections | ||
*Point Phil to KML with velocity model regions | *Point Phil to KML with velocity model regions |
Revision as of 18:10, 2 April 2018
Scott Callaghan's Project/Product Backlog
Project/Product Backlog
- Modify workflow to use Scott's X509 Stampede2 certificate (rather than tera3d's)
- Reply to Rob on projections
- Point Phil to KML with velocity model regions
- Construct Vs/rho document for use in converting SRF
- Provide test to verify UCVM name-collision fix
- Send Karan writeup for use in Pegasus NSF report
- Add CyberShake sections to CSSI proposal
- Generate hazard curve using RSQSim ruptures
- Update Pegasus and Condor on shock
- Extract SQLite db for Study 17.3
- 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.