Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to searchLine 2: | Line 2: | ||
*Blue Waters: | *Blue Waters: | ||
**Monitored production runs | **Monitored production runs | ||
− | ** | + | **Continued work on parallelized rupture variation generator - decided to change strategies |
*Stampede: | *Stampede: | ||
− | ** | + | **Check disk usage for SGTs on /scratch - 20 TB |
− | * | + | **Emailed David for help with cleanup |
+ | **Got simple offloading code working | ||
== Today == | == Today == | ||
*Blue Waters: | *Blue Waters: | ||
**Monitor production runs | **Monitor production runs | ||
− | ** | + | **Work on revised approach to just read points from rupture geometry file |
− | |||
− | |||
== Blocked == | == Blocked == | ||
− | * | + | *Stampede - down for maintenance |
== Follow-ups == | == Follow-ups == | ||
− | * | + | *No |
Revision as of 17:03, 7 May 2013
Yesterday
- Blue Waters:
- Monitored production runs
- Continued work on parallelized rupture variation generator - decided to change strategies
- Stampede:
- Check disk usage for SGTs on /scratch - 20 TB
- Emailed David for help with cleanup
- Got simple offloading code working
Today
- Blue Waters:
- Monitor production runs
- Work on revised approach to just read points from rupture geometry file
Blocked
- Stampede - down for maintenance
Follow-ups
- No
Check on SA forward sim
Email Stampede staff, let them know about node crashing solution
Finish wiki entries for Stampede and Blue Waters validation
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration