Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 16: | Line 16: | ||
**Post-process 3 sets of WNGC SGTs | **Post-process 3 sets of WNGC SGTs | ||
**Watch JM killer | **Watch JM killer | ||
| + | *Create wiki entry for Study 2.2 data products (with links to maps, curves, Feng's analysis, seismograms) | ||
| + | *Start DB population | ||
== Blocked == | == Blocked == | ||
| Line 23: | Line 25: | ||
*SEISM call at 11 | *SEISM call at 11 | ||
| − | + | Finish wiki entries for Stampede and Blue Waters validation | |
| − | |||
Think about readiness review | Think about readiness review | ||
Think about access to CyberShake data | Think about access to CyberShake data | ||
Revision as of 21:11, 14 March 2013
Yesterday
- Blue Waters:
- Tested RunManager integration, qsub dependencies, looks good, long queue times for SimSgt jobs
- Stampede:
- Started post-processing on first set of WNGC SGTs
- Reworked run scripts on shock and DAX generator to support post-processing the same site with multiple runs simultaneously
- Calculated peak amplitudes for Rob and emailed
- CyberShake calls
Today
- Blue Waters:
- Test data movement, monitor run
- 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
- Watch JM killer
- Create wiki entry for Study 2.2 data products (with links to maps, curves, Feng's analysis, seismograms)
- Start DB population
Blocked
- No
Follow-ups
- SEISM call at 11
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
