Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 16: | Line 16: | ||
**Set up with AWP | **Set up with AWP | ||
*Kraken: | *Kraken: | ||
| + | **Investigate OOM failures with new workflows | ||
**Error on PP with Blue Waters AWP WNGC SGTs; investigate | **Error on PP with Blue Waters AWP WNGC SGTs; investigate | ||
*Update Pegasus to get new output-dir | *Update Pegasus to get new output-dir | ||
| Line 21: | Line 22: | ||
*Add AWP helper scripts to DAX generator | *Add AWP helper scripts to DAX generator | ||
*Email cybershake list to notify about CS Study 2.3 site list | *Email cybershake list to notify about CS Study 2.3 site list | ||
| + | |||
== Blocked == | == Blocked == | ||
*No | *No | ||
Revision as of 18:18, 25 February 2013
Yesterday
- Blue Waters:
- Ran post-AWP scripts
- Finished defining workflow-generating scripts
- Stampede:
- Continued testing PP with different combinations of widths and number of DAXes
- Kraken:
- Submitted WNGC AWP SGTs from BW
- Configure forward RWG simulation
Today
- Blue Waters:
- Test workflow-generating scripts
- Stampede:
- Continue testing PP configurations
- Set up with AWP
- Kraken:
- Investigate OOM failures with new workflows
- Error on PP with Blue Waters AWP WNGC SGTs; investigate
- Update Pegasus to get new output-dir
- Prepare and travel for Blue Waters workshop
- Add AWP helper scripts to DAX generator
- Email cybershake list to notify about CS Study 2.3 site list
Blocked
- No
Follow-ups
- Nico at 11
- Jessica at 12
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration
