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 call
*Resumed PAS 1 Hz run on Blue Waters when system comes back; issue with jobs failing which I think is related to BW upgrade
*Forwarded Rob's responses to Norm
*Resumed WNGC workflow on Titan
*Continued developing DirectSynth (~45%)
*Prepare SBSM 1 Hz post-processing on Titan
*Took another pass at CUG abstract, got feedback from Phil
*Continued work on DirectSynth (~80%)
*Got login on Titan
*Emailed Val to check on status of Titan purge exemptions


== Today ==
== Today ==
*Integrate Phil's changes into CUG abstract
*Summer School mentor call
*Resume PAS 1 Hz run on Blue Waters when system comes back
*Recompile libmemcached on Blue Waters
*Prepare SBSM 1 Hz post-processing
*Recompile CyberShake codes on Blue Waters
*Monitor Titan run
*Continue work on DirectSynth
*Continue work on DirectSynth


== Blocked ==
== Blocked ==
*Blue Waters downtime extended
*No


== Follow-ups ==
== Follow-ups ==
*ER-Rest call
*Blue Waters call


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

Revision as of 18:04, 20 January 2015

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
  • Resumed WNGC workflow on Titan
  • Prepare SBSM 1 Hz post-processing on Titan
  • Continued work on DirectSynth (~80%)

Today

  • Summer School mentor call
  • Recompile libmemcached on Blue Waters
  • Recompile CyberShake codes on Blue Waters
  • Monitor Titan run
  • Continue work on DirectSynth

Blocked

  • No

Follow-ups

  • Blue Waters call

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration