Martin Lindén

Another interesting possibility is to try some imputation scheme (see https://en.wikipedia.org/wiki/Imputation_(statistics) ) . This is common in many machine learning applications, but I don't know if anyone has tried it for vbSPT.

Another interesting possibility is to try some imputation scheme (see [https://en.wikipedia.org/wiki/Imputation_(statistics)]) . This is common in many machine learning applications, but I don't know if anyone has tried it for vbSPT.

Another interesting possibility is to try some imputation scheme (see https://en.wikipedia.org/wiki/Imputation_(statistics) ) . This is common in many machine learning applications, but I don't know if anyone has tried it for vbSPT.

Another interesting possibility is to try some imputation scheme (see https://en.wikipedia.org/wiki/Imputation_(statistics). This is common in many machine learning applications, but I don't know if anyone has tried it for vbSPT.

Hi! vbSPT cannot handle missing positions, unfortunately. It can however handle a large number of trajectories, so one way forward might be to split up your data and analyse the stretches between missing values as distinct, independent trajectories. In that case, it might also be a good idea enforce a lower limit on the trajectory length and discard anything with less than, say 5-10 points (experimetns with simulated data might help you choose). If you are able to supply a localisation uncertainty...

Dear Asok, it is difficult to say just form that. Could you provid a little more detail, for example about what is the content of the hmm struct? Best, Martin

Dear Alok, I think the problem might be that arrow.m is an old version that is not compatible with your matlab versions, see https://se.mathworks.com/matlabcentral/answers/230792-why-does-arrow-fail-r2015a Please try to update Tools/displayHMMmodel/private/arrow.m in vbSPT with the latest version from https://se.mathworks.com/matlabcentral/fileexchange/278-arrow and see if that helps. Best regards, Martin

Note to readers: this discussion moved offline to allow exchange of private data....