How do you adjust for that now? Do you treat Valby's times differently since she runs that way?
Everything is adjusted to be 1.3% slower right now, which was the previous average difference between TiC PRs and 5k PRs (now the difference is 0% with the normalization). I do not treat any individual runner's times differently.
Valby is not elevating the times of others in the race, nor is any one runner. The race is scored based on the median of the differences between scores and times.
By ‘elevating’, I meant she is probably influencing the times of others in those races to be faster than what they would have run if she wasn’t in the race.
By ‘elevating’, I meant she is probably influencing the times of others in those races to be faster than what they would have run if she wasn’t in the race.
I wonder if that effect holds true glfor the main pack? They probably let her go and just run their own race except for a few at the front, or who decide to chase her.
Just saying it’s bad doesn’t really help me make it better. If you can direct me to what you believe to be bad, I can look into why it’s making mistakes and tweak the algorithm. Idk why you’d go through the effort of making this thread just to hate on the website - nobody is making you use it.
The only reason I do 5k times is so that you can understand the relative differences. Imho I don’t really know how to think about what the difference between a 160 and 180 speed rating is. But I do know the difference between 15:00 and 15:30. I also think the 5k equivalents do pretty well at predicting early season indoor times from what I’ve seen.
I’ve been planning on adding an override feature in the simulator for a while - just haven’t gotten around to it. Managing tfrrs data errors is more work than people realize. That, and I do have a real job as well…
Hey, I think I've identified one possible source of significant error... although I'm not sure how you would really correct for it. Certain parts of the country *cough* the south *cough* don't necessarily have good track 5ks from most runners, I find a lot down here really don't run great 5k times, since the weather turns to crap by April. And when your races are filled with guys who don't run great 5k times (compared to fitness), it will throw things off quite a bit.
By ‘elevating’, I meant she is probably influencing the times of others in those races to be faster than what they would have run if she wasn’t in the race.
I wonder if that effect holds true glfor the main pack? They probably let her go and just run their own race except for a few at the front, or who decide to chase her.
There probably is some ‘trickle’ down effect, from the top runners somewhat influencing their slower teammates, which in-turn influence the others around them in the pack.
I wonder if that effect holds true glfor the main pack? They probably let her go and just run their own race except for a few at the front, or who decide to chase her.
There probably is some ‘trickle’ down effect, from the top runners somewhat influencing their slower teammates, which in-turn influence the others around them in the pack.
For instance, the top seven runners at Nuttycombe this year ran faster times than the top seven last year, which is remarkable, considering how worse the conditions were. So if the top runners are stringing out sooner than normal, due to the rabbit up front, it allows the pack to free up sooner.
There probably is some ‘trickle’ down effect, from the top runners somewhat influencing their slower teammates, which in-turn influence the others around them in the pack.
For instance, the top seven runners at Nuttycombe this year ran faster times than the top seven last year, which is remarkable, considering how worse the conditions were. So if the top runners are stringing out sooner than normal, due to the rabbit up front, it allows the pack to free up sooner.
A more obvious example was the faster than normal times posted on the OSU course at Natty’s last year.
Just saying it’s bad doesn’t really help me make it better. If you can direct me to what you believe to be bad, I can look into why it’s making mistakes and tweak the algorithm. Idk why you’d go through the effort of making this thread just to hate on the website - nobody is making you use it.
The only reason I do 5k times is so that you can understand the relative differences. Imho I don’t really know how to think about what the difference between a 160 and 180 speed rating is. But I do know the difference between 15:00 and 15:30. I also think the 5k equivalents do pretty well at predicting early season indoor times from what I’ve seen.
I’ve been planning on adding an override feature in the simulator for a while - just haven’t gotten around to it. Managing tfrrs data errors is more work than people realize. That, and I do have a real job as well…
Hey, I think I've identified one possible source of significant error... although I'm not sure how you would really correct for it. Certain parts of the country *cough* the south *cough* don't necessarily have good track 5ks from most runners, I find a lot down here really don't run great 5k times, since the weather turns to crap by April. And when your races are filled with guys who don't run great 5k times (compared to fitness), it will throw things off quite a bit.
This is basically only a problem if the south is in a bubble. Races are not only scored based on the 5ks people have run — are scored based on an equal weighting of all of their performances that season. Some unbiased races eventually make it into the profiles of the southern runners, their fitness efforts update, which updates the ratings of the southern courses and make those ratings less biased, and so on.
This is, however, one of my main concerns about applying the algorithm to high school.
Lacctic is also weak when comparing across divisions. Some mid major d1 dude with a 15:00 track pr will have a better lacctic rating than a 14:20 d3 guy. Ethan Gregg is only decent until he runs at paul short etc. I just watched a d3 guy go 24:00 and run a course record (on a course that's held a national meet) and his rating is 14:42...making him a crappy d1 guy. I think the algorithm puts too much emphasis on division.
Lacctic is also weak when comparing across divisions. Some mid major d1 dude with a 15:00 track pr will have a better lacctic rating than a 14:20 d3 guy. Ethan Gregg is only decent until he runs at paul short etc. I just watched a d3 guy go 24:00 and run a course record (on a course that's held a national meet) and his rating is 14:42...making him a crappy d1 guy. I think the algorithm puts too much emphasis on division.
Honest question: do you think the algorithm actually considers division or do you mean that guys like Gregg are probably just not running full tilt to win meets?
Hey Bijan, thanks for Lacctic, it has made XC much more fun to follow. A couple added features I would love to see:
A checkbox on the simulation to use each runner's MOST RECENT PERFORMANCE TiC instead of their overall rating.
A checkbox on the simulation to use each runner's ALL TIME HIGH TiC performance. I know this could get dicey with outliers factoring in but would be fun to think if everybody optimized on the day what would they get, rather than the weighted average TiC.
That is not what he said. He said it does not consider altitude. He said it uses relative times. Using relative times accounts for all factors including altitude.
An example of this was the South regional run on a short course where Valby ran 17:59.
Lacctic calculated that this was her slowest race of the year. It did not consider course length in its calculation. It was based on relative times.
Does it make any sense that she would run her slowest race of the year at Regionals? It's much more likely that she ran one of her fastest races, being in top shape and presumably in the middle of a taper and running against better competition, but that her competition was really going hard for the first meet that truly counted in their best peaked or almost peaked race, to qualify for nationals, while she was guaranteed a spot and probably a win well before the end of the race so she may have eased in a bit. In other words, the gap was decreased to the competition because the competition was better and she wasn't 100% and the system equates that with a slower performance but it wasn't. It was probably worth about 18:40 6k. If, however, nationals performances for the top runners are usually rated by lacctic as their best of the season, despite competition and effort for the field being the best, I will eat my words.
An example of this was the South regional run on a short course where Valby ran 17:59.
Lacctic calculated that this was her slowest race of the year. It did not consider course length in its calculation. It was based on relative times.
Does it make any sense that she would run her slowest race of the year at Regionals? It's much more likely that she ran one of her fastest races, being in top shape and presumably in the middle of a taper and running against better competition, but that her competition was really goi
It’s quite possible she ran slower at Regionals in prep for Natty’s. Some runners (e.g., Chmiel) didn’t even run Regionals.
I think there currently is a bug of some sorts at LACCTiC. When I click on an athlete name to see their 2023 LACCTiC Fitness Estimate (LFE), the latest NCAA Cross Country Champs is listed twice, and I think that is swaying the LFE.
I think there currently is a bug of some sorts at LACCTiC. When I click on an athlete name to see their 2023 LACCTiC Fitness Estimate (LFE), the latest NCAA Cross Country Champs is listed twice, and I think that is swaying the LFE.
* I’m referring to the 2023Season Fitness Estimate. In computing that number, I think LACCTiC is double-counting Natty’s, true?
In the list of races for the 2022 Season Fitness Estimate, the Natty’s race is NOT listed twice.
I think there currently is a bug of some sorts at LACCTiC. When I click on an athlete name to see their 2023 LACCTiC Fitness Estimate (LFE), the latest NCAA Cross Country Champs is listed twice, and I think that is swaying the LFE.
* I’m referring to the 2023Season Fitness Estimate. In computing that number, I think LACCTiC is double-counting Natty’s, true?
In the list of races for the 2022 Season Fitness Estimate, the Natty’s race is NOT listed twice.
I can’t bear the 50 or more negativity posts against lacctic which is the best product I’ve seen! lacctic is remarkable. Have you tried the USATF website?! Lacctic runs circles around that joke. And have you tried the wtfa website which I believe lacctic is mirroring? Lacctic improves that website and they make $250M and run every diamond league race. Lacctic is free and created by a “washed up” grad student. Bijan might be washed up but seb coe, the pres at wtfa, needs to make bijan the head of website developm
I think there currently is a bug of some sorts at LACCTiC. When I click on an athlete name to see their 2023 LACCTiC Fitness Estimate (LFE), the latest NCAA Cross Country Champs is listed twice, and I think that is swaying the LFE.
* I’m referring to the 2023Season Fitness Estimate. In computing that number, I think LACCTiC is double-counting Natty’s, true?
In the list of races for the 2022 Season Fitness Estimate, the Natty’s race is NOT listed twice.
Thank you, Sir, for correcting the issue! The problem appears to be resolved.
Help us build the best running shoe review site for a chance to win a LetsRun t-shirt.Help us build the best running shoe review site for a chance to win one of 10 LetsRun t-shirts.