Difference between revisions of "Staff Priorities - Fabio"

From SCECpedia
Jump to navigationJump to search
Line 2: Line 2:
  
 
* Modified Anderson GoF Code
 
* Modified Anderson GoF Code
** Enabled plotting
+
** Made it a BBP module
** Format improvements (Pylint -21.56 to 8.50)
+
** Uses BBP directory structure, outputs plots in outdata
** Packaging code into BBP module
+
* Call with AS
* Tested BW login on portal
+
** Complete results for all bands (some differences)
* Checked with KO and RT about SDSU code
+
** Handed off updated code, waiting for feedback
 +
* E-mail with KO and RT regarding BBToolbox update
 +
** Code tweaks to adjust to nga 1/2 models -- need further clarification
  
 
== Today ==
 
== Today ==
  
* Complete Anderson GoF Code changes
+
* Check with KM, CG regarding NGA-West 2 validation
** Make it a BBP module
+
* Software lab EEW machine setup
* Send code back to AS for continued development
 
** Call with AS
 
  
 
== Blocked: ==
 
== Blocked: ==
Line 21: Line 21:
 
== Followups: ==
 
== Followups: ==
  
* Call with AS (TBD)
+
* High-F call @ 11am
 
* Task priorities with PM (TBD)
 
* Task priorities with PM (TBD)
  

Revision as of 17:08, 9 June 2015

Yesterday

  • Modified Anderson GoF Code
    • Made it a BBP module
    • Uses BBP directory structure, outputs plots in outdata
  • Call with AS
    • Complete results for all bands (some differences)
    • Handed off updated code, waiting for feedback
  • E-mail with KO and RT regarding BBToolbox update
    • Code tweaks to adjust to nga 1/2 models -- need further clarification

Today

  • Check with KM, CG regarding NGA-West 2 validation
  • Software lab EEW machine setup

Blocked:

  • No

Followups:

  • High-F call @ 11am
  • Task priorities with PM (TBD)

To Do:

Short Term

Broadband Platform

  • Anderson GoF code from AS - Total: 3 days
    • Analyze code, dependencies, provide AS feedback: 1 day
    • Convert code to BBP module, add module to BBP workflow: 1 day
    • Test BBP platform, produce new metrics: 1 day
  • New BBToolbox version available from SDSU - Total: 3 days
    • Incorporate SDSU changes into BBToolbox: 1 day
    • Run Part-A/Part-B validations: 2 days
  • NGA-West 2 validation on BBP - Total: 6 days
    • Contact CG, collect input scenarios: 1 day
    • Write test code: 1 day
    • Run tests: 2 days
    • Review results: 2 days
  • Setup laptop as EEW machine in software lab - Total: 1 day
    • Erase laptop, install clean Mac OS X, install EEW software: 1 day
  • Integrate Rupture Generator code from SG - Total: 28 days
    • Review code, understand inputs/outputs, run outside platform: 1 day
    • Run Part-A problem using Matlab code, review results: 1 day
    • Migrate code into BBP Platform, convert Matlab code into Python/C/Fortran, test: 20 days
    • Run Part-A/Part-B validation exercise on HPCC: 5 days (contingent on code performance)

High-F

  • Set up High-F code repository - Total: 3 days
    • Collect codes from groups, scripts - 1 day
    • Select SVN/Github repository - 1 day
    • Create repository - 1 day
  • Understand how to map station location to grid point - Total: 2 days
    • Understand approaches used by AWP and Hercules to map station location to grid point - 1 day
    • Discuss with PM, DG, how to use UCVM to do this mapping - 1 day

Medium Term

  • Package GF generation code from RG into BBP Platform
  • New raytracing code for SDSU method
  • Update Anderson method