Difference between revisions of "Staff Priorities - Fabio"
From SCECpedia
Jump to navigationJump to search| Line 1: | Line 1: | ||
== Yesterday: == | == Yesterday: == | ||
| − | * | + | * Worked on the arias duration code |
| − | * | + | ** before: using numpy.trapz function |
| − | ** | + | *** takes array, returns float |
| − | * | + | ** now: using scipy.integrate.cumtrapz function |
| − | * | + | *** takes n elem array, returns n-1 elem array |
| − | ** | + | ** front pad with zeros |
| + | ** O(n!) --> O(n) | ||
| + | ** 60000 points: 20-min per component to 4-sec per component | ||
| + | ** Ran tests, results look good | ||
| + | ** :) | ||
== Today: == | == Today: == | ||
| + | * Check new arias duration code into svn | ||
* Look into integrating the environment metadata code into broadband | * Look into integrating the environment metadata code into broadband | ||
| − | |||
* PyCon follow-ups | * PyCon follow-ups | ||
Revision as of 16:26, 19 March 2013
Contents
Yesterday:
- Worked on the arias duration code
- before: using numpy.trapz function
- takes array, returns float
- now: using scipy.integrate.cumtrapz function
- takes n elem array, returns n-1 elem array
- front pad with zeros
- O(n!) --> O(n)
- 60000 points: 20-min per component to 4-sec per component
- Ran tests, results look good
- :)
- before: using numpy.trapz function
Today:
- Check new arias duration code into svn
- Look into integrating the environment metadata code into broadband
- PyCon follow-ups
Blocked:
- No
Followups:
- No
