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 == | ||
*Blue Waters: | *Blue Waters: | ||
** | **Looks like occasional I/O ops are very slow in seis_psa | ||
*Ran curve sensitivity code | |||
* | |||
*Continued scec-02 -> scec-04 data copy | *Continued scec-02 -> scec-04 data copy | ||
== Today == | == Today == | ||
*Blue Waters: | *Blue Waters: | ||
**Get | **Get metrics from production SGTs | ||
*Stampede: | *Stampede: | ||
** | **Submit failed PP runs | ||
* | *Check in on Broadband runs on epicenter | ||
*Continue scec-02 -> scec-04 data copy | *Continue scec-02 -> scec-04 data copy | ||
* | *Analyze curve sensitivity results | ||
== Blocked == | == Blocked == | ||
| Line 22: | Line 18: | ||
== Follow-ups == | == Follow-ups == | ||
* | *Blue Waters | ||
Revision as of 17:09, 20 May 2013
Yesterday
- Blue Waters:
- Looks like occasional I/O ops are very slow in seis_psa
- Ran curve sensitivity code
- Continued scec-02 -> scec-04 data copy
Today
- 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
Blocked
- No
Follow-ups
- Blue Waters
Finish wiki entries for Stampede and Blue Waters validation
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration
