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 == | ||
* | *Added CyberShake section to pegasus-mpi-cluster XSEDE paper | ||
*Repeated RWG/AWP comparison with CVM-H, looks good | |||
* | *Reran AWP with CVM-S TEST site with modified Q - made mistake, running again | ||
*Checked on new TAU run on Kraken - need to rerun | |||
* | *Monitor workflow run | ||
*Talked to Gideon - killing workflow, need to change cores/node | |||
== Today == | == Today == | ||
* | *Working on correctly specifying cores/node | ||
*Add CyberShake section | *Add references to CyberShake section in paper | ||
*Look at plots from AWP forward run if new CVM-S run still has ringing | |||
*Look at plots from AWP forward run | |||
*Add default striping change on Kraken dirs to workflow | *Add default striping change on Kraken dirs to workflow | ||
== Blocked == | == Blocked == | ||
Revision as of 17:03, 17 April 2012
Yesterday
- Added CyberShake section to pegasus-mpi-cluster XSEDE paper
- Repeated RWG/AWP comparison with CVM-H, looks good
- Reran AWP with CVM-S TEST site with modified Q - made mistake, running again
- Checked on new TAU run on Kraken - need to rerun
- Monitor workflow run
- Talked to Gideon - killing workflow, need to change cores/node
Today
- Working on correctly specifying cores/node
- Add references to CyberShake section in paper
- Look at plots from AWP forward run if new CVM-S run still has ringing
- Add default striping change on Kraken dirs to workflow
Blocked
- No
Follow-ups
- No
Areas of Responsibilities
- CyberShake 1.4
- Broadband CyberShake
- Code migration