Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
*Blue Waters: | *Blue Waters: | ||
| − | ** | + | **Monitor production runs |
| − | ** | + | **Worked on revised approach to just read points from rupture geometry file - progressed to testing |
| − | |||
| − | |||
| − | |||
| − | |||
== Today == | == Today == | ||
*Blue Waters: | *Blue Waters: | ||
**Monitor production runs | **Monitor production runs | ||
| − | ** | + | **Continue testing and getting performance numbers for revised extraction jobs |
| + | *Stampede: | ||
| + | **Continue work on offloading code | ||
== Blocked == | == Blocked == | ||
| − | * | + | *No |
== Follow-ups == | == Follow-ups == | ||
| − | * | + | *CyberShake calls |
| + | *Call with Bob and Nick | ||
Revision as of 17:11, 8 May 2013
Yesterday
- Blue Waters:
- Monitor production runs
- Worked on revised approach to just read points from rupture geometry file - progressed to testing
Today
- Blue Waters:
- Monitor production runs
- Continue testing and getting performance numbers for revised extraction jobs
- Stampede:
- Continue work on offloading code
Blocked
- No
Follow-ups
- CyberShake calls
- Call with Bob and Nick
Check on SA forward sim
Email Stampede staff, let them know about node crashing solution
Finish wiki entries for Stampede and Blue Waters validation
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration
