Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Found seg fault in extract_sgt_mpi, tested, tried full workflow, passed
+
*CyberShake calls
*Started installing CyberShake SGT codes on Blue Waters - issues with UCVM
+
*Rolled out new version of extract_sgt_mpi
*Testing for RWG -> AWP mesh -- issues with MPI I/O on HPC, emailed them
+
*Worked on UCVM install on Blue Waters -- traced to setting errno=33 somewhere odd
*Talked to David about moving SGTs from Ranger to Ranch
+
*Successful RWG -> AWP mesh converter testing on HPC
  
 
== Today ==
 
== Today ==
*Roll out new version of extract_sgt_mpi
+
*Install and test pegasus 4.2 on shock
*Continue working on UCVM install on Blue Waters
+
*Continue working on CyberShake install on Blue Waters
*Resume RWG -> AWP mesh testing when HPC has issues worked out
+
*Experiment with RWG -> AWP mesh converter to find optimal core count
  
 
== Blocked ==
 
== Blocked ==
Line 14: Line 14:
  
 
== Follow-ups ==
 
== Follow-ups ==
*CyberShake calls
+
*No
  
 
*Watch Morgan's AGU presentation
 
*Watch Morgan's AGU presentation

Revision as of 18:20, 17 January 2013

Yesterday

  • CyberShake calls
  • Rolled out new version of extract_sgt_mpi
  • Worked on UCVM install on Blue Waters -- traced to setting errno=33 somewhere odd
  • Successful RWG -> AWP mesh converter testing on HPC

Today

  • Install and test pegasus 4.2 on shock
  • Continue working on CyberShake install on Blue Waters
  • Experiment with RWG -> AWP mesh converter to find optimal core count

Blocked

  • No

Follow-ups

  • No
  • Watch Morgan's AGU presentation
  • Run test of I/O forwarding on Kraken
  • Continue testing compiler optimizations
  • Run some I/O tests to get reference values
  • Reply to TACC, NICS regarding authorized people


Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration