You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thank you for sharing this great project.
Consider in subsequent releases a possibility for users to define cost function, as they could need different metrics to evaluate the distance when computing DTW. Example of the interface (dist_func optional parameter is added):
We would need to support this also in the C code to be consistent. While not necessarily difficult to add in one location, it requires changes at multiple locations (e.g. also in the bounds) and increases the cost of maintaining. So we will have to think about how to do this consistent throughout the codebase (we already have this a bit to support ndim series).
If you urgently need this. It is not too difficult to change this in the python part (no compilation required). Simply change these two lines in the code:
In the master branch, this functionality is now available by using the inner_dist argument. When using the pure Python implementation, this can be any callable function (wrapped in an object that has as callable arguments inner_dist and result). When using the the fast dtw computation in C this needs to be one of 'euclidean' or 'squared euclidean'.
Hello DTAI Team,
thank you for sharing this great project.
Consider in subsequent releases a possibility for users to define cost function, as they could need different metrics to evaluate the distance when computing DTW. Example of the interface (dist_func optional parameter is added):
where dist_func suppose to have a signature:
The text was updated successfully, but these errors were encountered: