Difference between revisions of "Staff Priorities - Fabio"
From SCECpedia
Jump to navigationJump to searchLine 2: | Line 2: | ||
* High-F | * High-F | ||
− | ** | + | ** Generated plots for half space data with filter at 4Hz |
− | * | + | ** Sent high-F call announcement |
− | ** | + | * Site response module testing |
− | ** | + | ** Compared data with and without the GP site response module |
− | * | + | ** Posted data on web, sent e-mail to FZ |
− | ** SR code | + | * Asked JY to set up FZ BBP account so he can run simulations on BBP server |
− | ** | + | * BBP Gauntlets |
− | + | ** Worked on SR Matlab code | |
+ | ** Received more codes from NL | ||
== Today == | == Today == | ||
* Continue work on RZZ2015 | * Continue work on RZZ2015 | ||
+ | * Call with SR | ||
+ | * High-F call | ||
* SGS code debug | * SGS code debug | ||
− | |||
− | |||
* Run revised NGA-West 2 testing | * Run revised NGA-West 2 testing | ||
* Try logging into Gordon | * Try logging into Gordon | ||
Line 26: | Line 27: | ||
== Followups: == | == Followups: == | ||
− | * | + | * SR call @ 10am |
+ | * High-F call @ 11am | ||
== To Do: == | == To Do: == |
Revision as of 16:30, 28 July 2015
Contents
Yesterday
- High-F
- Generated plots for half space data with filter at 4Hz
- Sent high-F call announcement
- Site response module testing
- Compared data with and without the GP site response module
- Posted data on web, sent e-mail to FZ
- Asked JY to set up FZ BBP account so he can run simulations on BBP server
- BBP Gauntlets
- Worked on SR Matlab code
- Received more codes from NL
Today
- Continue work on RZZ2015
- Call with SR
- High-F call
- SGS code debug
- Run revised NGA-West 2 testing
- Try logging into Gordon
Blocked:
- No
Followups:
- SR call @ 10am
- High-F call @ 11am
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