Staff Priorities - Scott: Difference between revisions
From SCECpedia
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
* | *Caught up on email | ||
* | *Started looking at failed CyberShake PP runs | ||
* | *May have fixed wireless card issues | ||
== Today == | == Today == | ||
* | *Continue work on failed CyberShake runs - loosen up allowed values, especially at high periods | ||
*Metrics from production runs | |||
* | *Resume scec-02 -> scec-04 copy | ||
* | |||
== Blocked == | == Blocked == | ||
| Line 14: | Line 13: | ||
== Follow-ups == | == Follow-ups == | ||
* | *No | ||
Finish wiki entries for Stampede and Blue Waters validation | Finish wiki entries for Stampede and Blue Waters validation | ||
Revision as of 17:18, 11 June 2013
Yesterday
- Caught up on email
- Started looking at failed CyberShake PP runs
- May have fixed wireless card issues
Today
- Continue work on failed CyberShake runs - loosen up allowed values, especially at high periods
- Metrics from production runs
- Resume scec-02 -> scec-04 copy
Blocked
- No
Follow-ups
- No
Finish wiki entries for Stampede and Blue Waters validation
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration
- Blue Waters:
- Get metrics from production SGTs
- Stampede:
- Submit failed PP runs
- Check in on Broadband runs on epicenter
- Continue scec-02 -> scec-04 data copy
- Analyze curve sensitivity results
