Kind of lets them off the hook for a previous incorrect prediction tho?I've thought about the rule preventing last second flips/changes in predictions in all the prediction threads. Rather that counting the original prediction only, I think if there are conflicting predictions and the last prediction happens at least 48 hours prior to the committment, we'll rule it a Push if the last prediction is correct.
I supposed 1hit-1miss =push/0Kind of lets them off the hook for a previous incorrect prediction tho?
Why not just count both predictions? 1 hit, 1 miss.
Disagree. 1-1 is 50% a push doesnt bring down (or up %)I supposed 1hit-1miss =push/0
Yea guy below you answered how I see it.I supposed 1hit-1miss =push/0
Yea guy below you answered how I see it.
A push means they're off the hook for the initial wrong prediction.
1 miss and 1 hit means they get recorded accurately. Which is 50%.
Yea, listen nobody is going to bat 100% in recruiting predictions bc its fluid like you said.I see your point for sure. On the one hand, kids change their mind. On the other hand, coming up with a SWAG early on and then changing your crystal ball is a cop out. Should just say "leans" not "predict", so it doesn't count either way.
these aren't pushes. They are bad predictions. He predicted in June that Cole would be a Cane, and he committed to UGA. That's not a push. Lindend, do Geo and Flo have something on you that you don't want to get exposed?Accuracy change after adjusting to the new rule on conflicting predictions being a push. (10/14 compared to 10/16)
Hit Rate: 71% (10/14) [Sample size too small, don't draw conclusions from this percentage]
2023 Predictions
[TABLE=alternate]
[TR]
[TD]Date[/TD]
[TD]Prediction[/TD]
[TD]Outcome[/TD]
[TD]Verdict[/TD]
[/TR]
[TR]
[TD]9/8[/TD]
[TD]Expectation for Cole is UGA[/TD]
[TD]Picked UGA[/TD]
[TD]Push[/TD]
[/TR]
[TR]
[TD]6/29[/TD]
[TD]Schmo isn't coming to Miami[/TD]
[TD]Picked Pitt[/TD]
[TD]Push[/TD]
[/TR]
[TR]
[TD]6/29[/TD]
[TD]Would be shocked if Cole isn't a Cane[/TD]
[TD]Picked UGA[/TD]
[TD]Push[/TD]
[/TR]
[TR]
[TD]6/27[/TD]
[TD]Cole on commit watch[/TD]
[TD]Picked UGA[/TD]
[TD]Push[/TD]
[/TR]
[TR]
[TD]6/27[/TD]
[TD]Geo see Schmo committing[/TD]
[TD]Picked Pitt[/TD]
[TD]Push[/TD]
[/TR]
[/TABLE]
I didn't expect such a firestorm of disagreement after not a single person complained about the proposed change. Given the ferocity of the disagreement, clearly, further refinements are needed! Hopefully, we can come up with a consensus that allows a more accurate view of the hits/misses.I've thought about the rule preventing last second flips/changes in predictions in all the prediction threads. Rather that counting the original prediction only, I think if there are conflicting predictions and the last prediction happens at least 48 hours prior to the committment, we'll rule it a Push if the last prediction is correct.
That equally lets them off the hook (both solutions have the same problem). One Hit, one miss ends up a push.Kind of lets them off the hook for a previous incorrect prediction tho?
Why not just count both predictions? 1 hit, 1 miss.
You have a point here. It actually does lower their accuracy rates (although not as much as the original model which only counted the miss). You and @Da Jumbo Mutombo might have the correct model.Disagree. 1-1 is 50% a push doesnt bring down (or up %)
1 miss and 1 hit means they get recorded accurately. Which is 50%.
Yea, the Wiltfong model that allows the last second flips is bogus and should be avoided at all costs. We will only take changes 48 hours prior to the commitment. Otherwise, the original prediction is the only one that will count.Otherwise, this is like what Wiltfong does with his crystal balls. Always changes them last second and keep his % high.
My take: Your thread, your criteria. If someone doesn't like it, tough. It's not like you're skewing to get a desired result.I didn't expect such a firestorm of disagreement after not a single person complained about the proposed change. Given the ferocity of the disagreement, clearly, further refinements are needed! Hopefully, we can come up with a consensus that allows a more accurate view of the hits/misses.
I didn't expect such a firestorm of disagreement after not a single person complained about the proposed change. Given the ferocity of the disagreement, clearly, further refinements are needed! Hopefully, we can come up with a consensus that allows a more accurate view of the hits/misses.
That's not a push. Lindend, do Geo and Flo have something on you that you don't want to get exposed?