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 3: Line 3:
*RWG TEST SGT runs competed on HPC, submitted PP
*RWG TEST SGT runs competed on HPC, submitted PP
*RWG USC SGT runs completed
*RWG USC SGT runs completed
*Meeting with Phil
*CyberShake call
*CyberShake call
*Initial test of UCVM in AWP format does not agree with reference
*Initial test of UCVM in AWP format does not agree with reference
*Gideon finished piping code "I/O forwarding"
*Started getting list of sites together for production run


== Today ==
== Today ==
*Extract v3 vs v3.0.3 seismograms at commonly tested rupture, send to Rob
*Extract v3 vs v3.0.3 seismograms at commonly tested rupture, send to Rob
*Check UCVM AWP results - start with projection
*Check UCVM AWP results - start with projection
*Run test of I/O forwarding on Kraken
*Track down SGTs for production run


== Blocked ==
== Blocked ==

Revision as of 17:09, 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
  • Meeting with Phil
  • CyberShake call
  • Initial test of UCVM in AWP format does not agree with reference
  • Gideon finished piping code "I/O forwarding"
  • Started getting list of sites together for production run

Today

  • Extract v3 vs v3.0.3 seismograms at commonly tested rupture, send to Rob
  • Check UCVM AWP results - start with projection
  • Run test of I/O forwarding on Kraken
  • Track down SGTs for production run

Blocked

  • No

Follow-ups

  • No


  • 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