Staff Priorities - Scott: Difference between revisions
From SCECpedia
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
*Blue Waters: | *Blue Waters: | ||
**Continued monitoring production runs | **Continued monitoring production runs | ||
** | **Ran tests with Efecan's suggested striping - faster for extraction, not for seis | ||
* | **Submitted test with memcached back on | ||
* | *Automated movement of scec-02 files to scec-04 | ||
* | *Modified curve calculation to ignore certain ruptures | ||
* | |||
== Today == | == Today == | ||
*Blue Waters: | *Blue Waters: | ||
**Continue monitoring production runs | **Continue monitoring production runs | ||
** | **Look at seis_psa results with memcached - if still slow, add timings | ||
* | *Monitor data movement from scec-02 to scec-04 | ||
* | *Monitor monitord DB insertion | ||
*Northridge down | |||
== Blocked == | == Blocked == | ||
* | *No | ||
== Follow-ups == | == Follow-ups == | ||
* | *CyberShake calls | ||
Revision as of 17:07, 15 May 2013
Yesterday
- Blue Waters:
- Continued monitoring production runs
- Ran tests with Efecan's suggested striping - faster for extraction, not for seis
- Submitted test with memcached back on
- Automated movement of scec-02 files to scec-04
- Modified curve calculation to ignore certain ruptures
Today
- Blue Waters:
- Continue monitoring production runs
- Look at seis_psa results with memcached - if still slow, add timings
- Monitor data movement from scec-02 to scec-04
- Monitor monitord DB insertion
- Northridge down
Blocked
- No
Follow-ups
- CyberShake calls
Finish wiki entries for Stampede and Blue Waters validation
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration