Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
| − | * | + | *Confirmed that there's a discrepency with saved SGTs on Titan test |
| − | * | + | *Worked on BBP RotD100 code; matched it to reference results, close to Baker RotD code also |
| − | + | *Seg faults in 1 Hz post-processing; possibly in kickstart? | |
| − | |||
| − | * | ||
| − | |||
| − | |||
| − | |||
== Today == | == Today == | ||
| − | * | + | *Modify RotD100 code to take command-line arguments instead of file |
| − | * | + | *Write code to read in seismogram files, call RotD100 code |
| − | * | + | *Investigate seg faults with Gideon |
| − | * | + | *Dig into saved SGT issue on Titan |
| − | |||
== Blocked == | == Blocked == | ||
Revision as of 17:04, 22 September 2014
Yesterday
- Confirmed that there's a discrepency with saved SGTs on Titan test
- Worked on BBP RotD100 code; matched it to reference results, close to Baker RotD code also
- Seg faults in 1 Hz post-processing; possibly in kickstart?
Today
- Modify RotD100 code to take command-line arguments instead of file
- Write code to read in seismogram files, call RotD100 code
- Investigate seg faults with Gideon
- Dig into saved SGT issue on Titan
Blocked
- No
Follow-ups
- No
Areas of Responsibilities
- CyberShake
- Broadband CyberShake
- Code migration
