Thanks GregBoys. I've read the excellent DC Rainmaker post. I'm not terribly inclined to change my swimming to suit the software defects of a watch. I used the Finis Swimsense watch for years and would find it perfectly accurate for 19 of 20 swims, dropping maybe a length on 1/20th of workouts. So it's possible to get this right. It's a $300 watch, it should just work.
I had a chance to test the watch this weekend, after training it on my freestyle stroke.
My original question:
Ambit2 - does it actually work for pool swimming?
Short answer:
NO. Not for me, not with the movescount.com app. It's completely useless.
I can however import to
sporttracks.mobi and the data is fixed up and corrected so it's pretty much usable.
If you're interested... read on about my experience. Hopefully this will help you use your Ambit 2 more effectively.
The Plan
I set out to test the watch on freestyle swimming (the only stroke I can do) in a 25 yard pool. I used the first length to train the watch, then did the following:
225y free (back to short end of pool) [hit lap button]
(1 minute rest) [hit lap button]
200y free [hit lap button]
(1 minute rest) [hit lap button]
75y free [hit lap button]
------
Total distance: 500 yards.
I'm an amateur swimmer, I don't push off the wall very hard, but I'm not flailing around in the pool by any means. NOTE: I used the technique promoted by DC Rainmaker hitting [LAP] at each set, however I didn't hit the stop/start on the rest laps - hitting two buttons every set seems obnoxious (and actually, the Ambit2 handled this fine).
Movescount.com fails... big time
Below is what I see in movescount.com. You can see right off it dropped quite a lot of turns, which throws off distance, which throws off pace, and SWOLF, and pretty much everything.
Time and pace also include rests, making the app somewhat useless (even assuming it detected turns correctly). On the plus side
it detected all my strokes perfectly (after I trained it).
Where did this happen? Lets look at the charts to get a clue:
The swim starts out good, but goes downhill quickly. You can see 3 lengths where it's missed one turn (doubling pace), one where it missed 3 turns and detected a turn after a few seconds (showing me at world record pace for a few seconds, LOL), and the last set it's dropped two turns.
I'm not sure why this is jumping around but all the high values are wrong. I breathe every 3 strokes... it seems to be confusing it.
The lengths table gives a better view. I've circled all the wrong turn detections. OUCH. I've also added the interval breaks, which should add to 225, 200, 75.
SportTracks does much better
It's not a complete loss. I uploaded this to sporttracks.mobi - the data fix algorithms kicked in, added turns where needed and accounted for rest time.
The same pace/stroke charts look much cleaner:
You can see one length where it's tried to fix a missed turn and misplaced it. Still very close.
The intervals table looks perfect:
And the lengths looks good, again showing exactly where the turn/length couldn't be fixed:
Conclusion
If pool swimming with the Ambit 2 is working for you... AWESOME! For myself, I needed to fix a lot of data problems:
* Missed turns: 5 of 20 turns were missed. Total distance (and pace and SWOLF) wrong.
* Extra turns: 1 turn after 2 seconds. I'm not Michael Phelps - this should be easy to detect in the watch.
* Website doesn't exclude rest laps
* Stroke rate may be incorrect (need to look at data, possibly adding extra stroke every time I breathe)
Pros:
* Stroke detection seemed fine after "training"
I think Suunto can do much better on their swim algorithms and hope this improves in a future firmware update.