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 ==
*Resolved proxy issue on Blue Waters
*Confirmed that there's a discrepency with saved SGTs on Titan test
*Issue with Blue Waters GridFTP alias; using workaround for now
*Worked on BBP RotD100 code; matched it to reference results, close to Baker RotD code also
*CyberShake calls
*Seg faults in 1 Hz post-processing; possibly in kickstart?
*HighF call
*Submitted 1 Hz post-processing workflow on Blue Waters
*0.5 Hz 200m GPU code running very slowly on BW; emailed Efecan
*Replied to Omar and Nicole (NCSA science author)
*Downloaded PEER data, ran through RotD100 code, doesn't match reference results


== Today ==
== Today ==
*Finish up workflow on Titan
*Modify RotD100 code to take command-line arguments instead of file
*Pick a few CyberShake sites to calculate 300 km cutoff for
*Write code to read in seismogram files, call RotD100 code
*Monitor 1 Hz post-processing on BW
*Investigate seg faults with Gideon
*Make recommended changes from Efecan
*Dig into saved SGT issue on Titan
*Try to get alternative RotD100 code


== Blocked ==
== Blocked ==

Revision as of 17:04, 22 September 2014

Yesterday

  • Confirmed that there's a discrepency with saved SGTs on Titan test
  • Worked on BBP RotD100 code; matched it to reference results, close to Baker RotD code also
  • Seg faults in 1 Hz post-processing; possibly in kickstart?

Today

  • Modify RotD100 code to take command-line arguments instead of file
  • Write code to read in seismogram files, call RotD100 code
  • Investigate seg faults with Gideon
  • Dig into saved SGT issue on Titan

Blocked

  • No

Follow-ups

  • No

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration