Fixed activity classifier and model updates stalling indefinitely due to a single hung CoreML prediction blocking all activity type work (BIG-335)
Fixed timeline processing being unnecessarily cancelled and restarted when navigating into item details or activity type selection, causing slower timeline resolution (BIG-336)
Fixed place scoring producing near-zero scores for places with limited visit history, due to KDE bandwidth collapsing when histogram data is concentrated in a single bin (BIG-332)
Improvements
Current visits are no longer penalised for being shorter than a place’s typical visit duration — a 2-minute-old visit at a place expecting 60-minute stays now receives neutral scoring until enough time has passed (BIG-76)
Improved place proximity scoring with Gaussian decay, providing better separation between overlapping places (BIG-332)
Map: Is it possible to change map type?, and also dark or light? as here in the evening it’s really hard to read.
Activity: when on any given day, and clicking on Activity I’d expect it to show the actual I was on, but no, its on the date it was last used, that’s a bit awkward like shown on the two attached pictures
I have this (these) unknown place(s) that it doesn’t seem to be able to deal with, which is actually just one place I stayed for s party almost all day.
I haven’t added a Map Settings view yet, but will prioritise that now! This feedback on the public beta is good signal for knowing which features from the old app I should focus on first, versus which ones no one seems to care about so I can neglect
This is how the old app works too Though the old app has an option for “View in Activity” and also from Activity tab an option for “View in Timeline”. That’s missing in Arc Editor, so I’ll prioritise that too!
You should be able to use the normal edit and confirm/correct flows to clean those up. Though that loading spinner suggests something’s backed up.
If that happens again, check in the Debug Info view under “Active Operations”. I’ll be very curious to see the screenshot from there! That’d offer strong clues to what’s going on.
@Hutima Thanks for that! Yeah that clarifies perfectly.
And I think the build 41 that I just sent out a minute ago will help a lot! I think we found the root cause of that particular kind of problem and fixed it.
If it’s still happening after updating to build 41 in TestFlight, definitely let me know. Because at this point our impression is that we’ve nailed all the remaining problem cases.
This one seems to have solved itself by having some additional time to think about it​
Another also interesting thing we use to be able to do in the old version was be able to zoom in on an area and click on individual lines, like on the screen I have this “outage” drive in upper left side, where I did a short visit that I’d like to catch as such, but I can’t mark the drive line at all, and thereby I can’t either edit and/or find brief stops on it - can that be accomplished somehow?
That’s still possible, and about as well as in the old app. But you have to tap really carefully on the line, and in practice it often takes many attempts to get it!
The Mapbox SDK doesn’t catch the taps on the path lines most of the time, which was a problem in the old app too. At some point I want to try to find a way to … help it catch the taps better. Maybe do something like add fake invisible path lines that are much wider, thus larger tap areas. But I suspect that’ll create new messes.
Anyway yeah, it’s possible in the new app! But it takes lots of attempts, and can be quite frustrating
Hmm. That blank timeline is confusing! I’m not sure what that’s about…
But at least it’s improved a bit I’ll see if I can find some more things to fix today, and hopefully get a new build out this afternoon or tomorrow. And thanks for the feedback and debug info! Super helpful.
Yeah this is … I suspect it’s actually something at the low level maths scale of things. Like, LocoKit2’s location data handling is significantly better than old LocoKit’s, but in some edge cases like underground trains old LocoKit did better almost by accident.
I can improve that, for sure. I’ll just need to do some solid testing on underground trains for a few days. I keep meaning to do that when in Bangkok or Tokyo but never quite getting around to it. Hopefully soon!
Ah yep. It’s now looking like all the remaining problems (well almost all) are around CoreML model updates (those updateModel lines in the Active Operations).
Ok hopefully today I’ll figure out what’s going on there! Thanks for the screenshots. Super helpful!
like shown on the two attached pictures
Though the old app has an option for “View in Activity” and also from Activity tab an option for “View in Timeline”. That’s missing in Arc Editor, so I’ll prioritise that too!
