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 ==
*Monitored Experiment 2 filtering test, complete
*UCVM paper call
*Emailed velocity plots to CB
*Uploaded Experiment 2 test results, replotted sources, emailed to group
*Emailed Tom with update from CyberShake call, asked for opinion
*Email CyberShake group with new experiment results
*OLCF resumed scratch access, copied things over
*Queued up insertion of Study 14.2 RotD results (for CVM-S4.26)
*Continued debugging DirectSynth
*Continued debugging DirectSynth
*Sent out application email to past Summer School attendees
*Created 2 Hz source


== Today ==
== Today ==
*Upload Experiment 2 test results to wiki
*Replot sources on same plot
*Email CyberShake group with new experiment results
*Queue up 1 Hz run, 2 Hz source
*Queue up 1 Hz run, 2 Hz source
*Plot seismograms from Experiment 2
*Continue debugging DirectSynth; seismograms agree with reference but PSA results do not
*Start working on CAAR proposal
*Start working on CAAR proposal
*Start calculating + inserting Study 14.2 RotD results (for CVM-S4.26)
*Continue debugging DirectSynth


== Blocked ==
== Blocked ==
Line 21: Line 17:


== Follow-ups ==
== Follow-ups ==
*UCVM paper call
*No


== Areas of Responsibilities ==
== Areas of Responsibilities ==

Revision as of 18:07, 6 February 2015

Yesterday

  • UCVM paper call
  • Uploaded Experiment 2 test results, replotted sources, emailed to group
  • Email CyberShake group with new experiment results
  • Queued up insertion of Study 14.2 RotD results (for CVM-S4.26)
  • Continued debugging DirectSynth
  • Created 2 Hz source

Today

  • Queue up 1 Hz run, 2 Hz source
  • Plot seismograms from Experiment 2
  • Continue debugging DirectSynth; seismograms agree with reference but PSA results do not
  • Start working on CAAR proposal

Blocked

  • No

Follow-ups

  • No

Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration