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 ==
*Couldn't replicate seg faults, tried full-scale, repeated;  tracked down to corruption in Y extracted SGTs
*Found seg faults, produced good hazard curve
*Submitted source partitioning job
*Source partitioning job completed (successfully?)
*Submitted Z component runs
*Completed fwd runs with RWG and AWP
*Completed Z component runs with RWG and AWP
*Submitted halfspace runs
*Submitted halfspace runs
*Plotted and sent other sets of AWP/RWG seismograms from TEST hazard curve
*Responded to Rob re:MPI_Sendrecv()


== Today ==
== Today ==
*Continue debugging seg faults
*Generate list of metrics to produce from Kraken runs
*Generate list of metrics to produce from Kraken runs
*When Kraken returns, check on queued runs
*Test JBSim3d with header files
*Check on RWG and AWP halfspace runs
*Use reciprocity to generate Z seismograms with RWG and AWP
*Extract seismograms at TEST site location from RWG and AWP forward runs


== Blocked ==
== Blocked ==
*Kraken down for PM
*No


== Follow-ups ==
== Follow-ups ==
*Storage call
*No


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

Revision as of 17:08, 4 May 2012

Yesterday

  • Found seg faults, produced good hazard curve
  • Source partitioning job completed (successfully?)
  • Completed fwd runs with RWG and AWP
  • Completed Z component runs with RWG and AWP
  • Submitted halfspace runs

Today

  • Generate list of metrics to produce from Kraken runs
  • Test JBSim3d with header files
  • Check on RWG and AWP halfspace runs
  • Use reciprocity to generate Z seismograms with RWG and AWP
  • Extract seismograms at TEST site location from RWG and AWP forward runs

Blocked

  • No

Follow-ups

  • No

Areas of Responsibilities

  • CyberShake 1.4
  • Broadband CyberShake
  • Code migration