irish eyes
Footballguy
Well, it's Todd Bowles. No business being a head coach at any level.Todd Bowles choosing to kick a 55 yard FG with a veteran kicker that has a career long of 51.
Well, it's Todd Bowles. No business being a head coach at any level.Todd Bowles choosing to kick a 55 yard FG with a veteran kicker that has a career long of 51.
He had fruit.I disagreed with everything Pete Carroll did today. Hell, I probably disagreed with what he had for breakfast.
Bagel would have increased his WP by 4.3%He had fruit.I disagreed with everything Pete Carroll did today. Hell, I probably disagreed with what he had for breakfast.
Why is that odd? If you run a calculation, of course it's going to come up with a specific number.84% EWP? What an oddly specific number. Particularly with the virtually limitless number of variables that go into any NFL play (let alone the subsequent sequence of events).
Analytics are fun. One day when Bezos-Bot 2000 is all grown up they may be truly predictive. But ATM it's still pseudo science.
After a long punt, it's now 3rd and 10 from your own 4, you're trailing in the 2nd half. QB can't get the play call in before the play clock expires... call the timeout to prevent the penalty of 2 yards? I think saving the timeout might be worth more than that.
I disagreed with everything Pete Carroll did today. Hell, I probably disagreed with what he had for breakfast.
Reminds me of the time Aqib Talib took advantage of the half-the-distance rule to prevent a TD at no cost (other than to his wallet)After a long punt, it's now 3rd and 10 from your own 4, you're trailing in the 2nd half. QB can't get the play call in before the play clock expires... call the timeout to prevent the penalty of 2 yards? I think saving the timeout might be worth more than that.
I disagreed with everything Pete Carroll did today. Hell, I probably disagreed with what he had for breakfast.
Didn't want to spoil it by naming names, but, one guess which coach called this TO down 3 at the end of the 3rd quarter. But it was actually 2nd and 10 after re-checking the game log.
Then Schlereth is an idiotFormer player Mark Schlereth said it well this week: "Analytics is something stupid invented by math nerds who never played the game."
They call him Stink for a reason.Then Schlereth is an idiotFormer player Mark Schlereth said it well this week: "Analytics is something stupid invented by math nerds who never played the game."
True but I still remember a time when NFL coaches would punt from the other teams 40 just to gain 20 yards in field position. The truth lies somewhere in the middle.They call him Stink for a reason.Then Schlereth is an idiotFormer player Mark Schlereth said it well this week: "Analytics is something stupid invented by math nerds who never played the game."
But he's not entirely wrong about analytics. It provides highly questionable numbers that people who don't truly understand them take as gospel truth.
That's the problem with analytics, they provide exact percentages for all scenarios as if they could possibly determine with any degree of confidence that a team has a 76% chance of converting a 3 & 3 with a pass and only 58% if they run. Those are nonsense stats. Saying they have a better chance passing vs running is far more intellectually honest (even if that statement may also be untrue).True but I still remember a time when NFL coaches would punt from the other teams 40 just to gain 20 yards in field position. The truth lies somewhere in the middle.They call him Stink for a reason.Then Schlereth is an idiotFormer player Mark Schlereth said it well this week: "Analytics is something stupid invented by math nerds who never played the game."
But he's not entirely wrong about analytics. It provides highly questionable numbers that people who don't truly understand them take as gospel truth.
as if they could possibly determine with any degree of confidence that a team has a 76% chance of converting a 3 & 3 with a pass and only 58% if they run
I am aware of what analytics actually does and what it is presented as, and those are two entirely different things.as if they could possibly determine with any degree of confidence that a team has a 76% chance of converting a 3 & 3 with a pass and only 58% if they run
I’m afraid I’m not following.
Analytics does not determine anything.
It presents data to take it into consideration.
They don’t pull the % out of thin air. It’s the result of compiled data for similar situations
I am aware of what analytics actually does and what it is presented as, and those are two entirely different things.as if they could possibly determine with any degree of confidence that a team has a 76% chance of converting a 3 & 3 with a pass and only 58% if they run
I’m afraid I’m not following.
Analytics does not determine anything.
It presents data to take it into consideration.
They don’t pull the % out of thin air. It’s the result of compiled data for similar situations
Probably a topic for a dedicated thread though.
Reminds me of the time Aqib Talib took advantage of the half-the-distance rule to prevent a TD at no cost (other than to his wallet)After a long punt, it's now 3rd and 10 from your own 4, you're trailing in the 2nd half. QB can't get the play call in before the play clock expires... call the timeout to prevent the penalty of 2 yards? I think saving the timeout might be worth more than that.
I disagreed with everything Pete Carroll did today. Hell, I probably disagreed with what he had for breakfast.
Didn't want to spoil it by naming names, but, one guess which coach called this TO down 3 at the end of the 3rd quarter. But it was actually 2nd and 10 after re-checking the game log.
They also provide data like a 75% win probability if you kick a FG vs. 71% if you go for it on 4th and fail vs. 93% if if go for it and convert. Yet the anti-analytics folks yell and scream like mad when the coach goes for it....as if those numbers didn't ALREADY take into account shifts in momentum etc.That's the problem with analytics, they provide exact percentages for all scenarios as if they could possibly determine with any degree of confidence that a team has a 76% chance of converting a 3 & 3 with a pass and only 58% if they run. Those are nonsense stats. Saying they have a better chance passing vs running is far more intellectually honest (even if that statement may also be untrue).True but I still remember a time when NFL coaches would punt from the other teams 40 just to gain 20 yards in field position. The truth lies somewhere in the middle.They call him Stink for a reason.Then Schlereth is an idiotFormer player Mark Schlereth said it well this week: "Analytics is something stupid invented by math nerds who never played the game."
But he's not entirely wrong about analytics. It provides highly questionable numbers that people who don't truly understand them take as gospel truth.
GB, you're one of my favorite posters here, but you're really straw-manning with this stuff. Analytics don't "predict", they tell you what has happened historically in similar situations. Also, I don't recall ever seeing any kind of analytically based analysis arguing that a team should run or pass in a specific situation. How could you even make that argument, considering that there are a million different types of runs vs. passes?That's the problem with analytics, they provide exact percentages for all scenarios as if they could possibly determine with any degree of confidence that a team has a 76% chance of converting a 3 & 3 with a pass and only 58% if they run. Those are nonsense stats. Saying they have a better chance passing vs running is far more intellectually honest (even if that statement may also be untrue).True but I still remember a time when NFL coaches would punt from the other teams 40 just to gain 20 yards in field position. The truth lies somewhere in the middle.They call him Stink for a reason.Then Schlereth is an idiotFormer player Mark Schlereth said it well this week: "Analytics is something stupid invented by math nerds who never played the game."
But he's not entirely wrong about analytics. It provides highly questionable numbers that people who don't truly understand them take as gospel truth.
I appreciate that Ignatius, sincerely. But that's the problem with the data, what a conglomeration of other road teams did on 3rd & 3 from the opponents 43 yard line on the left hash mark, playing on Field Turf in a dome has almost zero predictive value for what a specific road team is doing on 3rd & 3 from the left hash mark on the opponents 43, playing on Field Turf in a dome.GB, you're one of my favorite posters here, but you're really straw-manning with this stuff. Analytics don't "predict", they tell you what has happened historically in similar situations.
The "data in" is still low quality relative to any specific situation it is being compared to so the "statistic out" has a very low degree of confidence. And that is before you even consider the algorithms that are used to parse this data.
Exactly. And people ONLY bash the analytics the times it doesn't work. It works more than it doesn't (I mean, by definition it does), but it seems every time it works there's never a "wow I wouldn't have done that if I was the coach, but he made a very smart decision". Probably my least fave thing about sports fandom is people blasting a decision after it doesn't work.They also provide data like a 75% win probability if you kick a FG vs. 71% if you go for it on 4th and fail vs. 93% if if go for it and convert. Yet the anti-analytics folks yell and scream like mad when the coach goes for it....as if those numbers didn't ALREADY take into account shifts in momentum etc.
MANY (most?) of those who rail against using data like this are simply anti-intellectuals who don't like math and tend put way too much faith in "gut feeling" and tradition. Again...he's an idiot
The biggest problem I have with this (constantly repeated) argument is that it's deeply flawed. Historical data that doesn't contain these "extra variable" by definition includes ALL the potential extra variables. Thus you over-emphasize the variable you feel argue against a decision while ignoring the fact that many of the events leading to the data set and "analytics solution" have already INCLUDED many scenarios that were similar variable wise.GB, you're one of my favorite posters here, but you're really straw-manning with this stuff. Analytics don't "predict", they tell you what has happened historically in similar situations.
The number of variables that exist between all of those specific scenarios combined and a single specific scenario happening in real time are legion. Lumping all of them together and spitting out a number is a fun exercise but it has little value beyond maybe providing a potential yes/no data point that helps you justify a decision to the media.
I think most reasonable poeple realize that the data sets are imperfect...but too many are inherently and obtusely reluctant to account for them at all.
The momentum thing is a GREAT example though. If looking at a specific decision and using analytics, you don't think momentum is already baked into it? It absolutely IS ALREADY BAKED IN!I think most reasonable poeple realize that the data sets are imperfect...but too many are inherently and obtusely reluctant to account for them at all.
I think that's what people like me are asking coaches and the elder statesmen in the game to do. To look or account for them at all. To the analytics guys, I'd ask the same thing I asked the SABR guys in baseball, which is maintain a bit of humility about what statistics can do predictively and what it can't account for.
Adam Harstad, who writes for FBG on theoretical dynasty matters, just tweeted about momentum the other day and said that just because you can't quantify it doesn't mean that it doesn't exist. You can't just wish it away. I forget his argument and the technical terms he was using, but I've always looked at it that this is a human game with human people participating in it. It is subject to limitations and conceits.
That's all I'd say about that. That sometimes analytics pretends to account for everything present in that iterative moment that you have to decide, and as Chaka points out, you might have historical data that accounts for certain things, but not for that specific time at that specific place in those specific circumstances. A human element is also something to take into account, not just a statistical model.
The "data in" is still low quality relative to any specific situation it is being compared to so the "statistic out" has a very low degree of confidence. And that is before you even consider the algorithms that are used to parse this data.
I've been saying this for years, but I think you've said it better than I ever have.
That said, moving the needle on some very basic stuff (like punting while you're fourth-and-short on the opposition's 43) was a huge boon to the NFL, and the NFL still hasn't listened to very basic stuff like that.
But I fully agree with your claim that you have to look at the inputs and how they're manipulated into a correlative value before you judge an analytic statistic.
Yep, I've been saying the same things for a long time as well. It's ironic to me how certain posters try to characterize anyone who disagrees with them as "anti-intellectual" or "math haters" when it couldn't be further from the truth. Many (most?) of us would love for the data to be higher quality and thus more valuable/predictive but are "intellectual enough" to understand that it simply isn't. The condescension is off-putting.I think most reasonable poeple realize that the data sets are imperfect...but too many are inherently and obtusely reluctant to account for them at all.
I think that's what people like me are asking coaches and the elder statesmen in the game to do. To look or account for them at all. To the analytics guys, I'd ask the same thing I asked the SABR guys in baseball, which is maintain a bit of humility about what statistics can do predictively and what it can't account for.
Adam Harstad, who writes for FBG on theoretical dynasty matters, just tweeted about momentum the other day and said that just because you can't quantify it doesn't mean that it doesn't exist. You can't just wish it away. I forget his argument and the technical terms he was using, but I've always looked at it that this is a human game with human people participating in it. It is subject to limitations and conceits.
That's all I'd say about that. That sometimes analytics pretends to account for everything present in that iterative moment that you have to decide, and as Chaka points out, you might have historical data that accounts for certain things, but not for that specific time at that specific place in those specific circumstances. A human element is also something to take into account, not just a statistical model.
FTR I am not supporting old-school thinking in my criticism. Just considering the flaws in analytic presentation to the public.The momentum thing is a GREAT example though. If looking at a specific decision and using analytics, you don't think momentum is already baked into it? It absolutely IS ALREADY BAKED IN!
In order to go 1-0 THIS WEEK, you have to be ahead after 60 minutes. You don't get to take an average result over 10 seasons. Emotion is important. Momentum is real. (Additionally, the loss of 3 is huge in close games because it invalidates future FGs and 2-pt conversions.)FTR I am not supporting old-school thinking in my criticism. Just considering the flaws in analytic presentation to the public.The momentum thing is a GREAT example though. If looking at a specific decision and using analytics, you don't think momentum is already baked into it? It absolutely IS ALREADY BAKED IN!
I believe the future of Analytics is bright. There will likely come a day when an AI is calling the plays for an NFL franchise. Or maybe running the whole show. It will be interesting to see competing AIs emerge and consider the possibility of why two different AIs draw different conclusions based upon the same data.
I am not sure who is the official keeper of the analytics thrown around during NFL broadcasts (AWS?) does anyone know if there is public access to their methodology?
How far back does their research go? Are we using Bart Starr as a comparative data point to Josh Allen? Bronko Nagurski to Christian McCaffrey? How does the algorithm handicap a play with Mitch Trubisky under center as opposed to Kyler Murray? Can we simply assume they've got it "figured out"?
To the point of "momentum". Any attempt to distill a concept like "momentum" into a quantifiable variable is inherently magical thinking.
Are all "momentums" equal? Do they have a way to measure "momentum"? Is my "momentum" bigger than yours?
I wasn't even considering "momentum" as one of the limitless variables involved in comparing two seemingly, but not actually, identical situations.
What about fatigue? Or the underlying injuries the 22 guys on the field are uniquely dealing with on any given play? How do those injury considerations change when it's 40 degrees on the field or 75 degrees? Is crowd noise factored in? Does that impact change in the Meadowlands vs Levi's stadium? What about when the Center's wife is dealing with a difficult pregnancy or when Giselle gets bored with Tom's shtick and their preparation is negatively impacted? Does the algorithm have data points to account for that?
The number of variables is staggering, even for super computers running advanced algorithms written by humans.
Ya and everyone is acting like 'going for it' based on analytics fails more than it succeeds. They talk about the 'missed 3 points' instead of the 'gained 7 points' or 'still 3 points but easier kick and more time off the clock". And the later happens more than the missing 3 points. People just like to claim that analytics 'don't work' when it fails, but NEVER glorify it near as much when it does.In order to go 1-0 THIS WEEK, you have to be ahead after 60 minutes. You don't get to take an average result over 10 seasons. Emotion is important. Momentum is real. (Additionally, the loss of 3 is huge in close games because it invalidates future FGs and 2-pt conversions.)FTR I am not supporting old-school thinking in my criticism. Just considering the flaws in analytic presentation to the public.The momentum thing is a GREAT example though. If looking at a specific decision and using analytics, you don't think momentum is already baked into it? It absolutely IS ALREADY BAKED IN!
I believe the future of Analytics is bright. There will likely come a day when an AI is calling the plays for an NFL franchise. Or maybe running the whole show. It will be interesting to see competing AIs emerge and consider the possibility of why two different AIs draw different conclusions based upon the same data.
I am not sure who is the official keeper of the analytics thrown around during NFL broadcasts (AWS?) does anyone know if there is public access to their methodology?
How far back does their research go? Are we using Bart Starr as a comparative data point to Josh Allen? Bronko Nagurski to Christian McCaffrey? How does the algorithm handicap a play with Mitch Trubisky under center as opposed to Kyler Murray? Can we simply assume they've got it "figured out"?
To the point of "momentum". Any attempt to distill a concept like "momentum" into a quantifiable variable is inherently magical thinking.
Are all "momentums" equal? Do they have a way to measure "momentum"? Is my "momentum" bigger than yours?
I wasn't even considering "momentum" as one of the limitless variables involved in comparing two seemingly, but not actually, identical situations.
What about fatigue? Or the underlying injuries the 22 guys on the field are uniquely dealing with on any given play? How do those injury considerations change when it's 40 degrees on the field or 75 degrees? Is crowd noise factored in? Does that impact change in the Meadowlands vs Levi's stadium? What about when the Center's wife is dealing with a difficult pregnancy or when Giselle gets bored with Tom's shtick and their preparation is negatively impacted? Does the algorithm have data points to account for that?
The number of variables is staggering, even for super computers running advanced algorithms written by humans.
It's loss aversion. We fixate on the downside because it causes more "pain" than the upside provides "pleasure".Ya and everyone is acting like 'going for it' based on analytics fails more than it succeeds. They talk about the 'missed 3 points' instead of the 'gained 7 points' or 'still 3 points but easier kick and more time off the clock". And the later happens more than the missing 3 points. People just like to claim that analytics 'don't work' when it fails, but NEVER glorify it near as much when it does.In order to go 1-0 THIS WEEK, you have to be ahead after 60 minutes. You don't get to take an average result over 10 seasons. Emotion is important. Momentum is real. (Additionally, the loss of 3 is huge in close games because it invalidates future FGs and 2-pt conversions.)FTR I am not supporting old-school thinking in my criticism. Just considering the flaws in analytic presentation to the public.The momentum thing is a GREAT example though. If looking at a specific decision and using analytics, you don't think momentum is already baked into it? It absolutely IS ALREADY BAKED IN!
I believe the future of Analytics is bright. There will likely come a day when an AI is calling the plays for an NFL franchise. Or maybe running the whole show. It will be interesting to see competing AIs emerge and consider the possibility of why two different AIs draw different conclusions based upon the same data.
I am not sure who is the official keeper of the analytics thrown around during NFL broadcasts (AWS?) does anyone know if there is public access to their methodology?
How far back does their research go? Are we using Bart Starr as a comparative data point to Josh Allen? Bronko Nagurski to Christian McCaffrey? How does the algorithm handicap a play with Mitch Trubisky under center as opposed to Kyler Murray? Can we simply assume they've got it "figured out"?
To the point of "momentum". Any attempt to distill a concept like "momentum" into a quantifiable variable is inherently magical thinking.
Are all "momentums" equal? Do they have a way to measure "momentum"? Is my "momentum" bigger than yours?
I wasn't even considering "momentum" as one of the limitless variables involved in comparing two seemingly, but not actually, identical situations.
What about fatigue? Or the underlying injuries the 22 guys on the field are uniquely dealing with on any given play? How do those injury considerations change when it's 40 degrees on the field or 75 degrees? Is crowd noise factored in? Does that impact change in the Meadowlands vs Levi's stadium? What about when the Center's wife is dealing with a difficult pregnancy or when Giselle gets bored with Tom's shtick and their preparation is negatively impacted? Does the algorithm have data points to account for that?
The number of variables is staggering, even for super computers running advanced algorithms written by humans.
Great stuff here. Loss aversion is definitely a real thing and blurs people's vision quite a bit. Like you say, going for it on 4th and getting the first down might give people a "nice that was great" vs missing it and this thread getting filled with posts. If there was a "post here when coaches do something you agree with" thread, it would clearly be much much smaller. People love to complain and they feel the emotion of the missed play or loss, much much more. So I can see how anti-analytics people are affected by that and inaccurately state that it was a bad decision, almost always AFTER the fact.It's loss aversion. We fixate on the downside because it causes more "pain" than the upside provides "pleasure".Ya and everyone is acting like 'going for it' based on analytics fails more than it succeeds. They talk about the 'missed 3 points' instead of the 'gained 7 points' or 'still 3 points but easier kick and more time off the clock". And the later happens more than the missing 3 points. People just like to claim that analytics 'don't work' when it fails, but NEVER glorify it near as much when it does.In order to go 1-0 THIS WEEK, you have to be ahead after 60 minutes. You don't get to take an average result over 10 seasons. Emotion is important. Momentum is real. (Additionally, the loss of 3 is huge in close games because it invalidates future FGs and 2-pt conversions.)FTR I am not supporting old-school thinking in my criticism. Just considering the flaws in analytic presentation to the public.The momentum thing is a GREAT example though. If looking at a specific decision and using analytics, you don't think momentum is already baked into it? It absolutely IS ALREADY BAKED IN!
I believe the future of Analytics is bright. There will likely come a day when an AI is calling the plays for an NFL franchise. Or maybe running the whole show. It will be interesting to see competing AIs emerge and consider the possibility of why two different AIs draw different conclusions based upon the same data.
I am not sure who is the official keeper of the analytics thrown around during NFL broadcasts (AWS?) does anyone know if there is public access to their methodology?
How far back does their research go? Are we using Bart Starr as a comparative data point to Josh Allen? Bronko Nagurski to Christian McCaffrey? How does the algorithm handicap a play with Mitch Trubisky under center as opposed to Kyler Murray? Can we simply assume they've got it "figured out"?
To the point of "momentum". Any attempt to distill a concept like "momentum" into a quantifiable variable is inherently magical thinking.
Are all "momentums" equal? Do they have a way to measure "momentum"? Is my "momentum" bigger than yours?
I wasn't even considering "momentum" as one of the limitless variables involved in comparing two seemingly, but not actually, identical situations.
What about fatigue? Or the underlying injuries the 22 guys on the field are uniquely dealing with on any given play? How do those injury considerations change when it's 40 degrees on the field or 75 degrees? Is crowd noise factored in? Does that impact change in the Meadowlands vs Levi's stadium? What about when the Center's wife is dealing with a difficult pregnancy or when Giselle gets bored with Tom's shtick and their preparation is negatively impacted? Does the algorithm have data points to account for that?
The number of variables is staggering, even for super computers running advanced algorithms written by humans.
It's also why I don't really buy the momentum arguments. It's not that I think momentum doesn't exist, it's just that its impact is a lot messier than people think, and it often gets deployed as a crutch argument. Take the example of "taking the points"; if scoring three points gives your team a psychological boost, it follows that scoring seven gives it an even bigger one. And if you have a 60% chance of converting the TD, you're more likely than not to get that boost. Note that I'm not citing momentum as a reason to go for it -- although I could imagine some scenarios where it might be, such as when a team caps off a furious 4th quarter comeback with a last second TD to draw within one -- just pointing out that it's never as neat as some people think, and that if you're using it in support of one action, it could just as easily be repurposed to argue for the opposite action
OK look bub, I'm going to take back every nice thing I've ever said about you if you put me in the position of defending NFL announcers. How dare you! HOW DARE YOU!!!!!I appreciate that Ignatius, sincerely. But that's the problem with the data, what a conglomeration of other road teams did on 3rd & 3 from the opponents 43 yard line on the left hash mark, playing on Field Turf in a dome has almost zero predictive value for what a specific road team is doing on 3rd & 3 from the left hash mark on the opponents 43, playing on Field Turf in a dome.GB, you're one of my favorite posters here, but you're really straw-manning with this stuff. Analytics don't "predict", they tell you what has happened historically in similar situations.
The number of variables that exist between all of those specific scenarios combined and a single specific scenario happening in real time are legion. Lumping all of them together and spitting out a number is a fun exercise but it has little value beyond maybe providing a potential yes/no data point that helps you justify a decision to the media.
And I have no problem with using that data, I dig deep every week trying to make dozens of WDIS decisions, but I fully recognize, and openly acknowledge that I am mostly making W.A.G.s
But too many people who don't truly understand how statistics works, and I'm referring to the announcers and talking heads not posters in here, look at the output stat and think "Oh, they had a 74% chance to accomplish X if they had just done Y, they're stupid for not having done X!!!" And that is simply not the case.
The "data in" is still low quality relative to any specific situation it is being compared to so the "statistic out" has a very low degree of confidence. And that is before you even consider the algorithms that are used to parse this data.
PhD in Human Genetics here, and even though I am far closer to Peter Venkman as a scientist than, say Milton Friedman, but I like to think I have a decent understanding of higher level statistics.
There is a future for analytics and I am absolutely on board with them in the future and now. But ATM the general football viewing audience gives them far too much weight.
I think this is the case many times that teams take a TO instead of just taking the 5 yd penalty. Time outs are very valuable. How valuable you won't know until you need them. Losing 5 yds on a 3rd and 7 from your 35 yd line in the 1st quarter really doesn't change things in the overall scheme of things. Just take the delay of game and keep the time out.After a long punt, it's now 3rd and 10 from your own 4, you're trailing in the 2nd half. QB can't get the play call in before the play clock expires... call the timeout to prevent the penalty of 2 yards? I think saving the timeout might be worth more than that.
Generally agree, though first-half TOs are far less valuable. I might call one in that situation in the first quarter but take the penalty in the thirdI think this is the case many times that teams take a TO instead of just taking the 5 yd penalty. Time outs are very valuable. How valuable you won't know until you need them. Losing 5 yds on a 3rd and 7 from your 35 yd line in the 1st quarter really doesn't change things in the overall scheme of things. Just take the delay of game and keep the time out.After a long punt, it's now 3rd and 10 from your own 4, you're trailing in the 2nd half. QB can't get the play call in before the play clock expires... call the timeout to prevent the penalty of 2 yards? I think saving the timeout might be worth more than that.
Don't get me wrong, there are times when a delay of game penalty could be big and worth using the time out. But I think there are many more cases throughout a season where the 5yd penalty really doesn't change the game at all.
I would actually love to read accounts of how different NFL teams use analytics to inform in-game decisions. Ever since I learned that teams aren't allowed to calculate WP% on the fly, I've assumed they have some general rules of thumb: "If it's 4th and X or less and the ball is on the Y yard line or closer ..." with the HC always having the discretion to do what he thinks is the best call. But I can't recall ever seeing it reported. Maybe it's considered a trade secret or something.Good discussion on analytics fellas - it’s a tool, a data point, which influences but (obviously) should not dictate.
I like the approach Dan Campbell and his OC Ben Johnson take. They have a lot of reports getting generated by lower level staffers, quality control, self-scouting reports, et al. Analytics is a huge part of developing game plans and red zone schemes. Johnson played QB as a walk on; his double major was mathematics and computer science. He’s obviously the kind of coach who embraces analytics.
In game, though, it’s more about context. They coach by feel. Analytics is a tool but it’s more important to have situational awareness.
MCDC has had some brain cramp moments (first Vikings game), but philosophically I like their concept.
The Bears just punted from the Eagles' 31-yard line.
With the score within 14 points, it's only the 3rd punt from the 31 and in since 2010.
The wind is bad and Santos had missed an XP from that direction. They were at 4th and 27 after a couple of sacks (4th and 32 after they took a delay of game penalty to give the punter more room.) Still a bad decision, though.Not watching the game but can someone explain how the hell this was allowed to happen?
The Bears just punted from the Eagles' 31-yard line.
With the score within 14 points, it's only the 3rd punt from the 31 and in since 2010.
So, the chargers. In a meaningless game. Had starters in.
Mike Williams carted off with a back injury & now being reported that Joey Bosa is hurt, too.
That all sounds pretty not smart to me. Maybe rest players if the week 18 game doesn’t count?
Agree to disagree.So, the chargers. In a meaningless game. Had starters in.
Mike Williams carted off with a back injury & now being reported that Joey Bosa is hurt, too.
That all sounds pretty not smart to me. Maybe rest players if the week 18 game doesn’t count?
Williams' injury has been reported as back spasms. Assuming that is true, he should be fine and will play in the wild card game. Bosa did not suffer a new injury or reaggravate a previous injury. As far as I know, no others were injured.
I think sometimes people overlook the reality of fielding a team for a game. The fewest players the Chargers played on offense this season in any of the first 16 games is 17. The fewest on defense is 16. They have 3 special teams specialists who don't overlap on offense defense (LS, PK, P) and 3+ players who play special teams and do not play on offense or defense, even though they are listed with an offensive/defensive position (they play on coverage and return teams).
That is 39 players at a minimum. The team only has 46-48 players active on gameday, depending on whether they activate 0-2 players from the practice squad. Today, they activated the max number (2) and had 48 active players. The Chargers absolutely should have held out or limited the snaps for any player dealing with a current injury, and they did that -- SCB Callahan was inactive because he is dealing with a current injury. Otherwise, they should have shifted more snaps to the depth players in the various rotations, and they did that in the second half. If there is any valid criticism, it is that they should have done that sooner.
Meanwhile, it was appropriate for the offense to try to build on its good game last week, its first good game in weeks, and build some momentum entering the playoffs. And on defense, both Bosa and James needed game reps with the starting defense to re-integrate and be ready for the playoffs; they got them and exited the game in the 2nd and 3rd quarters, respectively.
I did think it was a slightly closer call given that the Lions were up 4. If the lead is 3, it's a no-brainer.Coaches that go for it on 4th down to win the game?
Hell yeah
I did think it was a slightly closer call given that the Lions were up 4. If the lead is 3, it's a no-brainer.Coaches that go for it on 4th down to win the game?
Hell yeah
But overall, this is a point I've hit repeatedly in this thread: Don't give the ball back to HOF QBs with a chance for them to win the game! Get one yard and put them away.
Plus it’s not an automatic that if they don’t get it they lose.I did think it was a slightly closer call given that the Lions were up 4. If the lead is 3, it's a no-brainer.Coaches that go for it on 4th down to win the game?
Hell yeah
But overall, this is a point I've hit repeatedly in this thread: Don't give the ball back to HOF QBs with a chance for them to win the game! Get one yard and put them away.
the discussion we were having is why not
kick FG they can still tie/win the game
make it & it’s over
didn’t come all this way to play it safe
no hesitation from the sidelines