Absolutely NOT best route planned - simple to find better, ABPR fails
- Done
|
R |
Richardboschroder |
abetterrouteplanner.com?plan_uuid=9f08aa60-2fba-4aa8-bee8-b55ebbba7364
THIS is the optimal route , driven it several times. One simple stop in Løddekopinge Sveden on the way back.
BUT this route you ABPR would NEVER calculate, only because i KNOW the Løddekopinge stop will be the optimal, and add it as a Waypoint.
Try remove the Løddekøpinge stop, and let ABPR calculate the route, it will lead you on a HUGE Detour or more than 30minutes, just to save you 4KM !!, but why - i ask for FASTEST route !,
It will even drive you same way, down to the loddekøpinge, so we drive right by the UFC charger..
Why does ABPR prefer a 30 minunte longer route, to save 4 KM ?, when i choose FASTEST .
I'm not sure, i CAN trust ABPRs advice ?
Activity Newest / Oldest
Samuel_ABRP
Status changed to: Done
Samuel_ABRP
Hi,
You preferred Eon and Clever but not powered by eon & clever. If you add that as preferred charger as well it will take your preferred route.
Richardboschroder
no. Even with out any pref. chargers, it will go for a completely crazy route, with 1 hour chargeing at some slowcooking charger
abetterrouteplanner.com/?plan_uuid=4e041f3c-754b-4e6a-8baa-f76e23b5ea60
if you go for the FEWBUTLONG, it will choose 1 very long charge, 1 hour!!
If you look at my first route, it had only one fast charging in løddekøpinge on the way back - thats the optimal. WHy cant it find that route ?
Maybe, you cant beat the human brain, when routeplanning :-)
Bo_ABRP
Samuel does have a point, with Powered by... as a preferred charger, it does give your optimal route.
Note that it just about exactly makes it, coming to the charger with 5% SoC. There is always some internal variation of the SoC % within the planner, so it may think that you will not make it and ignore that option in some cases.
Richardboschroder
pls show me the route, planned by ABPR, with no waypoints, that match my optimal route. There is no way i can make ABPR calculate this optimal route. Even with allowing 0% soc at charger, it wont pick this optimal route :
abetterrouteplanner.com?plan_uuid=9f08aa60-2fba-4aa8-bee8-b55ebbba7364
the best it can come up with, is 2 times charging at løddekøpiinge (both on the way out and back), which is crazy, and takes much longer time.
The optimal route is ONE charging at Løddekopinge , on the way back - but ABPR wont realize that.
if you can explain to me, why MY route, which is faster, and have fewer legs, is not the optimal, and why abpr leaves this out and wont find it. pls try.
I suspect a bug, that actually cuts out the correct sollution , to reduce response time. The "travelling sales man problem" is one of the most complex to solve, and you cant examine every possible sollution, you have to cut big parts of the sollutionspace out, to avoid very very long processing time. So it might just be not possible for ABPR to do, what the human brain can do :-)
So we might have to accept, humans CAN do better planning than computers. or , can you proove me wrong :_)
Our brains calculate slower, but smarter .
Bo_ABRP
We have just released some optimizer updates to cope with roundtrips better (especially single-charge roundtrips).
On your example, removing all network preferences, I get abetterrouteplanner.com/?plan_uuid=9c03aa99-2c15-4637-8ffd-fcff41cda9d9
which uses the Lödde UFC charger. However, if I allow the Helsingborg Ionity again, it will pick that one since it actually is faster (according to our model).
Richardboschroder
No. My rute is the fastest route. 4hours35. Abpr wont come up with this on its own. It prefers the stop in helsingborg and according to abpr himself, this is 4hours37. I wonder why he cant see the perfekt plan without i have to guide with via points or prefered chargers. Here me perfekt route, beat that. abetterrouteplanner.com/?plan_uuid=6f8f9a0f-9d43-4f8f-8b4f-6e00e0aba534
Samuel_ABRP
Congratulations, you beat the machine.
So i took your last route, removed all the guidepoints and the charger, added "powered by Eon & Clever" as preferred network (as that is the one you want to use preferably anyways) and it came up with this route:
abetterrouteplanner.com/?plan_uuid=90c2a884-d95c-45dd-8f20-5984cb435b1a
So it can find your route with the right settings. I guess our job is done here. The improvement we made seems to work.