Replies: 9 comments
-
This issue / warning above is still a factor. |
Beta Was this translation helpful? Give feedback.
-
should the error above indicate it is raised by measures.py? |
Beta Was this translation helpful? Give feedback.
-
Could you share the value of the covariance ( |
Beta Was this translation helpful? Give feedback.
-
This is probably caused by my data:
|
Beta Was this translation helpful? Give feedback.
-
Thanks. Looks like issue is negative covariance matrix? Does setting Any thoughts @jmbarr? |
Beta Was this translation helpful? Give feedback.
-
Thank you for the suggestion: Tested the following with no difference still returning
|
Beta Was this translation helpful? Give feedback.
-
Yup - that can't be a valid covariance matrix. The elements on the diagonal are the variance of the elements of the state vector and so have to be positive. So something went wrong when calculating This sometimes happens when the timings get mangled and you end up trying to 'predict' into the past. Check the timestamps perhaps? |
Beta Was this translation helpful? Give feedback.
-
Ok, that is a possibility (timestamp issue), this happens when I'm out of new data. Will review. Thanks. Reviewed timestamps when warning/error appears, monotonic and have 1 to 70 seconds of separation. |
Beta Was this translation helpful? Give feedback.
-
Can you trace back to the operation that caused |
Beta Was this translation helpful? Give feedback.
-
This started to appear in recent testing.
It may be caused by straight line trajectories, not sure yet.
Any suggestions on locating the root cause are welcome.
next level down
lib\scipy\spatial\distance.py(1094)mahalanobis()
(Pdb++) delta
array([-52882.94101612, -106.38527496])
(Pdb++) VI
CovarianceMatrix([[1.37098147e-07, 0.00000000e+00],
[0.00000000e+00, 1.37098147e-07]])
ss/measures.py/:167
added
print('u',u,'\nv',v,'\nvi',vi)
Beta Was this translation helpful? Give feedback.
All reactions