Difference between revisions of "Staff Priorities - Fabio"

From SCECpedia
Jump to navigationJump to search
Line 1: Line 1:
 
== Yesterday ==
 
== Yesterday ==
  
* Email from CA Dept Water Resources
+
* High-F call
** Talked to JC regarding how to set CORNER_FREQ param for UCSB module
+
* Follow-up with PM
** Replied with information regarding CORNER_FREQ
+
* E-mail JY regarding opening BBP Trac
** Added information to BBP File Format page
+
* E-mail MW regarding SCEC acct/SRL articles
* Sent updated GP results to RG
+
* Converted/Tested Matlab RMG script to Python
** RG happy with results, will also update HF module soon
+
* Sent BBP runtime comparison to PM (Unit and Acceptance tests)
* Went through updated RMG code from SG
+
* Replied to RG regarding High-F files
** New script generates input file from fault parameters
 
* Converted new script from Matlab to Python
 
* Ran Unit and Acceptance tests on BBP server
 
  
 
== Today ==
 
== Today ==
Line 17: Line 14:
 
* SG rupture generator
 
* SG rupture generator
 
** Continue Matlab-to-Python conversion
 
** Continue Matlab-to-Python conversion
* Waiting for GP method reruns from RG
+
* GMSV call
 +
* BBP call with PM
  
 
== Blocked: ==
 
== Blocked: ==
Line 25: Line 23:
 
== Followups: ==
 
== Followups: ==
  
* No
+
* GMSV @ 11am
 +
* PM @ 1:30pm
  
 
== To Do: ==
 
== To Do: ==

Revision as of 18:22, 25 June 2015

Yesterday

  • High-F call
  • Follow-up with PM
  • E-mail JY regarding opening BBP Trac
  • E-mail MW regarding SCEC acct/SRL articles
  • Converted/Tested Matlab RMG script to Python
  • Sent BBP runtime comparison to PM (Unit and Acceptance tests)
  • Replied to RG regarding High-F files

Today

  • Run revised NGA-West 2 testing
  • SG rupture generator
    • Continue Matlab-to-Python conversion
  • GMSV call
  • BBP call with PM

Blocked:

  • No

Followups:

  • GMSV @ 11am
  • PM @ 1:30pm

To Do:

Short Term

Broadband Platform

  • Update GP rupture generator - Total: 3 days
    • Sent Rob parameters - done
    • Integrate code - 1 day
    • Run tests for Part-A / Part-B - 2 days
  • 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