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 ==
*Calculated stats for lower velocity SGTs, sent them out
*Retried s351 post-processing on Kraken, ran successfully, matched
*JBSim3d_PSA curves matched for TEST site
*Retried ALP run with AWP on Kraken, continuing to get MPI errors
*Found error in s351 post-processing in specifying memory requirements
*Submitted SGT run with fast velocity, low Q
*Submitted double-couple run, all zeros in output
*Changed memcached invocation on Kraken to pipe output to log file
*Issue with AWP ALP run - MPI settings


== Today ==
== Today ==
*Retry s351 post-processing on Kraken
*Keep testing MPI issues with ALP run
*Retry ALP run with AWP on Kraken
*Look at small (~900) memcached errors
*
*Check low Q runs
*Queue run with ioprof to get file I/O numbers with new executables


== Blocked ==
== Blocked ==
Line 15: Line 15:


== Follow-ups ==
== Follow-ups ==
*No
*CyberShake calls





Revision as of 17:07, 6 June 2012

Yesterday

  • Retried s351 post-processing on Kraken, ran successfully, matched
  • Retried ALP run with AWP on Kraken, continuing to get MPI errors
  • Submitted SGT run with fast velocity, low Q
  • Changed memcached invocation on Kraken to pipe output to log file

Today

  • Keep testing MPI issues with ALP run
  • Look at small (~900) memcached errors
  • Check low Q runs
  • Queue run with ioprof to get file I/O numbers with new executables

Blocked

  • No

Follow-ups

  • CyberShake calls


  • Compare En-Jui's SGT results to AWP


Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration
  • Create bio, work summary, abstract for EU-US summer school