Jump to content
  • Welcome!

    Register and log in easily with Twitter or Google accounts!

    Or simply create a new Huddle account. 

    Members receive fewer ads , access our dark theme, and the ability to join the discussion!

     

The "L" is mostly on First Half Baker


Khaki Lackey
 Share

Recommended Posts

1 minute ago, PantherGuy said:

I see your reasoning, but the run defense was bad from the first snap.

I agree, but we know the run D is a liability and the TOP really exaggerated it. The second half showed me that when the QB play wasn't awful (and Elflein is partially to blame also for all the bad snaps) that the run game improved and the run D improved too. (usually teams that are bad against the run wear out and get worse as the game goes on, whereas we actually got better.)

Link to comment
Share on other sites

The Huddle: "We lost the game because of Baker, no Matt Rhule was at fault, no Ben MacAdoo was at fault, no the run defense was at fault, no the O-line was at fault, no Ikem was at fault, no Dave Tepper's wife was at fault, no Sir Purr was at fault, no Darin Gantt was at fault, no Mike Craft was at fault, fire everyone" !!! 

  • Beer 1
Link to comment
Share on other sites

16 minutes ago, Khaki Lackey said:

Do you know what the time of possession was in the first versus second halves?

16min (1st half) and 22min (2nd half) roughly. Our 3 scoring drives in the 2nd half were an accumulative total of almost 6min... which is eye opening.

Edited by TheCasillas
  • Pie 1
Link to comment
Share on other sites

4 minutes ago, TheSpecialJuan said:

The Huddle: "We lost the game because of Baker, no Matt Rhule was at fault, no Ben MacAdoo was at fault, no the run defense was at fault, no the O-line was at fault, no Ikem was at fault, no Dave Tepper's wife was at fault, no Sir Purr was at fault, no Darin Gantt was at fault, no Mike Craft was at fault, fire everyone" !!! 

The Huddle:

75% - Its Matt Rhule

16% - I'm really trying hard here to hold out hope

9% - why are these clowns messing things up for Matt Rhule!  What did you expect? Rattles off a list of excuses longer than Matt Rhule himself would. 

  • Pie 1
  • The D 1
Link to comment
Share on other sites

12 minutes ago, TheCasillas said:

Are you asking me if it is the QB's fault for throwing a pick? It appears to me that Baker had a clear pocket and a wide open Shi. image.thumb.png.816c2f8fb2c6390fc0212e179f10b597.png

image.thumb.png.cf8a54785535899ee513e90420996f8c.png

There is literally a guy #20 coming at him unblocked as he is having to rush that throw...  This is how TOs happen all the time.  QBs get uncomfortable because they are constantly getting hit that they rush throws.  After how he looked in that one picture, I'm surprised he was still standing and comfortable enough to get us the lead in the 4th.   Again if we had a different game plan and slowed down their pass rush there is a MUCH higher chance he hangs in there and makes that throw (like he did in the second half).  

Link to comment
Share on other sites

4 minutes ago, ForJimmy said:

There is literally a guy #20 coming at him unblocked as he is having to rush that throw...  This is how TOs happen all the time.  QBs get uncomfortable because they are constantly getting hit that they rush throws.  After how he looked in that one picture, I'm surprised he was still standing and comfortable enough to get us the lead in the 4th.   Again if we had a different game plan and slowed down their pass rush there is a MUCH higher chance he hangs in there and makes that throw (like he did in the second half).  

It was a 5 man blitz, not a four man pass rush. This was our third drive and Baker had only been sacked once at this point in the game. The player was 4 yards away when Baker began to throw the ball. If you watched the video you'd probably lean less into him being rush to throw. The player doesnt even touch Baker. 

 

It was a bad throw by Baker. He is to blame. He had 3 options open on that play. 

Edited by TheCasillas
Link to comment
Share on other sites

4 minutes ago, CRA said:

The Huddle:

75% - Its Matt Rhule

16% - I'm really trying hard here to hold out hope

9% - why are these clowns messing things up for Matt Rhule!  What did you expect? Rattles off a list of excuses longer than Matt Rhule himself would. 

Nah that's just you seeing what you want to see. Rhule's done planty to make this team bad, but I've never seen bad QB play overlooked as much as it was on Sunday.

I guess Darnold is a hall of fame talent that's just being held back from Matt Rhule. Or did we actually blame the QB for bad play last year?

Link to comment
Share on other sites

4 minutes ago, ForJimmy said:

There is literally a guy #20 coming at him unblocked as he is having to rush that throw...  This is how TOs happen all the time.  QBs get uncomfortable because they are constantly getting hit that they rush throws.  After how he looked in that one picture, I'm surprised he was still standing and comfortable enough to get us the lead in the 4th.   Again if we had a different game plan and slowed down their pass rush there is a MUCH higher chance he hangs in there and makes that throw (like he did in the second half).  

If picks are the coaches fault, I guess Sam Darnold is a really good QB. Why is he not starting?

Link to comment
Share on other sites

2 minutes ago, ForJimmy said:

I was thinking that too, but I don't think he gets to his second look and makes a good throw before #20 hits him.

#20 never hits him though. I really wish I could screen record this so you can see it. Baker knows where he is going with the ball before the blitz is within 3-4 yards of him. 

Link to comment
Share on other sites

OP is 100% correct. Our biggest problem was 1st half Baker. There were other problems, but if Baker did more than go 3 and out for practically a full 30 minutes, the outcome of this game would have been much different.

All the other problems combined, including the defense and the coaching, would not have lost us the game if Baker was competent in the first half. Even just one more drive.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share


  • PMH4OWPW7JD2TDGWZKTOYL2T3E.jpg

  • Topics

  • Posts

    • You may be interested to know that the average depth of separation is dependent upon the type of route run. Though go-routes are the most type of route run, they also produce the least amount of separation (and, of course, completions).   "The average pass catcher runs a go route on nearly a quarter of all routes (22.3%), the highest percentage of any route type in our data. However, those routes are targeted roughly 1 out of 10 times (10.8 percent), the lowest target rate of any route. The WR screen is the least-run route (3.4%), and it's the only route where the average target is behind the line of scrimmage. But it's also targeted at the highest rate (40.7%) and early in the play (1.6 seconds average time to throw). The most targeted routes outside of the WR Screen? The out (27.8%) and slant (25.2%) routes are the next most popular across the league."     "The most valuable routes by expected points added per target were the post (+0.48) and corner (+0.43) routes. The go route (+0.19) ranked seventh on the list of 10 route types. The go route (+0.19) ranked seventh on the list of 10 route types. One possible reason for this: It's harder to separate on go routes, which put the player on a straight path, than on posts or corners, which ask the player to make a cut. Targeted pass catchers on posts and corners average 2.4 yards and 2.3 yards of separation from the nearest defender, respectively, while pass catchers targeted on go routes average just 1.8 yards of separation."   https://www.nfl.com/news/next-gen-stats-intro-to-new-route-recognition-model#:~:text=Targeted pass catchers on posts,) and slant (+0.26).   I would expect that Thielen would have an easier time catching the ball based that he runs the routes where it's easier to get open. Tet? Yet to be seen, but we may be better served getting him on some slants and crossers also.  In general, receivers are going to average a lower completion percentage and yards of separation on certain types of routes than others, that's why we shouldn't necessarily be taking stats, even advanced ones, at face value, as there are dynamics that most aren't even thinking about.  In terms of Tet, he's bigger and somewhat slower than a smaller dude, so you'd expect him not to have as much separation on go-routes, but his catch radius is massive and his hands are awesome. Hitting him in stride will probably be killer, but of course QBs are less accurate on go-routes according to the stats. Depending upon Tet's route versatility and how he is used, we could have a unicorn though. He's relatively fast, has great hands and gets YAC (and on an off note, if X can hold on to the ball, he's dangerous as well because he already has shown some separation ability).    
    • Most elite WRs aren't necessarily burners. Not a lot of elite WRs in the modern era were 4.3 guys. If anything, sometimes it seems like the super fast guys use their speed as a crutch and it hampers their development in the intricacies of route running.
×
×
  • Create New...