Difference between revisions of "Staff Priorities - Fabio"
From SCECpedia
Jump to navigationJump to search| Line 1: | Line 1: | ||
== Yesterday == | == Yesterday == | ||
| − | * | + | * Updated Trac site with new codes/tasks |
| − | ** | + | * Ran UCVM on BW |
| − | + | ** cvmsi 500 cores, cybershake region | |
| − | ** | + | ** obtained mesh |
| − | * | + | * Installed EEW software on laptop, installed in software lab |
| − | * Ran | + | * Ran SG's rupture generation code |
| − | ** | + | ** Got 50 SRF files in about 3 hours |
| − | * | + | * Updated GP rupture generator with new code from RG |
| + | * Responded to BBP query | ||
== Today == | == Today == | ||
| − | * | + | * Create netcdf file from mesh from BW |
* Run revised NGA-West 2 testing | * Run revised NGA-West 2 testing | ||
| − | + | * Run SG's code for single realization | |
| − | * Run SG's code | ||
* Try RG's new rupture generator code | * Try RG's new rupture generator code | ||
| + | ** HPCC Part-A and Part-B | ||
| + | * Return EEW computer to JY | ||
== Blocked: == | == Blocked: == | ||
| Line 24: | Line 26: | ||
== Followups: == | == Followups: == | ||
| − | * | + | * High-F call @ 11am |
== To Do: == | == To Do: == | ||
Revision as of 17:06, 16 June 2015
Contents
Yesterday
- Updated Trac site with new codes/tasks
- Ran UCVM on BW
- cvmsi 500 cores, cybershake region
- obtained mesh
- Installed EEW software on laptop, installed in software lab
- Ran SG's rupture generation code
- Got 50 SRF files in about 3 hours
- Updated GP rupture generator with new code from RG
- Responded to BBP query
Today
- Create netcdf file from mesh from BW
- Run revised NGA-West 2 testing
- Run SG's code for single realization
- Try RG's new rupture generator code
- HPCC Part-A and Part-B
- Return EEW computer to JY
Blocked:
- No
Followups:
- 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
