Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
Scottcal (talk | contribs)
No edit summary
Scottcal (talk | contribs)
No edit summary
Line 1: Line 1:
== Yesterday ==
== Yesterday ==
*Blue Waters:
*Blue Waters:
**Resolve velocity model issues, passed validation
**Continued working through workflow creator, added new capabilities
*Stampede:
**Investigated issues behind stage-out of job status:  looks like scontrol stops being called
**Tried test with slurm2, same problem
**Found typo in logging
*Kraken:
*Kraken:
**Queued up forward simulation
**Forward simulation completed, started extracting seismograms, rotation issue, emailed with Rob
*Started putting Blue Waters information on internal wiki
*Finished putting Blue Waters information on internal wiki, emailed group
*Responded to Gideon with information to run CyberShake TEST case


== Today ==
== Today ==
Line 14: Line 11:
**Continue working through workflow creator
**Continue working through workflow creator
*Stampede:
*Stampede:
**Continue investigating GRAM issues
**Support GRAM staff investigation of Perl script hanging
*Kraken:
*Kraken:
**Monitor forward simulation
**Add rotation to seismogram extraction, continue with comparison
*Finish putting Blue Waters information on internal wiki
*Email ISI to ask about gathering metrics from Study 2.2
*Email CyberShake list to announce Study 2.2 completion
*Wiki entries for Blue Waters and Stampede validation
*Wiki entries for Blue Waters and Stampede validation


Line 24: Line 22:


== Follow-ups ==  
== Follow-ups ==  
*CyberShake calls
*No


== Areas of Responsibilities ==
== Areas of Responsibilities ==

Revision as of 18:08, 8 March 2013

Yesterday

  • Blue Waters:
    • Continued working through workflow creator, added new capabilities
  • Kraken:
    • Forward simulation completed, started extracting seismograms, rotation issue, emailed with Rob
  • Finished putting Blue Waters information on internal wiki, emailed group
  • Responded to Gideon with information to run CyberShake TEST case

Today

  • Blue Waters:
    • Continue working through workflow creator
  • Stampede:
    • Support GRAM staff investigation of Perl script hanging
  • Kraken:
    • Add rotation to seismogram extraction, continue with comparison
  • Email ISI to ask about gathering metrics from Study 2.2
  • Email CyberShake list to announce Study 2.2 completion
  • Wiki entries for Blue Waters and Stampede validation

Blocked

  • No

Follow-ups

  • No

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration