Difference between revisions of "Staff Priorities - Scott"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
*Produced USC hazard curve
+
*Worked on 200m TEST hazard curve (until file systems went down)
*Calculated comparison curves, emailed out to group
+
*Outlined plan for reducing temporary data for 1 Hz
*Worked on 200m rupture point spacing with new RVs
+
*Emailed Gideon about locality preferences
**Calculated and insert into DB
+
*Revised DAX generator to group output by source
**200m SGTs were on scratch, have been purged
 
**Queued curve, DAX issues, emailed Karan
 
  
 
== Today ==
 
== Today ==
*Fix DAX issues, produce 200m TEST curve
+
*Start implementing plan to reduce temp data
*Revise DAX generator to group output by source
+
*Respond to Gideon
*Preliminary work on reducing temporary data
+
*Work on draft abstract for extreme scaling workshop
 +
*Catch up on signals course
  
 
== Blocked ==
 
== Blocked ==
*No
+
*200m TEST curve, tests of group-output-by-source until file systems return
  
 
== Follow-ups ==
 
== Follow-ups ==
*No
+
*Summer school call
 +
*HighF call
 +
*CyberShake calls
  
  

Revision as of 17:08, 15 April 2014

Yesterday

  • Worked on 200m TEST hazard curve (until file systems went down)
  • Outlined plan for reducing temporary data for 1 Hz
  • Emailed Gideon about locality preferences
  • Revised DAX generator to group output by source

Today

  • Start implementing plan to reduce temp data
  • Respond to Gideon
  • Work on draft abstract for extreme scaling workshop
  • Catch up on signals course

Blocked

  • 200m TEST curve, tests of group-output-by-source until file systems return

Follow-ups

  • Summer school call
  • HighF call
  • CyberShake calls


  • Try out SeedMe so I can respond to Amit
  • Start drafting abstract for extreme scaling


Areas of Responsibilities

  • CyberShake
  • Broadband CyberShake
  • Code migration