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 ==
*Resumed PAS 1 Hz run on Blue Waters when system comes back; issue with jobs failing which I think is related to BW upgrade
*Summer School mentor call
*Resumed WNGC workflow on Titan
*Recompiled libmemcached on Blue Waters
*Prepare SBSM 1 Hz post-processing on Titan
*Recompiled CyberShake codes on Blue Waters
*Continued work on DirectSynth (~80%)
*Found bug in DAX generator, had to start PAS post-processing over on BW
*Monitored Titan run
*Continued work on DirectSynth (~90%)


== Today ==
== Today ==
*Summer School mentor call
*Summer School call
*Recompile libmemcached on Blue Waters
*Start migrating Titan codes to geo112
*Recompile CyberShake codes on Blue Waters
*Support Shashank with AWP-ODC-SGT GPU issues
*Monitor Titan run
*Monitor Titan run
*Monitor BW run
*Continue work on DirectSynth
*Continue work on DirectSynth


Line 16: Line 19:


== Follow-ups ==
== Follow-ups ==
*Blue Waters call
*CyberShake call


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

Revision as of 18:08, 21 January 2015

Yesterday

  • Summer School mentor call
  • Recompiled libmemcached on Blue Waters
  • Recompiled CyberShake codes on Blue Waters
  • Found bug in DAX generator, had to start PAS post-processing over on BW
  • Monitored Titan run
  • Continued work on DirectSynth (~90%)

Today

  • Summer School call
  • Start migrating Titan codes to geo112
  • Support Shashank with AWP-ODC-SGT GPU issues
  • Monitor Titan run
  • Monitor BW run
  • Continue work on DirectSynth

Blocked

  • No

Follow-ups

  • CyberShake call

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration