Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to searchLine 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
*Blue Waters: | *Blue Waters: | ||
− | ** | + | **Monitored run |
*Stampede: | *Stampede: | ||
− | ** | + | **Found issue with the JM killer |
− | |||
− | |||
− | |||
== Today == | == Today == | ||
− | *Blue Waters | + | *Blue Waters |
− | **Test data movement | + | **Test data movement |
**Sort out some issues with the Run Manager changing job status to Error prematurely | **Sort out some issues with the Run Manager changing job status to Error prematurely | ||
**Set up SSH keys to add jobs to pending.txt on shock when SGT run finishes | **Set up SSH keys to add jobs to pending.txt on shock when SGT run finishes | ||
− | *Stampede | + | *Stampede |
**Post-process 3 sets of WNGC SGTs | **Post-process 3 sets of WNGC SGTs | ||
− | * | + | *Start monitord DB population |
*Create wiki entry for Study 2.2 data products (with links to maps, curves, Feng's analysis, seismograms) | *Create wiki entry for Study 2.2 data products (with links to maps, curves, Feng's analysis, seismograms) | ||
− | |||
== Blocked == | == Blocked == | ||
Line 23: | Line 19: | ||
== 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:00, 18 March 2013
Yesterday
- Blue Waters:
- Monitored run
- Stampede:
- Found issue with the JM killer
Today
- Blue Waters
- Test data movement
- Sort out some issues with the Run Manager changing job status to Error prematurely
- Set up SSH keys to add jobs to pending.txt on shock when SGT run finishes
- Stampede
- Post-process 3 sets of WNGC SGTs
- Start monitord DB population
- Create wiki entry for Study 2.2 data products (with links to maps, curves, Feng's analysis, seismograms)
Blocked
- No
Follow-ups
- No
Finish wiki entries for Stampede and Blue Waters validation Think about readiness review Think about access to CyberShake data
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration