Staff Priorities - Scott: Difference between revisions
From SCECpedia
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
*Try multiple tests with AWP-ODC-SGT on Kraken to see if we can get any agreement | *Try multiple tests with AWP-ODC-SGT on Kraken to see if we can get any agreement | ||
*Look for obvious errors in profile run | *Look for obvious errors in profile run | ||
*Try Jaguar log-in | |||
== Blocked == | == Blocked == | ||
| Line 18: | Line 19: | ||
== Follow-ups == | == Follow-ups == | ||
*No | *No | ||
== Areas of Responsibilities == | == Areas of Responsibilities == | ||
* CyberShake 1.4 | * CyberShake 1.4 | ||
* Broadband CyberShake | * Broadband CyberShake | ||
* Code migration | * Code migration | ||
Revision as of 17:33, 29 March 2012
Yesterday
- Tried to run AWP-ODC-SGT post-processing workflow on Ranger, found weird Condor errors
- Ran AWP-ODC-SGT post-processing, much higher hazard curves
- Compare profile run results, don't match - error somewhere
- Ran AWP-ODC-SGT on Kraken with Shiyu's executable, got different results
- Tried running AWP-ODC-SGT with user scottcal, got 3rd executable and 3rd set of results
- Asked Patrick to try, got 4th executable
Today
- Try running individual seismogram synthesis for values with big differences
- Debug weird Condor errors between shock and Ranger
- Try multiple tests with AWP-ODC-SGT on Kraken to see if we can get any agreement
- Look for obvious errors in profile run
- Try Jaguar log-in
Blocked
- No
Follow-ups
- No
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration
