Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 7: | Line 7: | ||
*Added support for multiple runs with same site in RunManager | *Added support for multiple runs with same site in RunManager | ||
*Started wiki entries for Blue Waters and Stampede validation | *Started wiki entries for Blue Waters and Stampede validation | ||
| − | * | + | *Accepted request to review HPC Summer School applications |
| − | |||
| − | |||
== Today == | == Today == | ||
| Line 27: | Line 25: | ||
== Follow-ups == | == Follow-ups == | ||
*No | *No | ||
| + | |||
| + | Think about readiness review | ||
| + | Think about access to CyberShake data | ||
== Areas of Responsibilities == | == Areas of Responsibilities == | ||
Revision as of 17:06, 12 March 2013
Yesterday
- Blue Waters:
- Continued working through workflow creator - integrating with RunManager
- Kraken:
- Moved seismogram extraction to shock
- Extracted forward seismograms - after a few false starts, sent results to Rob for review
- Added support for multiple runs with same site in RunManager
- Started wiki entries for Blue Waters and Stampede validation
- Accepted request to review HPC Summer School applications
Today
- Blue Waters:
- Add support for data movement when SGT jobs complete
- Test RunManager integration and qsub dependencies
- Stampede:
- Follow-up with GRAM group re: hanging Perl script
- Kraken:
- Post-process 4 sets of WNGC SGTs and test support for multiple runs with same site
- Email ISI to ask about gathering metrics from Study 2.2
- Complete wiki entries for Blue Waters and Stampede validation
Blocked
- No
Follow-ups
- No
Think about readiness review Think about access to CyberShake data
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration
