Staff Priorities - Scott: Difference between revisions

From SCECpedia
Jump to navigationJump to search
← Older editNewer edit →
Scottcal (talk | contribs)
8,097 edits
No edit summary
Scottcal (talk | contribs)
8,097 edits
No edit summary
Line 1: Line 1:
== Yesterday ==
== Yesterday ==
*CyberShake calls
*Installed and tested pegasus 4.2 on shock - bug in pegasus-sc-converter, fixed
*Rolled out new version of extract_sgt_mpi
*Finished installing CyberShake SGT codes on Blue Waters
*Worked on UCVM install on Blue Waters -- traced to setting errno=33 somewhere odd
*Discovered all AWP SGTs have been purged from Kraken, started re-verification process
*Successful RWG -> AWP mesh converter testing on HPC


== Today ==
== Today ==
*Install and test pegasus 4.2 on shock
*Add separate header functionality to extract_sgt_mpi (required for AWP SGTs)
*Continue working on CyberShake install on Blue Waters
*Test CyberShake codes on Blue Waters
*Experiment with RWG -> AWP mesh converter to find optimal core count
*Finish re-verifying AWP code on Kraken


== Blocked ==
== Blocked ==

Revision as of 18:06, 18 January 2013

Yesterday

  • Installed and tested pegasus 4.2 on shock - bug in pegasus-sc-converter, fixed
  • Finished installing CyberShake SGT codes on Blue Waters
  • Discovered all AWP SGTs have been purged from Kraken, started re-verification process

Today

  • Add separate header functionality to extract_sgt_mpi (required for AWP SGTs)
  • Test CyberShake codes on Blue Waters
  • Finish re-verifying AWP code on Kraken

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