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 ==
*AWP SGT jobs at USC finished
*Ran PP with AWP SGTs - a few workflows terminated, rerunning
*Ran verification test with RWG v3.0.3, seeing ~10% differences
*RWG TEST SGT runs competed on HPC, submitted PP
*Emailed Rob with test results and analysis of differences, Rob says expected
*RWG USC SGT runs completed
*Submitted TEST SGTs on hpc to verify that v3.0.3 results on Kraken are good
*CyberShake call
*Submitted USC SGTs on kraken to get hazard curve
*Initial test of UCVM in AWP format does not agree with reference
*Worked on direct calculation of UCVM in AWP format


== Today ==
== Today ==
*Run PP with AWP SGTs at USC
*Extract v3 vs v3.0.3 seismograms at commonly tested rupture, send to Rob
*Monitor RWG TEST and USC SGT runs
*Check UCVM AWP results - start with projection
*Run tests of UCVM in AWP format


== Blocked ==
== Blocked ==

Revision as of 17:06, 20 September 2012

Yesterday

  • Ran PP with AWP SGTs - a few workflows terminated, rerunning
  • RWG TEST SGT runs competed on HPC, submitted PP
  • RWG USC SGT runs completed
  • CyberShake call
  • Initial test of UCVM in AWP format does not agree with reference

Today

  • Extract v3 vs v3.0.3 seismograms at commonly tested rupture, send to Rob
  • Check UCVM AWP results - start with projection

Blocked

  • No

Follow-ups

  • Phil regarding CyberShake
  • CyberShake call


  • Email CyberShake papers to Liwen
  • Continue testing compiler optimizations
  • Run some I/O tests to get reference values


Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration