Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
*Ran PP with AWP SGTs - a few workflows terminated, rerunning | *Ran PP with AWP SGTs - a few workflows terminated, rerunning | ||
| − | *RWG TEST | + | *RWG v3.0.3 TEST run complete on HPC |
*RWG USC SGT runs completed | *RWG USC SGT runs completed | ||
*Meeting with Phil | *Meeting with Phil | ||
| Line 14: | Line 14: | ||
*Run test of I/O forwarding on Kraken | *Run test of I/O forwarding on Kraken | ||
*Track down SGTs for production run | *Track down SGTs for production run | ||
| + | *Compare v3.0.3 TEST runs from HPC and Kraken | ||
== Blocked == | == Blocked == | ||
Revision as of 17:13, 20 September 2012
Yesterday
- Ran PP with AWP SGTs - a few workflows terminated, rerunning
- RWG v3.0.3 TEST run complete on HPC
- RWG USC SGT runs completed
- Meeting with Phil
- CyberShake call
- Initial test of UCVM in AWP format does not agree with reference
- Gideon finished piping code "I/O forwarding"
- Started getting list of sites together for production run
Today
- Extract v3 vs v3.0.3 seismograms at commonly tested rupture, send to Rob
- Check UCVM AWP results - start with projection
- Run test of I/O forwarding on Kraken
- Track down SGTs for production run
- Compare v3.0.3 TEST runs from HPC and Kraken
Blocked
- No
Follow-ups
- No
- 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
