Difference between revisions of "Staff Priorities - Fabio"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
  
* Posted new results
+
* Back from PyCon
* Completed work on attenuation plots code
+
* Receipts
** Tested against Matlab version - matches results
+
* Check mesh extraction job on Blue Waters
** Run for 5 BBP methods, posted results on bbpvault
+
* Meeting with JY regarding counting downloads on hypocenter
* Updated Pylint stats
 
  
 
== Today ==
 
== Today ==
  
* Work on code review slides
+
* Review AP revised Irikura code
* Additional metrics
+
* Integrate Irikura rupture generator on BBP
** Coverage for unit tests
+
* Run tests to make sure we can reproduce AP's results
* Update Trac site
+
* Run few SO CAL events on BBP server to validate code
** Release notes page
 
* Minor documentation updates
 
  
 
== Blocked: ==
 
== Blocked: ==
Line 22: Line 19:
 
== Followups: ==
 
== Followups: ==
  
* No
+
* Allocation call @11am
  
 
== To Do: ==
 
== To Do: ==
Line 30: Line 27:
 
==== Broadband Platform ====
 
==== Broadband Platform ====
  
* Update GP rupture generator - Total: 3 days
+
* BBP Code updates needed before git migration
** Sent Rob parameters - done
+
** Remove GMT dependencies and files
** Integrate code - 1 day
+
** Move to argparse
** Run tests for Part-A / Part-B - 2 days
+
** Simplify tests to use smaller files
 
+
** Remove unused data files in tests directory
* 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
 
* NGA-West 2 validation on BBP - Total: 6 days
Line 49: Line 38:
 
** Run tests: 2 days
 
** Run tests: 2 days
 
** Review results: 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 ====
 
==== High-F ====
Line 65: Line 45:
 
** Select SVN/Github repository - 1 day
 
** Select SVN/Github repository - 1 day
 
** Create 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 ===
 
=== Medium Term ===
Line 75: Line 51:
 
* New raytracing code for SDSU method
 
* New raytracing code for SDSU method
 
* Update Anderson method
 
* Update Anderson method
 +
* BBP Projects
 
* Try logging into Gordon
 
* Try logging into Gordon

Revision as of 21:28, 13 June 2016

Yesterday

  • Back from PyCon
  • Receipts
  • Check mesh extraction job on Blue Waters
  • Meeting with JY regarding counting downloads on hypocenter

Today

  • Review AP revised Irikura code
  • Integrate Irikura rupture generator on BBP
  • Run tests to make sure we can reproduce AP's results
  • Run few SO CAL events on BBP server to validate code

Blocked:

  • No

Followups:

  • Allocation call @11am

To Do:

Short Term

Broadband Platform

  • BBP Code updates needed before git migration
    • Remove GMT dependencies and files
    • Move to argparse
    • Simplify tests to use smaller files
    • Remove unused data files in tests directory
  • 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

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

Medium Term

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