Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to searchLine 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
− | * | + | *CyberShake calls |
− | * | + | *Rolled out new version of extract_sgt_mpi |
− | * | + | *Worked on UCVM install on Blue Waters -- traced to setting errno=33 somewhere odd |
− | + | *Successful RWG -> AWP mesh converter testing on HPC | |
== Today == | == Today == | ||
− | * | + | *Install and test pegasus 4.2 on shock |
− | *Continue working on | + | *Continue working on CyberShake install on Blue Waters |
− | * | + | *Experiment with RWG -> AWP mesh converter to find optimal core count |
== Blocked == | == Blocked == | ||
Line 14: | Line 14: | ||
== Follow-ups == | == Follow-ups == | ||
− | * | + | *No |
*Watch Morgan's AGU presentation | *Watch Morgan's AGU presentation |
Revision as of 18:20, 17 January 2013
Yesterday
- CyberShake calls
- Rolled out new version of extract_sgt_mpi
- Worked on UCVM install on Blue Waters -- traced to setting errno=33 somewhere odd
- Successful RWG -> AWP mesh converter testing on HPC
Today
- Install and test pegasus 4.2 on shock
- Continue working on CyberShake install on Blue Waters
- Experiment with RWG -> AWP mesh converter to find optimal core count
Blocked
- No
Follow-ups
- No
- Watch Morgan's AGU presentation
- Run test of I/O forwarding on Kraken
- Continue testing compiler optimizations
- Run some I/O tests to get reference values
- Reply to TACC, NICS regarding authorized people
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration