Difference between revisions of "CyberShake Study 15.4"

From SCECpedia
Jump to navigationJump to search
(Created page with '== Preparation for production runs == #Get DirectSynth working at full run scale, verify results #File ticket for 90-day purged space at Blue Waters #Follow up on high priority …')
 
Line 13: Line 13:
 
#<s>Evaluate topology-aware scheduling</s>
 
#<s>Evaluate topology-aware scheduling</s>
 
#Add restart capability to DirectSynth
 
#Add restart capability to DirectSynth
 +
#Add cleanup to workflow

Revision as of 21:28, 24 February 2015

Preparation for production runs

  1. Get DirectSynth working at full run scale, verify results
  2. File ticket for 90-day purged space at Blue Waters
  3. Follow up on high priority jobs at Titan
  4. Work out interface between Titan workflows and Blue Waters workflows
  5. File ticket for reservation at Blue Waters, along with justification
  6. Finish test of 1 Hz simulation with 2 Hz source
  7. Update DAX to support separate MD5 sums
  8. Add MD5 sum job to TC
  9. Check list of Mayssa's concerns
  10. Run test of 1 Hz SGT workflow on Blue Waters
  11. Evaluate topology-aware scheduling
  12. Add restart capability to DirectSynth
  13. Add cleanup to workflow
Retrieved from "https://strike.scec.org/scecwiki/index.php?title=CyberShake_Study_15.4&oldid=12034"