Difference between revisions of "Staff Priorities - Scott"
From SCECpedia
Jump to navigationJump to search| Line 7: | Line 7: | ||
== Today == | == Today == | ||
| − | |||
*Check on s001 run on Titan | *Check on s001 run on Titan | ||
*Change legend on seismogram plots | *Change legend on seismogram plots | ||
| Line 13: | Line 12: | ||
*Put new study ID in db | *Put new study ID in db | ||
| − | |||
| − | |||
*Create GP07/GP10/GP14 comparison plots | *Create GP07/GP10/GP14 comparison plots | ||
| − | |||
*Start on computational section | *Start on computational section | ||
| Line 22: | Line 18: | ||
*Propose experiments on Google doc | *Propose experiments on Google doc | ||
| − | |||
*Pull out into doc the questions we asked on last year's application, email to group | *Pull out into doc the questions we asked on last year's application, email to group | ||
Revision as of 19:40, 14 February 2017
Yesterday
- Respond to Mats's questionnaire about data integrity for Pegasus
- Review 2017 IHPCSS proposal
- Produce writeup on 2017 IHPCSS mentoring activities
- Create and email link to images of Vp, Vs, Rho without cutoffs
- Register and use ALCF token
Today
- Check on s001 run on Titan
- Change legend on seismogram plots
- Pull northern seismogram to make sure NT is large enough
- Put new study ID in db
- Create GP07/GP10/GP14 comparison plots
- Start on computational section
- Check on CyberShake on Cori after Wed
- Propose experiments on Google doc
- Pull out into doc the questions we asked on last year's application, email to group
Blocked
- No
Follow-ups
- No
Areas of Responsibilities
- CyberShake
- Broadband CyberShake
- Code migration
