Celerity calculation is broken.

For some reason the thing has stopped calculating the wave celerity.


Id: 424ec1bcf56164c5afda69ab3c7a6877f42d05b3
Type: bugfix
Creation time: 2011-01-21 12:25
Creator: Mathew Topper <mathew.topper@...>
Release: 0.3 (unreleased)
Component: fifthwave.py
Status: closed : fixed fixed

Issue log

2011-09-15 15:40 Mathew Topper <mathew.topper@...> closed with disposition fixed
The celerity calculation has changed in the group version to looking for the position of the closest wave backwards from the position of the present wave and measuring the distance between them. This throughs up some odd results sometimes (quite a few jumps in celerity as it were) and so may not be so reliable. Pinning down the issue is a bit of a problem though as it might just be the data from the CFD rather than the spline fitting per se. I think a more detailed investigation could be done when better visuals of the metrics are made available for 0.4.
2011-02-09 14:39 Mathew Topper <mathew.topper@...> assigned to release 0.3 from unassigned
2011-01-21 16:22 Mathew Topper <mathew.topper@...> unassigned from release 0.2
Seems to be working to some extent. Not sure its important to find out whats wrong with it for 0.2 Maybe using a trend value would work better?
2011-01-21 12:25 Mathew Topper <mathew.topper@...> created