Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Ran into ODBC wall, going to try JDBC RC
+
*Got JDBC RC working
 +
*Tested GPU capability in BW workflows - some issues, possibly related to cores per node
 
*Continued debugging SeisPSA_large_mem
 
*Continued debugging SeisPSA_large_mem
*CyberShake call - Rob going to create new rupture variation generator
+
*Installed UCVM + CVM-SI26, ran workflow, stalled on curve creation step - OpenSHA needs Z1.0 and Z2.5 from SI26
*Modified workflow to include option for AWP GPU code
 
  
 
== Today ==
 
== Today ==
*Work on JDBC RC once John creates DB
+
*When Z data is installed in OpenSHA, calculate SI26 curve
*Continue debugging SeisPSA_large_mem when Stampede returns
+
*Work on GPU capability in BW workflows
*Test GPU capability in BW workflows
+
*When Phil gives ok, email Mats with talk topics
*Try installing UCVM + CVM-SI26 when setup script is ready
+
*Finish debugging SeisPSA_large_mem
  
 
== Blocked ==
 
== Blocked ==

Revision as of 20:49, 28 October 2013

Yesterday

  • Got JDBC RC working
  • Tested GPU capability in BW workflows - some issues, possibly related to cores per node
  • Continued debugging SeisPSA_large_mem
  • Installed UCVM + CVM-SI26, ran workflow, stalled on curve creation step - OpenSHA needs Z1.0 and Z2.5 from SI26

Today

  • When Z data is installed in OpenSHA, calculate SI26 curve
  • Work on GPU capability in BW workflows
  • When Phil gives ok, email Mats with talk topics
  • Finish debugging SeisPSA_large_mem

Blocked

  • No

Follow-ups

  • Phil to discuss RLS options, new RV generator on Monday at 1 pm PT

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration