Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
*Blue Waters: | *Blue Waters: | ||
| − | ** | + | **Added support for data movement when SGT jobs complete |
| − | * | + | *Stampede: |
| − | ** | + | **Followed up with GRAM group - can't look at it until next week |
| − | * | + | **Wrote cron job to kill job-managers*Complete wiki entries for Blue Waters and Stampede validation |
| − | * | + | *Emailed Phil forward seismogram overlays |
| − | + | *Emailed David path to PSA code with example | |
| − | * | ||
== Today == | == Today == | ||
*Blue Waters: | *Blue Waters: | ||
| − | + | **Test RunManager integration, data movement, qsub dependencies | |
| − | **Test RunManager integration | ||
*Stampede: | *Stampede: | ||
| − | + | **Post-process 4 sets of WNGC SGTs (test support for multiple runs with same site, cron job) | |
| − | + | *Email forward seismogram overlays to the CyberShake group | |
| − | **Post-process 4 sets of WNGC SGTs | ||
| − | *Email | ||
| − | |||
| − | |||
| − | |||
== Blocked == | == Blocked == | ||
| Line 26: | Line 19: | ||
== Follow-ups == | == Follow-ups == | ||
| − | * | + | *CyberShake calls |
| + | |||
| + | Email ISI to ask about gathering metrics from Study 2.2 | ||
Think about readiness review | Think about readiness review | ||
Think about access to CyberShake data | Think about access to CyberShake data | ||
Revision as of 21:23, 13 March 2013
Yesterday
- Blue Waters:
- Added support for data movement when SGT jobs complete
- Stampede:
- Followed up with GRAM group - can't look at it until next week
- Wrote cron job to kill job-managers*Complete wiki entries for Blue Waters and Stampede validation
- Emailed Phil forward seismogram overlays
- Emailed David path to PSA code with example
Today
- Blue Waters:
- Test RunManager integration, data movement, qsub dependencies
- Stampede:
- Post-process 4 sets of WNGC SGTs (test support for multiple runs with same site, cron job)
- Email forward seismogram overlays to the CyberShake group
Blocked
- No
Follow-ups
- CyberShake calls
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
