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 == | ||
*Continued | *Set up interface between Titan and Blue Waters workflows | ||
* | *Added cleanup to workflows | ||
* | *Continued tests of DirectSynth - finished job but with wrong parameters, so resubmitted | ||
*Monitor RotD insertions | |||
*Tried to debug issue where PMC invocations of seismogram code weren't working on BW | |||
== Today == | == Today == | ||
*Add restart capability to DirectSynth | *Add restart capability to DirectSynth | ||
*Monitor RotD insertions | *Monitor RotD insertions | ||
*Monitor DirectSynth job | |||
*Test interface | |||
*Open tickets with BW | |||
== Blocked == | == Blocked == | ||
| Line 15: | Line 17: | ||
== Follow-ups == | == Follow-ups == | ||
* | *CyberShake calls | ||
== Areas of Responsibilities == | == Areas of Responsibilities == | ||
Revision as of 18:00, 25 February 2015
Yesterday
- Set up interface between Titan and Blue Waters workflows
- Added cleanup to workflows
- Continued tests of DirectSynth - finished job but with wrong parameters, so resubmitted
- Monitor RotD insertions
- Tried to debug issue where PMC invocations of seismogram code weren't working on BW
Today
- Add restart capability to DirectSynth
- Monitor RotD insertions
- Monitor DirectSynth job
- Test interface
- Open tickets with BW
Blocked
- No
Follow-ups
- CyberShake calls
Areas of Responsibilities
- CyberShake
- Broadband CyberShake
- Code migration
