Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What does "non-emitting states" mean? #14

Open
SpectorSong opened this issue Mar 8, 2021 · 1 comment
Open

What does "non-emitting states" mean? #14

SpectorSong opened this issue Mar 8, 2021 · 1 comment

Comments

@SpectorSong
Copy link

Hello! First of all, thank you for developing this model, it helps me a lot in my project.
Now I have difficulty understanding "non-emitting states". The Annotation in newsonkrumm.py says:
Newson and Krumm use shortest path to handle situations where the distances between observations are larger than distances between nodes in the graph. The LeuvenMapMatching toolbox uses non-emitting states to handle this. We thus do not implement the shortest path algorithm in this class.
So what is the main difference between the two algorithm?
I noticed that your model refers to the paper:
Meert Wannes, Mathias Verbeke, "HMM with Non-Emitting States for Map Matching", European Conference on Data Analysis (ECDA), Paderborn, Germany, 2018.
But I failed to find it on the internet. If you can help me on the question, or tell me where to find the paper, I'd be very grateful.
Thanks for reading!

@wannesm
Copy link
Owner

wannesm commented Jun 29, 2021

Hi, we indeed only have an abstract available online. Put simply, a non-emitting state is a state that is not necessarily associated with an observation. Whereas a normal (emitting) state in an HMM is always associated with an observation.

In our setting an edge in the graph is a state. This means that if we have a road that consists out of 10 edges but only 2 GPS observation locations, we are not forced to map each edge to an observation. This would mean that the matching does not stop after two edges when it runs out of observations.

We have started working more actively on this toolbox again. A new version will soon be released (already available in branch feature/expand) and hope to finally write a longer description of the algorithm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants