Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to searchLine 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
− | * | + | *Extracted v3 vs v3.0.3 seismograms at 218/267/11 rupture, sent to Rob |
− | * | + | *Responded to Manuela (post-doc with Norm) about right Run IDs to use with CyberShake data |
− | * | + | *Compared v3.0.3 TEST runs from HPC and Kraken, good match |
− | * | + | *Continued tracking down SGTs for production run |
− | + | *Finished USC hazard curves with AWP | |
− | |||
− | |||
− | |||
== Today == | == Today == | ||
− | |||
*Check UCVM AWP results - start with projection | *Check UCVM AWP results - start with projection | ||
− | * | + | *Finish finding SGTs for production run |
− | + | *RWG USC curves almost done, do comparison when complete | |
− | * | ||
== Blocked == | == Blocked == | ||
Line 23: | Line 18: | ||
+ | *Run test of I/O forwarding on Kraken | ||
*Email CyberShake papers to Liwen | *Email CyberShake papers to Liwen | ||
*Continue testing compiler optimizations | *Continue testing compiler optimizations |
Revision as of 17:05, 21 September 2012
Yesterday
- Extracted v3 vs v3.0.3 seismograms at 218/267/11 rupture, sent to Rob
- Responded to Manuela (post-doc with Norm) about right Run IDs to use with CyberShake data
- Compared v3.0.3 TEST runs from HPC and Kraken, good match
- Continued tracking down SGTs for production run
- Finished USC hazard curves with AWP
Today
- Check UCVM AWP results - start with projection
- Finish finding SGTs for production run
- RWG USC curves almost done, do comparison when complete
Blocked
- No
Follow-ups
- No
- Run test of I/O forwarding on Kraken
- Email CyberShake papers to Liwen
- Continue testing compiler optimizations
- Run some I/O tests to get reference values
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration