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 ==
*Summer School mentor call
*Summer School call
*Recompiled libmemcached on Blue Waters
*CyberShake calls
*Recompiled CyberShake codes on Blue Waters
*Started migrating Titan codes to geo112
*Found bug in DAX generator, had to start PAS post-processing over on BW
*Looked at Shashank's AWP-ODC-SGT GPU issues, think it's related to bad inputs
*Monitored Titan run
*Monitored BW run, but OOM errors; scaled back from 10 rupture variations per batch to 5, tried again
*Continued work on DirectSynth (~90%)
*Queued SMCA 1Hz SGTs on Titan
*Added option to skip md5sum step
*Continue work on DirectSynth (~98%)


== Today ==
== Today ==
*Summer School call
*Configure better SGT inputs, test, send to Shashank
*Start migrating Titan codes to geo112
*Support Shashank with AWP-ODC-SGT GPU issues
*Monitor Titan run
*Monitor BW run
*Monitor BW run
*Monitor Titan SGTs
*Continue work on DirectSynth
*Continue work on DirectSynth
*Respond to Glenn
*Continue migrating Titan codes to geo112


== Blocked ==
== Blocked ==
Line 19: Line 21:


== Follow-ups ==
== Follow-ups ==
*CyberShake call
*No


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

Revision as of 18:02, 22 January 2015

Yesterday

  • Summer School call
  • CyberShake calls
  • Started migrating Titan codes to geo112
  • Looked at Shashank's AWP-ODC-SGT GPU issues, think it's related to bad inputs
  • Monitored BW run, but OOM errors; scaled back from 10 rupture variations per batch to 5, tried again
  • Queued SMCA 1Hz SGTs on Titan
  • Added option to skip md5sum step
  • Continue work on DirectSynth (~98%)

Today

  • Configure better SGT inputs, test, send to Shashank
  • Monitor BW run
  • Monitor Titan SGTs
  • Continue work on DirectSynth
  • Respond to Glenn
  • Continue migrating Titan codes to geo112

Blocked

  • No

Follow-ups

  • No

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration