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 ==
*Sent out SCEC abstract for review
*Submitted SCEC abstract
*Emailed Kim to ask about requested runs
*Found UCVM 11.9 still built on Kraken, passed tests
*PP run on 40x240 revealed a few (~0.05%) errors with memcached, variable utilization
*Got UCVM 12.2 working, somehow, resubmitted test job
*Started looking at UCVM 12.2 proj4 errors
*Modified jbsim3d to keep going with memcached errors
*Got PP runs plots from Gideon, looks like zip jobs are taking a long time, added option to separate zip jobs into independent job


== Today ==
== Today ==
*Submit SCEC abstract
*Check on UCVM run, continue testing integrated DAX generator
*Runs for Rob and Kim
*Try another PP run, 40x240, with separated zip jobs and continuing through memcached errors
*Rebuild UCVM 11.9 to have working version for testing
*Modify jbsim3d to keep going with memcached errors
*Test integrated DAX generator
*Ask Gideon to generate plots of PP runs to understand low utilization


== Blocked ==
== Blocked ==
Line 19: Line 16:
*No
*No


*Runs for Rob and Kim
*Continue testing compiler optimizations
*Continue testing compiler optimizations
*Run some I/O tests to get reference values
*Run some I/O tests to get reference values

Revision as of 17:04, 13 August 2012

Yesterday

  • Submitted SCEC abstract
  • Found UCVM 11.9 still built on Kraken, passed tests
  • Got UCVM 12.2 working, somehow, resubmitted test job
  • Modified jbsim3d to keep going with memcached errors
  • Got PP runs plots from Gideon, looks like zip jobs are taking a long time, added option to separate zip jobs into independent job

Today

  • Check on UCVM run, continue testing integrated DAX generator
  • Try another PP run, 40x240, with separated zip jobs and continuing through memcached errors

Blocked

  • No

Follow-ups

  • No
  • Runs for Rob and Kim
  • Continue testing compiler optimizations
  • Run some I/O tests to get reference values


Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration