Difference between revisions of "CyberShake Study 15.4"

From SCECpedia
Jump to navigationJump to search
Line 3: Line 3:
 
== Preparation for production runs ==
 
== Preparation for production runs ==
  
#<s>Get DirectSynth working at full run scale, verify results</s>
+
#<s>Check list of Mayssa's concerns</s>
#File ticket for 90-day purged space at Blue Waters
 
#Follow up on high priority jobs at Titan
 
#Work out interface between Titan workflows and Blue Waters workflows
 
#File ticket for reservation at Blue Waters, along with justification
 
#Finish test of 1 Hz simulation with 2 Hz source
 
 
#<s>Update DAX to support separate MD5 sums</s>
 
#<s>Update DAX to support separate MD5 sums</s>
 
#<s>Add MD5 sum job to TC</s>
 
#<s>Add MD5 sum job to TC</s>
#<s>Check list of Mayssa's concerns</s>
 
#Run test of full 1 Hz SGT workflow on Blue Waters
 
 
#<s>Evaluate topology-aware scheduling</s>
 
#<s>Evaluate topology-aware scheduling</s>
#Add restart capability to DirectSynth
+
#<s>Get DirectSynth working at full run scale, verify results</s>
#Add cleanup to workflow
+
#<s>Modify workflow to have md5sums be in parallel</s>
#Simulate curves for 3 sites with final configuration; compare curves and seismograms
+
#Test of 1 Hz simulation with 2 Hz source - 2/27
#Look at how to create study description file
+
#Add a third pilot job type to Titan pilots - 2/27
#Modify workflow to have md5sums be in parallel
+
#Create study description file for Run Manager - 2/27
#Add a third pilot job type to Titan pilots
+
#Run test of full 1 Hz SGT workflow on Blue Waters - 3/4
#Science readiness review
+
#Add cleanup to workflow and test - 3/4
#Technical readiness review
+
#Test interface between Titan workflows and Blue Waters workflows - 3/4
 +
#Add restart capability to DirectSynth - 3/6
 +
#Simulate curves for 3 sites with final configuration; compare curves and seismograms - 3/11
 +
#File ticket for 90-day purged space at Blue Waters - 3/13
 +
#File ticket for reservation at Blue Waters, along with justification - 3/13
 +
#Follow up on high priority jobs at Titan - 3/13
 +
#Science readiness review - 3/18
 +
#Technical readiness review - 3/18
 +
 
  
 
== Computational Status ==
 
== Computational Status ==

Revision as of 16:38, 26 February 2015

CyberShake Study 15.3 is a computational study to calculate one physics-based probabilistic seismic hazard model for Southern California at 1 Hz, using CVM-S4.26, the GPU implementation of AWP-ODC-SGT, the Graves and Pitarka (2015) rupture variations with uniform hypocenters, and the UCERF2 ERF. The SGT calculations will be split between NCSA Blue Waters and OLCF Titan, and the post-processing will be done entirely on Blue Waters. The goal is to calculate the standard Southern California site list (286 sites) used in previous CyberShake studies so we can produce comparison curves and maps, and data products for the UGMS Committee.

Preparation for production runs

  1. Check list of Mayssa's concerns
  2. Update DAX to support separate MD5 sums
  3. Add MD5 sum job to TC
  4. Evaluate topology-aware scheduling
  5. Get DirectSynth working at full run scale, verify results
  6. Modify workflow to have md5sums be in parallel
  7. Test of 1 Hz simulation with 2 Hz source - 2/27
  8. Add a third pilot job type to Titan pilots - 2/27
  9. Create study description file for Run Manager - 2/27
  10. Run test of full 1 Hz SGT workflow on Blue Waters - 3/4
  11. Add cleanup to workflow and test - 3/4
  12. Test interface between Titan workflows and Blue Waters workflows - 3/4
  13. Add restart capability to DirectSynth - 3/6
  14. Simulate curves for 3 sites with final configuration; compare curves and seismograms - 3/11
  15. File ticket for 90-day purged space at Blue Waters - 3/13
  16. File ticket for reservation at Blue Waters, along with justification - 3/13
  17. Follow up on high priority jobs at Titan - 3/13
  18. Science readiness review - 3/18
  19. Technical readiness review - 3/18


Computational Status

We are hoping to begin this study in early March.

Data Products

Goals

Verification

DirectSynth

A comparison of 1 Hz results with SeisPSA to results with DirectSynth for WNGC. SeisPSA results are in magenta, DirectSynth results are in black. They're so close it's difficult to make out the magenta.

2s 3s 5s 10s
WNGC SeisPSA v DirectSynth 2s.png
WNGC SeisPSA v DirectSynth 3s.png
WNGC SeisPSA v DirectSynth 5s.png
WNGC SeisPSA v DirectSynth 10s.png

2 Hz source

Blue Waters vs Titan for SGT calculation

Sites

Performance Enhancements (over Study 14.3)

Responses to Study 14.2 Lessons Learned

SGT codes

PP codes

Workflow management

Codes

Lessons Learned

Computational and Data Estimates

Performance Metrics

Presentations and Papers