Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
| − | * | + | *Worked on tool to query UCVM for shear modulus |
| − | * | + | *Created CyberShake schematic for Pegasus group |
| − | * | + | *DirectSynth configuration issues on Cori |
| − | + | *HighF call | |
| − | * | ||
== Today == | == Today == | ||
| − | * | + | *Debug issues with DirectSynth on Cori |
| − | * | + | *If Titan comes back, work on shear modulus code |
| − | + | *Test new Pegasus registration code | |
*Install schema and required info on test DB for insertion test | *Install schema and required info on test DB for insertion test | ||
| − | |||
== Blocked == | == Blocked == | ||
| − | * | + | *Titan down, no progress on shear modulus code |
== Follow-ups == | == Follow-ups == | ||
| − | * | + | *No |
| − | |||
== Areas of Responsibilities == | == Areas of Responsibilities == | ||
Revision as of 18:05, 23 February 2016
Yesterday
- Worked on tool to query UCVM for shear modulus
- Created CyberShake schematic for Pegasus group
- DirectSynth configuration issues on Cori
- HighF call
Today
- Debug issues with DirectSynth on Cori
- If Titan comes back, work on shear modulus code
- Test new Pegasus registration code
- Install schema and required info on test DB for insertion test
Blocked
- Titan down, no progress on shear modulus code
Follow-ups
- No
Areas of Responsibilities
- CyberShake
- Broadband CyberShake
- Code migration
