Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 11: | Line 11: | ||
*Blue Waters: | *Blue Waters: | ||
**Test data movement, monitor run | **Test data movement, monitor run | ||
| + | **Sort out some issues with the Run Manager changing job status to Error prematurely | ||
| + | **Set up SSH keys to add jobs to pending.txt on shock when SGT run finishes | ||
*Stampede: | *Stampede: | ||
**Post-process 3 sets of WNGC SGTs | **Post-process 3 sets of WNGC SGTs | ||
Revision as of 17:09, 14 March 2013
Yesterday
- Blue Waters:
- Tested RunManager integration, qsub dependencies, looks good, long queue times for SimSgt jobs
- Stampede:
- Started post-processing on first set of WNGC SGTs
- Reworked run scripts on shock and DAX generator to support post-processing the same site with multiple runs simultaneously
- Calculated peak amplitudes for Rob and emailed
- CyberShake calls
Today
- Blue Waters:
- Test data movement, monitor run
- Sort out some issues with the Run Manager changing job status to Error prematurely
- Set up SSH keys to add jobs to pending.txt on shock when SGT run finishes
- Stampede:
- Post-process 3 sets of WNGC SGTs
- Watch JM killer
Blocked
- No
Follow-ups
- SEISM call at 11
Email ISI to ask about gathering metrics from Study 2.2
Think about readiness review
Think about access to CyberShake data
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration
