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

The HMM looks like have an accumulation delay?? #6

Open
Sunnystaste opened this issue Jul 18, 2019 · 0 comments
Open

The HMM looks like have an accumulation delay?? #6

Sunnystaste opened this issue Jul 18, 2019 · 0 comments

Comments

@Sunnystaste
Copy link

JG_2 3G{J`ZSBHJ23 }VF S

            long start = System.currentTimeMillis();
            hmmManager.setGpsList(gpslist);
            List<Foot_Data> list = hmmManager.GetLocations();
            long end = System.currentTimeMillis();
            Log.e("HMM TIME COST", String.valueOf(end - start));

public List<Foot_Data> GetLocations() {
    setUpClass();
    ViterbiAlgorithm<RoadPosition, GpsMeasurement, RoadPath> viterbi =
            new ViterbiAlgorithm<>();
    TimeStep<RoadPosition, GpsMeasurement, RoadPath> prevTimeStep = null;
    for (GpsMeasurement gpsMeasurement : gpsList) {
        final Collection<RoadPosition> candidates = computeCandidates(gpsMeasurement);
        final TimeStep<RoadPosition, GpsMeasurement, RoadPath> timeStep =
                new TimeStep<>(gpsMeasurement, candidates);
        computeEmissionProbabilities(timeStep);
        if (prevTimeStep == null) {
            viterbi.startWithInitialObservation(timeStep.observation, timeStep.candidates,
                    timeStep.emissionLogProbabilities);
        } else {
            computeTransitionProbabilities(prevTimeStep, timeStep);
            viterbi.nextStep(timeStep.observation, timeStep.candidates,
                    timeStep.emissionLogProbabilities, timeStep.transitionLogProbabilities,
                    timeStep.roadPaths);
        }
        prevTimeStep = timeStep;
    }
    List<Foot_Data> list = new ArrayList<>();
    List<SequenceState<RoadPosition, GpsMeasurement, RoadPath>> roadPositions =
            viterbi.computeMostLikelySequence();
    for (SequenceState<RoadPosition, GpsMeasurement, RoadPath> s : roadPositions){
        Point p = s.state.position;
        Road_Data road_data = s.state.road_data;
        list.add(new Foot_Data(p,road_data));
    }
    return list;
}

The GetLocations is an method to achieve map-matching algorithm. It works well,but we have find something wrong with the TIME COST,HMM looks like have an accumulation delay. Could you please tell me why the TIME COST will increase? And if I want to resolve this problem, what should I do? THK U

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

1 participant