Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
 
*Blue Waters:
 
*Blue Waters:
−
**Continued PAS and USC workflows
+
**Continued USC workflows, submitted SBSM, a few wallclock time exceeds
 
*Stampede:
 
*Stampede:
−
**Continue debugging bad I/O problem - looks like mvapich2 issue, asked Gideon to send explanatory email
+
**Continued post-processing runs
−
**Resumed post-processing runs
 
 
*Kraken:
 
*Kraken:
−
**Create scripts and reference solutions for NICS
+
**Emailed NICS staff to check in
−
*Received list of directories from David
+
**Started forward San Andreas simulation
−
*Sent list of metrics to Karan
+
*Started plotting comparison curve for wiki SBSM CVM-H curves look like CVM-S
  
 
== Today ==
 
== Today ==
 
*Blue Waters:
 
*Blue Waters:
−
**Continue USC workflows, submit next site
+
**Finish remaining USC workflow
 +
**Finish remaining SBSM workflow
 +
**Add restart capability to workflows
 +
**Determine why CVM-H and CVM-S wfs look very similar for SBSM
 
*Stampede:
 
*Stampede:
−
**Continue post-processing runs
+
**Post-process USC, SBSM workflows when complete
−
*Kraken:
+
*Kraken
−
**Check in with NICS staff, make sure things are going ok
+
**Check on San Andreas forward simulation
−
**Start forward simulations for a San Andreas and mountain events
+
*Start monitord run on aftershock
−
*Start monitord run
+
 
  
 
== Blocked ==
 
== Blocked ==

Revision as of 18:06, 1 April 2013

Yesterday

  • Blue Waters:
    • Continued USC workflows, submitted SBSM, a few wallclock time exceeds
  • Stampede:
    • Continued post-processing runs
  • Kraken:
    • Emailed NICS staff to check in
    • Started forward San Andreas simulation
  • Started plotting comparison curve for wiki SBSM CVM-H curves look like CVM-S

Today

  • Blue Waters:
    • Finish remaining USC workflow
    • Finish remaining SBSM workflow
    • Add restart capability to workflows
    • Determine why CVM-H and CVM-S wfs look very similar for SBSM
  • Stampede:
    • Post-process USC, SBSM workflows when complete
  • Kraken
    • Check on San Andreas forward simulation
  • Start monitord run on aftershock


Blocked

  • No

Follow-ups

  • No

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
Retrieved from "https://strike.scec.org/scecwiki/index.php?title=Staff_Priorities_-_Scott&oldid=7200"