Difference between revisions of "Staff Priorities - David"
(→Today:) |
|||
Line 17: | Line 17: | ||
== Today: == | == Today: == | ||
− | - | + | - CyberShake PP run monitoring<br /> |
− | - | + | - CVM-SI 20 work<br /> |
− | - | + | - Investigate static linking issue with UCVM<br /> |
− | - | + | - Further investigate Po and En-Jui's thoughts<br /> |
+ | - CyberShake rotation code<br /> | ||
+ | - Write WCC to CS converter<br /> | ||
+ | - Test rotation code?<br /> | ||
+ | - SEISM call<br /> | ||
== Blocked: == | == Blocked: == |
Revision as of 18:00, 28 February 2013
Yesterday:
- CVI-SI 20 work
- Now works with UCVM, with dynamic linking
- Generated horizontal and vertical slices
- Generated new velocity profiles
- Began investigating Po's claims
- Initial analysis is that plots are correct as per model
- VIZ-CVM
- Re-ran it for CVM-H with 1D background enabled
- Got the same results as Patrick
- Resumed CyberShake PP runs
- Seems like they're going smoothly
- CyberShake seismogram rotation scripts
- Wrote initial CS to WCC converter
Today:
- CyberShake PP run monitoring
- CVM-SI 20 work
- Investigate static linking issue with UCVM
- Further investigate Po and En-Jui's thoughts
- CyberShake rotation code
- Write WCC to CS converter
- Test rotation code?
- SEISM call
Blocked:
- No
Followups:
- None
Contribution Summary
- New release of CVM-H - helped with version, modding files, etc.
- Generate MMI information for Maren
- Learned quite a bit about UCVM code base
- Wrote description of configurable parameters for the UCVM etree mesh extraction process
- CyberShake Monitoring