Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 2: | Line 2: | ||
*Tested workflows on Stampede - PP passes, still working on Integrated | *Tested workflows on Stampede - PP passes, still working on Integrated | ||
*Discovered we need to populate RuptureVariations table in DB for ERF 36 | *Discovered we need to populate RuptureVariations table in DB for ERF 36 | ||
| − | *CyberShake calls | + | *CyberShake calls - move to AWP-SGT-GPU on Blue Waters |
*Follow-up with Phil | *Follow-up with Phil | ||
*Worked on UCVM improvements for 1 Hz | *Worked on UCVM improvements for 1 Hz | ||
| Line 9: | Line 9: | ||
*Respond to Marine | *Respond to Marine | ||
*Continue testing integrated workflow | *Continue testing integrated workflow | ||
| − | * | + | *Insert RuptureVariation entries for ERF 36 |
*Run pegasus-statistics on Study 2.2 results | *Run pegasus-statistics on Study 2.2 results | ||
| + | |||
== Blocked == | == Blocked == | ||
Revision as of 17:28, 15 August 2013
Yesterday
- Tested workflows on Stampede - PP passes, still working on Integrated
- Discovered we need to populate RuptureVariations table in DB for ERF 36
- CyberShake calls - move to AWP-SGT-GPU on Blue Waters
- Follow-up with Phil
- Worked on UCVM improvements for 1 Hz
Today
- Respond to Marine
- Continue testing integrated workflow
- Insert RuptureVariation entries for ERF 36
- Run pegasus-statistics on Study 2.2 results
Blocked
- No
Follow-ups
- No
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration
