Closed JustinM2250 closed 3 years ago
:exclamation: No coverage uploaded for pull request base (
smooth-tracking@a2f6d9a
). Click here to learn what that means. The diff coverage isn/a
.
@@ Coverage Diff @@
## smooth-tracking #310 +/- ##
==================================================
Coverage ? 37.66%
==================================================
Files ? 17
Lines ? 1399
Branches ? 0
==================================================
Hits ? 527
Misses ? 810
Partials ? 62
Impacted Files | Coverage Ξ | |
---|---|---|
api/etag.go | 73.68% <0.00%> (ΓΈ) |
|
postgres/route.go | 66.40% <0.00%> (ΓΈ) |
|
api/api.go | 83.33% <0.00%> (ΓΈ) |
|
api/data_feed.go | 0.00% <0.00%> (ΓΈ) |
|
postgres/vehicle.go | 25.00% <0.00%> (ΓΈ) |
|
updater/updater.go | 4.02% <0.00%> (ΓΈ) |
|
api/fusion.go | 10.72% <0.00%> (ΓΈ) |
|
api/filesystem.go | 0.00% <0.00%> (ΓΈ) |
|
postgres/location.go | 64.96% <0.00%> (ΓΈ) |
|
api/routes.go | 0.00% <0.00%> (ΓΈ) |
|
... and 7 more |
Continue to review full report at Codecov.
Legend - Click here to learn more
Ξ = absolute <relative> (impact)
,ΓΈ = not affected
,? = missing data
Powered by Codecov. Last update a2f6d9a...ac2de5b. Read the comment docs.
Do not merge until tested
What is changed/New?
Added a change that decreases the distance the prediction travels when a turn is detected.
How was this accomplished?
How exactly did you make this change/fix? I ran the web app a few times and logged the data. Now I see that the speed for turns is probably 6-8 MPH. Therefore, I just correct the distance needed to travel whenever a turn is detected.
Additional Notes:
This may not be the best change, but it does decrease the average error by 200 meters.