Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
← Older editNewer edit →
Scottcal (talk | contribs)
8,097 edits
No edit summary
Scottcal (talk | contribs)
8,097 edits
No edit summary
Line 1: Line 1:
== Yesterday ==
== Yesterday ==
*Blue Waters:
*Blue Waters:
**Continued working through workflow creator - integrating with RunManager
**Added support for data movement when SGT jobs complete
*Kraken:
*Stampede:
**Moved seismogram extraction to shock
**Followed up with GRAM group - can't look at it until next week
*Extracted forward seismograms - after a few false starts, sent results to Rob for review
**Wrote cron job to kill job-managers*Complete wiki entries for Blue Waters and Stampede validation
*Added support for multiple runs with same site in RunManager
*Emailed Phil forward seismogram overlays
*Started wiki entries for Blue Waters and Stampede validation
*Emailed David path to PSA code with example
*Accepted request to review HPC Summer School applications


== Today ==
== Today ==
*Blue Waters:
*Blue Waters:
**Add support for data movement when SGT jobs complete
**Test RunManager integration, data movement, qsub dependencies
**Test RunManager integration and qsub dependencies
*Stampede:
*Stampede:
**Follow-up with GRAM group re: hanging Perl script
**Post-process 4 sets of WNGC SGTs (test support for multiple runs with same site, cron job)
*Kraken:
*Email forward seismogram overlays to the CyberShake group
**Post-process 4 sets of WNGC SGTs and test support for multiple runs with same site
*Email ISI to ask about gathering metrics from Study 2.2
*Complete wiki entries for Blue Waters and Stampede validation
*Email Phil forward seismogram overlays
*Email David path to PSA code with example


== Blocked ==
== Blocked ==
Line 26: Line 19:


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


Email ISI to ask about gathering metrics from Study 2.2
Think about readiness review
Think about readiness review
Think about access to CyberShake data
Think about access to CyberShake data

Revision as of 21:23, 13 March 2013

Yesterday

  • Blue Waters:
    • Added support for data movement when SGT jobs complete
  • Stampede:
    • Followed up with GRAM group - can't look at it until next week
    • Wrote cron job to kill job-managers*Complete wiki entries for Blue Waters and Stampede validation
  • Emailed Phil forward seismogram overlays
  • Emailed David path to PSA code with example

Today

  • Blue Waters:
    • Test RunManager integration, data movement, qsub dependencies
  • Stampede:
    • Post-process 4 sets of WNGC SGTs (test support for multiple runs with same site, cron job)
  • Email forward seismogram overlays to the CyberShake group

Blocked

  • No

Follow-ups

  • CyberShake calls


Email ISI to ask about gathering metrics from Study 2.2 Think about readiness review Think about access to CyberShake data

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration
Retrieved from "https://strike.scec.org/index.php?title=Staff_Priorities_-_Scott&oldid=6936"