Staff Priorities - Scott: Difference between revisions
From SCECpedia
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
* | *CyberShake calls | ||
*Outlined plan | *Outlined work plan to reduce temp data | ||
*Emailed | *Emailed Tom CyberShake sites closest to Nico's points | ||
* | *Caught up on signals course | ||
== Today == | == Today == | ||
*Email Tom requested map of CyberShake sites | |||
*Work on draft abstract for extreme scaling workshop | |||
*Start implementing plan to reduce temp data | *Start implementing plan to reduce temp data | ||
*Get timing data with rupture variation generator to Yifeng | |||
*Get timing data with rupture variation generator | |||
== Blocked == | == Blocked == | ||
| Line 17: | Line 15: | ||
== Follow-ups == | == Follow-ups == | ||
* | *La Habra call | ||
*Try out SeedMe so I can respond to Amit | *Try out SeedMe so I can respond to Amit | ||
Revision as of 17:19, 16 April 2014
Yesterday
- CyberShake calls
- Outlined work plan to reduce temp data
- Emailed Tom CyberShake sites closest to Nico's points
- Caught up on signals course
Today
- Email Tom requested map of CyberShake sites
- Work on draft abstract for extreme scaling workshop
- Start implementing plan to reduce temp data
- Get timing data with rupture variation generator to Yifeng
Blocked
- 200m TEST curve, tests of group-output-by-source until file systems return
Follow-ups
- La Habra call
- Try out SeedMe so I can respond to Amit
Areas of Responsibilities
- CyberShake
- Broadband CyberShake
- Code migration
