search

mricon / ingress-fieldplan

Generate an easy workplan for Ingress fielding excursions
GNU General Public License v3.0
31 stars 8 forks source link

Problem with cached data? #13

Closed danwie closed 5 years ago

danwie commented 5 years ago

I’m using version 3.2.0.

When running:

$ ./fieldplan.py -c idkfa -m bicycling -s https://docs.google.com/spreadsheets/d/1LNwNO7KuXxkvkyfCmfYuz4OZ0c9voP0O4oV7N7nyPMc/edit?usp=sharing

I get the result:

Ctrl-C to exit and use the latest best plan
(      2.69 km, 0.11 km2, 12 portals, 55575 AP, 0:30:15): 1/10000     
(      2.48 km, 0.13 km2, 12 portals, 55575 AP, 0:28:15): 1/10000     
(      2.20 km, 0.10 km2, 12 portals, 57138 AP, 0:27:30): 33/10000     
(      1.61 km, 0.12 km2, 12 portals, 55575 AP, 0:25:15): 177/10000     
(      2.03 km, 0.12 km2, 12 portals, 56825 AP, 0:25:15): 24/10000     
(Best: 1.64 km, 0.14 km2, 12 portals, 57138 AP, 0:24:30): 10000/10000     
Saved plan cache in /Users/daniel/.cache/ingress-fieldmap/plans/bicycling-eeec006ade36f97de13326a31d6f807bb1aab15e
.
.
Total workplan distance: 1.64 km
Total workplan play time: 0:24:30 (0:00:00 bicycling)
Total AP: 57138 (33138 without capturing)
Adding "🚲 0:24:30 (1.64km/12P/57,138AP)" sheet with 29 actions
Resizing columns and adding colours
Spreadsheet generation done

Q1: What do ”0:00:00 bicycling” mean?

If i rerun with the exact command I get the result:

Loading cache data from cache /Users/daniel/.cache/ingress-fieldmap/plans/bicycling-eeec006ade36f97de13326a31d6f807bb1aab15e
Best distance of the plan loaded from cache: 1.64 km
Best coverage of the plan loaded from cache: 0.14 km2
Best AP of the plan loaded from cache: 57138
Finding an efficient plan that maximizes AP
Started 2 worker processes
Ctrl-C to exit and use the latest best plan
(      1.64 km, 0.14 km2, 12 portals, 57138 AP, 0:44:00): 1/10000     
(      2.54 km, 0.12 km2, 12 portals, 55262 AP, 0:30:00): 9/10000     
(      2.28 km, 0.11 km2, 12 portals, 57138 AP, 0:29:30): 1/10000     
(      2.46 km, 0.12 km2, 12 portals, 56512 AP, 0:29:00): 1/10000     
(      2.15 km, 0.11 km2, 12 portals, 56512 AP, 0:27:00): 7/10000     
(      2.40 km, 0.14 km2, 12 portals, 57138 AP, 0:26:30): 89/10000     
(      2.22 km, 0.15 km2, 12 portals, 56825 AP, 0:26:15): 211/10000     
(      1.82 km, 0.11 km2, 12 portals, 56512 AP, 0:26:00): 32/10000     
(      1.95 km, 0.11 km2, 12 portals, 55262 AP, 0:25:00): 147/10000     
(      1.96 km, 0.10 km2, 12 portals, 56825 AP, 0:25:15): 286/10000     
(Best: 1.32 km, 0.12 km2, 12 portals, 57138 AP, 0:24:30): 10000/10000

Q2: Why does it start using a plan of 44:00 minutes when the already cached best plan already should be 24:30 minutes? Something wrong with the cached data?

Sorry if I’m missing something obvious.