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 ==
*Blue Waters
*Blue Waters
**Set up cronjob for auto-submit system
**Tested auto-submit system, seems good
**Continued working on AWP-ODC-SGT GPU code - still haven't found bug, code stopped working (again), emailed Efecan
**Able to coscheduled small MPI job
**Profile vectorized RWG code -- moderately improved performance, MPI communication is limiting factor
**Started work on Python script to coordinate post-processing execution in coscheduling environment
*Stampede
*Checked on monitord DB population - issue, Karan resolved, resumed
**Continue working on offloading
*Started monitord DB population


== Today ==
== Today ==
*Blue Waters
*Blue Waters
**Test auto-submit system
**Try out SGT GPU code; if runs successfully, ask Efecan about partitioning mesh
**Work on AWP-ODC-SGT GPU code after hearing back from Efecan
**Continue working on coscheduling
*Stampede
**Continue working on offloading
*Kraken
*Kraken
**Check on SA forward sim
**Check on SA forward sim
*Check on monitord DB population
*Email Stampede staff, let them know about node crashing solution
*Email Stampede staff, let them know about node crashing solution



Revision as of 17:29, 9 April 2013

Yesterday

  • Blue Waters
    • Tested auto-submit system, seems good
    • Able to coscheduled small MPI job
    • Started work on Python script to coordinate post-processing execution in coscheduling environment
  • Checked on monitord DB population - issue, Karan resolved, resumed

Today

  • Blue Waters
    • Try out SGT GPU code; if runs successfully, ask Efecan about partitioning mesh
    • Continue working on coscheduling
  • Kraken
    • Check on SA forward sim
  • Email Stampede staff, let them know about node crashing solution

Blocked

  • No

Follow-ups

  • GB call

Finish wiki entries for Stampede and Blue Waters validation Think about readiness review Think about access to CyberShake data

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration