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 ==
*Fixed error condition in workflow status
*Found issue with regex output catalog, fixed
*Modified GPU meshes to be nz=200
*Posted code versions on study page
*Submitted GPU job for USC to test fix
*Test data transfer speeds Blue Waters -> HPCC
*Technical readiness review
*NCSA meeting
*Found and fixed issue with 'more' in cronjob auto workflow submission
*Added check to suspend workflows if can't authenticate to BW jobmanager


== Today ==
== Today ==
*Look over TTS letter
*Test regex output catalog with final GPU curves
*Add ability to determine nodetype to Blue Waters cron job
*Calculation GPU comparison curves, post to wiki, notify group
*If USC GPU curve looks good, queue other 7
*Tag code in SVN once regex issue is resolved
*Tag code in SVN
*Work on study tracker
*Post versions on study page
*Edit Pegasus paper
*Add ability to track runs as part of a study to run manager on northridge.usc.edu
*Send photo + bio to Karan
*Test data transfer speeds Blue Waters -> HPCC
*Add check to suspend workflows if can't ping BW


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


== Follow-ups ==
== Follow-ups ==
*High-F call
*No
*Blue Waters call


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

Revision as of 17:54, 13 February 2014

Yesterday

  • Found issue with regex output catalog, fixed
  • Posted code versions on study page
  • Test data transfer speeds Blue Waters -> HPCC
  • NCSA meeting
  • Found and fixed issue with 'more' in cronjob auto workflow submission
  • Added check to suspend workflows if can't authenticate to BW jobmanager

Today

  • Test regex output catalog with final GPU curves
  • Calculation GPU comparison curves, post to wiki, notify group
  • Tag code in SVN once regex issue is resolved
  • Work on study tracker
  • Edit Pegasus paper
  • Send photo + bio to Karan

Blocked

  • No

Follow-ups

  • No

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration