hammerfest

Open full view…

Stage 1 - hammerfest

Thu, 04 Feb 2016 01:01:56 GMT

toddmarkelz
Thu, 04 Feb 2016 03:52:31 GMT

We definitely need to add teams and team scoring! I'd take some East vs. West coast action :)

trappermarkelz
Thu, 04 Feb 2016 04:01:25 GMT

Yeah, teams, team scores, also categories so there are more options to win! :)

trappermarkelz
Thu, 04 Feb 2016 04:02:33 GMT

I hear Zwift races are using cats based on you w/kg ftp. It's a new world.

toddmarkelz
Thu, 04 Feb 2016 04:06:31 GMT

That at least keeps all the people cheating with insanely high w/kg racing against each other... great idea!

trappermarkelz
Thu, 04 Feb 2016 15:01:01 GMT

Uh oh Pritesh, Handlebar-Hanley is in. Shit just got real.

priteshgandhi
Thu, 04 Feb 2016 17:34:19 GMT

Awesome - more representation from the East Coast!

trappermarkelz
Fri, 05 Feb 2016 12:31:33 GMT

RACE DAY! Hammerfest Blizzard bowl!

jaybird111
Fri, 05 Feb 2016 14:34:54 GMT

It is on!

trappermarkelz
Fri, 05 Feb 2016 17:09:55 GMT

I'm a bit worried about the number of ties on this short first stage. That is one of the learnings. Strava doesn't bring back 10ths of a second on the API... everything rounds to the closest second... even though Zwift has tenths of a second. Already seeing lots of close/tie times. So this first stage might be a bit of a wash! It just means longer stages work better to prevent ties.

jaybird111
Fri, 05 Feb 2016 17:27:27 GMT

Man that was fun, nearly spun off the rollers... I'm jealous of anyone that can stand up and hammer....

georgebonanto
Fri, 05 Feb 2016 17:27:44 GMT

I wonder if strava still uses the tenths to rank on their leaderboard. You might be able to use that to rank among tied times.

trappermarkelz
Fri, 05 Feb 2016 17:29:42 GMT

Yeah I'm looking at it as the times come in. But the API really only returns seconds. So I'll just need to make sure the leader boards and points properly handle ties.

trappermarkelz
Fri, 05 Feb 2016 21:07:03 GMT

So just did my run. And since I am paying more attention now, I grabbed screen shots. The Jersey sprint points in Zwift show my times as 15.7 and 20.48. The API would round those to 16 + 20 for a total of 36 seconds on the stage. However the stage times using the GPS on Strava has my segment times at 14s + 15s for a total of 29s... It seems like the first segment (the corrected legth) is more accurate but Broad street is too short. Curious what others think about their data. This shouldn't be an issue with Hammerfest races that take place on real roads where you can actually map it visually to real landmarks. It is hard to draw a segment in a fake world. :)

trappermarkelz
Fri, 05 Feb 2016 21:07:29 GMT

Here is my activity link to check it out: https://www.strava.com/activities/486641293/overview

georgebonanto
Fri, 05 Feb 2016 21:16:53 GMT

I had the same experience with the discrepancy between zwift sprint segment times and strava times. I think it's consistent between days/activities and between riders, so should not affect results, but it does make it hard to get an optimum time on the strava segment...

trappermarkelz
Fri, 05 Feb 2016 21:20:41 GMT

Yeah seems like that is the case. If everyone tries hard on the same timed jersey segments, it will translate into the same effort on the strava segments. They are too short to game and try and change the effort. Bare minimum that is why I tried to use pretty clear segments in Zwift and not make my own or get fancy with it. When I start mapping rides outside and accounting for stop lights and dangerous descents with multiple segments, it will get a little more tricky.

gilesdouglas
Sat, 06 Feb 2016 04:54:27 GMT

Yeah I had 15.62 and 19.65 and got 15 and 13 on the segments

gilesdouglas
Sat, 06 Feb 2016 04:55:38 GMT

Although that isn't consistent across riders (compare my times to trapper). But it'll be representative of what strava does outside too I guess

trappermarkelz
Sat, 06 Feb 2016 12:15:09 GMT

Jesus 13s on Broad? That is a monster time Giles.

jaybrewer
Sat, 06 Feb 2016 21:38:42 GMT

Bam! I've done my 2 attempts.

next