Can we track changes in mileage between user updates?

[dave1693]

A search of the forum archive didn't provide me an answer to this, though I may not have been looking in the right place.

My last update was about a week and a half ago. Some time in the past 3-4 days, my traveled mileage jumped by fourteen (14) miles. I'm used to minor fluctuations, but 14 miles seems rather not-minor, so I'm wondering what happened in the highway system since my last update that could have caused such a jump in traveled miles. Is there any way to find this out?

[michih]

We can: http://forum.travelmapping.net/index.php?topic=3057

The 14mi jump might also be caused by a temporarily broken concurrency, maybe in GA?

[ntallyn]

We can: http://forum.travelmapping.net/index.php?topic=3057

The 14mi jump might also be caused by a temporarily broken concurrency, maybe in GA?

I'm hoping it's a fixed concurrency that has been previously missing. 

If it is Georgia related, there may be quite a few new miles that will be added (or removed). I'm currently going through the HDX and cleaning up all the broken concurrencies.

[michih]

GA was wild guess mileage can only raise when a concurrency is broken, not when it is fixed. I think you have not yet committed any concurreny fix. If the mileage will drop again after the next GA pull request dealing with concurrencies, it might have been this.

[yakra]

We can: http://forum.travelmapping.net/index.php?topic=3057

[yakra@noreaster /home/tmp/tm]$ paste <(diff '2019-12-26@22:01:30/logs/users/dave1693.log' '2019-12-27@21:51:55/logs/users/dave1693.log' | grep '^<') <(diff '2019-12-26@22:01:30/logs/users/dave1693.log' '2019-12-27@21:51:55/logs/users/dave1693.log' | grep '^>') | less
< Log file created at: 2019-12-25 22:28:37.461301       > Log file created at: 2019-12-26 22:07:53.084151
< Overall in active systems: 36166.96 of 972439.62 mi (3.72%)   > Overall in active systems: 36180.64 of 978224.56 mi (3.70%)
< Overall in active+preview systems: 36502.62 of 1350160.56 mi (2.70%)  > Overall in active+preview systems: 36502.62 of 1350042.00 mi (2.70%)
< GA: 446.16 of 6617.58 mi (6.74%), 453.56 of 18391.05 mi (2.47%)       > GA: 446.16 of 6619.40 mi (6.74%), 453.56 of 18258.49 mi (2.48%)
< SC: 404.76 of 4500.55 mi (8.99%), 418.44 of 10276.47 mi (4.07%)       > SC: 418.44 of 10276.47 mi (4.07%), 418.44 of 10276.47 mi (4.07%)

usasc activation?
http://travelmapping.net/user/system.php?units=miles&u=dave1693&sys=usasc
You have 15.18 mi in the system right now, which is in the right ballpark. Some of this mileage is bound to be concurrent with previously-active systems such as usaus, so that mileage would have already been counted toward active systems, and not involved in the ~14 mi increase.

[michih]

so, only active system mileage has changed but active+preview system mileage is similar?

After the cleanup to GA, the mileage will only decrease from 36502.62mi to 36501.85mi (active+preview). It seems that you have only less overlapping user list file entries (in GA).

[dave1693]

Okay, the usasc activation accounts for the entirety of the new 13.68 miles. Which is more miles on SC state highways (that aren't also US or Interstates) than I'd expected but there it is.