i hope to post video, of my racing of tiny’s race this Saturday, @Tom_Shelton bets if @Eric_Schlange_ZwftIn will DQ if i do all 4 races, like he did last time. i mean the time i won then he DQ me. 
You have the same values at the top and bottom of the cat, so if you are 56 you are either c or b depending on your existing category
I would like to resell my VO2 for those who want to go to A (negotiable price) 
.
More seriously, why this change, this time using VO2 max, what is the point? 
VO2 is only being used for this weekend’s Tiny Race series. It’s one of the category enforcement options, but the non-standard ones aren’t used very often. Something a bit different, could be more relevant for those races.
If you’re 56 you are cat C. >56 means anything greater than 56 but not 56. This is basic computer programming 101.
1 Like
Only that mine is 40.1. I feel personally attacked.
Not sure I follow.
The at Home Cycling & Running Virtual Training App shows you your “zVO2” to one decimel place, for example mine is currently 36.1, well below E threshold of 40.
If you had a zVO2 of 56.0, my take is you would be in C.
If your zVO2 was 56.1, you would be in B.
“zVO2” looks to be almost 10% lower than the formula used at https://intervals.icu/ looking at my own stats, so I’m now curious as to how many non-lightweight racers have to race in a higher pen compared to standard Category Enforcement zMAP. Likewise for racers able to race in a lower pen, such as @Bath_Salts .
Plus I expect we will have a few sandbaggers who haven’t done much racing at their true ability recently, enter a lower pen based on low zVO2 figures and then smash the field this weekend.
Given ZwiftHQ’s history for questionable “zX” metrics, I’d be more inclined to use the Compound Score custom option, which is 5mins pure Watts x 5mins W/Kg. But let’s see what happens.
1 Like
Yes I know that it only concerns the tiny race… we just want to bring a little novelty to a race which I find quite attractive but which is still quite disturbed by a faulty Zwift power 
mine is showing exactly 56, can only enter B
Two possibilities spring to mind…
Maybe your zVO2 is somewhere between 56.0 and 56.05, but is rounded down in your feed?
Maybe the ranges haven’t been posted as configured, so for example C is 48 to <56?
To all the lonely A category riders, and the brave people who want to race them, I created a new mass-start event with 5 custom categories based on the VirtuSlo configuration created by @DejanPresen . All categories start from the same pen and are visible to each other during the race. Wednesdays at 18:10 UTC. We have three clubs promising to bring riders to the event for a smackdown but solo riders are more than welcome. Please tell your friends, tell your club, you can all race together until you’re not friends anymore. The first race on 5 June will be 3 laps of Loop de Loop. Routes will change every week so tell me which one you want.
Sign up: Rhino Racing Frenemies Forever
4 Likes
If that is the case then surely they should have contingency plans… It’s only number checking after all and maybe they need to revisit that…i asked years ago about having zwiftpower accuracy go to a further decimal point but was out rightly told by James that it wasn’t beneficial to being accurate
It’s also possible that the simplified table that Eric shared doesn’t perfectly reflect the expressions used in the event configuration, which look a little different.
Yet my zwift profile shows me bang on 56…this is a zwift issue nothing to do with the event configuration tbh
Just looked at some results. Tight groupings, but why do all of the times for each cat look like they’re in reverse order? All of the D times are faster than the A times?
example: ht tps://zwiftpower.com/events.php?zid=4396539
I think that will get fixed when Eric processes the results, including disqualifying “snipers.” Been a while since I last did Tiny Races before this morning, but D used to set off first, except for race 4 where they set off last.
Pen E wasn’t bad besides a handful who possibly shouldn’t have joined E at all and may well be promoted to D if same VO2 ranges are used next week. One racer dominated and pretty sure they got a Category Enforcement promotion to C.
Besides the flyer (Lutton), it was just like I remembered from a few months back, a leading group of ~20 breaking away and fighting for the top finishing spots… A brutal reintroduction to threshold+ intervals after concentrating on base to try and improve my stamina!
Ahh… yes I see that somehow he posts results back into the Zwift events listing and corrects times. Why is it though that the times are all screwed up – looks like zwiftpower’s finish times for every cat is based on when the first group starts out (which is D)? Staggered starts are common and don’t usually see this issue.
That’s only on zwiftpower. If you look at the results on companion the times are correct for each group, and the groups finished in the expected order.
Zwiftpower doesn’t do elapsed times very well. It only stores the event start time to go with the actual finish time, so as these races are set up with D going first the other categories get minutes added to their elapsed times.
It’s done deliberately so that the order can be changed to allow the slower pens more time between rounds if needed. Actually looks an oversight from @Eric_Schlange_ZwftIn that E pen started last in the first race.