Papa Schnay
Footballguy
I'm wondering how much longer I'll be alive in this thing with both AP and Ray Rice stinking the joint up all year long. 4 weeks in, and still kicking somehow. lol.
Ummm…you cleared the cut line by about 50.http://o.ffense.com/fbg35k/index.php?teamid=106070Benjamin is like having 2 or 3 guys. Post your team link. 120 is probably a safe number this week assuming a high ownership guy doesn't go Julio.Now I did. Just missing too many guys via Bye week and injury.You didn't select Kelvin Benjamin?I have little chance this week.
Drew Brees $26 19.85 19.15 22.45 24.60 bye Geno Smith $7 17.85 20.40 19.80 13.85 bye ---------------------------------------------------------------------------------------------------------------------------------------------Eddie Lacy $28 7.50 8.10 5.50 12.90 bye Doug Martin $24 2.60 0.00 0.00 13.60 out? bye Dexter McCluster $7 5.60 4.90 3.50 0.10 bye Travaris Cadet $3 1.50 0.00 0.90 12.00 bye ---------------------------------------------------------------------------------------------------------------------------------------------Jordy Nelson $25 17.30 35.90 10.90 32.80 bye Emmanuel Sanders $18 14.80 18.60 25.90 0.00 Eric Decker $15 12.40 16.30 2.90 14.80 bye Greg Jennings $9 17.80 1.40 12.00 10.20 bye Miles Austin $8 4.00 16.40 17.10 0.00 ---------------------------------------------------------------------------------------------------------------------------------------------Julius Thomas $26 38.90 15.90 12.20 0.00 Jordan Cameron $22 7.70 0.00 3.80 0.00 Jason Witten $18 4.40 9.20 10.90 13.60 bye ---------------------------------------------------------------------------------------------------------------------------------------------Mason Crosby $4 4.00 13.60 1.00 10.30 bye Sebastian Janikowski $3 2.00 2.00 13.30 2.00 bye ---------------------------------------------------------------------------------------------------------------------------------------------Baltimore Ravens $4 0.00 8.00 1.00 4.00 bye Pittsburgh Steelers $3 3.00 0.00 13.00 3.00 bye ---------------------------------------------------------------------------------------------------------------------------------------------TOTAL 141.15 158.10 135.85 148.80 CUTOFF 138.15 140.20 134.65 137.60
seems to be a common themebicycle_seat_sniffer said:still hovering in the 170s
Have to say with the current RB landscape this is going to be interesting
to the contest..
There's the question of Jeremy Maclin. FBG is crediting him with 11.8, and the box score at Football Reference agrees: 5 catches, 68 yards. But at NFL.com, the Game Center says 4 catches for 57 yards, and the weekly NFL.com stats page agrees. That would be 9.7.Ignoratio Elenchi said:The only discrepancy in numbers I'm seeing is that you don't credit (well, debit) Roethlisberger for his -6 receiving yards (from the lateral play). QBs don't get ppr, but according to the rules, they should get receiving yards. Of course, he didn't have the reception on that play. It makes only a 0.05 change in the cut line, but of course it moves teams around at the margins.![]()
You nailed it. Looks like FBG accounted for Roethlisberger's -6 receiving yards in the official results. That was the only discrepancy in the results. I updated my site accordingly and everything on my site (queriers, ownership stats, team pages, etc.) should now be updated through Week 4. Let me know if anything looks off.
Yahoo is showing a stat correction moving the 11 yards from Maclin to Brad Smith.There's the question of Jeremy Maclin. FBG is crediting him with 11.8, and the box score at Football Reference agrees: 5 catches, 68 yards. But at NFL.com, the Game Center says 4 catches for 57 yards, and the weekly NFL.com stats page agrees. That would be 9.7.Ignoratio Elenchi said:The only discrepancy in numbers I'm seeing is that you don't credit (well, debit) Roethlisberger for his -6 receiving yards (from the lateral play). QBs don't get ppr, but according to the rules, they should get receiving yards. Of course, he didn't have the reception on that play. It makes only a 0.05 change in the cut line, but of course it moves teams around at the margins.![]()
You nailed it. Looks like FBG accounted for Roethlisberger's -6 receiving yards in the official results. That was the only discrepancy in the results. I updated my site accordingly and everything on my site (queriers, ownership stats, team pages, etc.) should now be updated through Week 4. Let me know if anything looks off.
Per the contest rules:Yahoo is showing a stat correction moving the 11 yards from Maclin to Brad Smith.There's the question of Jeremy Maclin. FBG is crediting him with 11.8, and the box score at Football Reference agrees: 5 catches, 68 yards. But at NFL.com, the Game Center says 4 catches for 57 yards, and the weekly NFL.com stats page agrees. That would be 9.7.Ignoratio Elenchi said:The only discrepancy in numbers I'm seeing is that you don't credit (well, debit) Roethlisberger for his -6 receiving yards (from the lateral play). QBs don't get ppr, but according to the rules, they should get receiving yards. Of course, he didn't have the reception on that play. It makes only a 0.05 change in the cut line, but of course it moves teams around at the margins.![]()
You nailed it. Looks like FBG accounted for Roethlisberger's -6 receiving yards in the official results. That was the only discrepancy in the results. I updated my site accordingly and everything on my site (queriers, ownership stats, team pages, etc.) should now be updated through Week 4. Let me know if anything looks off.
So if there was a stat correction, Drinen may update the results. My site won't automatically do this (I stop running the scoring script after MNF) but maybe going forward I'll run an update on Thursday morning to make sure that my results remain aligned with the official results, in the event that FBG makes any updates.All scoring is determined final at 11:59pm on Tuesday regardless if the NFL later changes the data. Preliminary weekly results will be published on Tuesday morning following the completion of all games.
All stat changes made by the league prior to 11:59 pm Tuesday will be incorporated into the contest scoring and standings reflecting these changes will be posted on Wednesday morning. Users have until 5:00 p.m. Eastern time on Wednesday to report possible scoring errors to drinen@footballguys.com. The standings posted on Thursday morning are considered official, even if an error (by the league, by footballguys, or by anyone or anything else) is later discovered.
Hey Iggy, maybe an interesting metric will be how many points that counted each player scored.Random trivia:
Demarco Murray and Martellus Bennett are the only two players who have counted every single week for every single entry that owns them.
Antonio Brown comes in at 99.9% - there were 16 entries that didn't use his 17 points in week 2.
I don't think this is exactly what you're asking for, but I added a few columns of output to the 2014 player querier: http://o.ffense.com/fbg35k/currquerier/index.phpHey Iggy, maybe an interesting metric will be how many points that counted each player scored.(e.g. points times number of teams that used him)Random trivia:
Demarco Murray and Martellus Bennett are the only two players who have counted every single week for every single entry that owns them.
Antonio Brown comes in at 99.9% - there were 16 entries that didn't use his 17 points in week 2.
-QG
I haven't done exactly the calculation you propose, but I think you'll find that Kelvin Benjamin owns the per $ category. A little harder to gauge the other one, but either Antonio Brown or Jay Cutler look like the most likely contenders.QB
Jake Locker $7 22.70 1042 439Thanks Iggy, yeah using the example above 439 people actually used Jake Locker and he got 22.70
So his impact on the contest was 9,965.3
His per $ impact on the conest was 1,423.61 for this week
At some point I'll try to sift through this all and maybe we can get an MVP (both total and per $)![]()
-QG
Yeah, best score of the year. Better to be lucky than smart.Ummm…you cleared the cut line by about 50.http://o.ffense.com/fbg35k/index.php?teamid=106070Benjamin is like having 2 or 3 guys. Post your team link. 120 is probably a safe number this week assuming a high ownership guy doesn't go Julio.Now I did. Just missing too many guys via Bye week and injury.You didn't select Kelvin Benjamin?I have little chance this week.
Fixed to reflect proper reverence to 15-Kicker GuyA little busy this week.
Awards and notable teams of the week. Note that these awards are based on the NFL's Jeremy Maclin correction, which isn't reflected in the FBG report yet.
Strongest Living Team: Still RHON, Entry 100300, averaging over 209 points per week.
Strongest Dead Team: HRNSUP, Entry 102779, averaging 189 per week, in 258th place overall.
Keep Your Day Job Award: Still Entry 100869, with an average score of 78.5, almost 5 points below the next-worst team.
Safest Team: For the third week in a row, AdamAfrica, Entry 102306, never less than 64.2 above the cut line.
Just Skating By Award: Entry 104004, in their best week, cleared the cut line by 6.55 points. H Man, the previous champion here, was eliminated this week.
Icarus Award: Lavender Fleas, Entry 106325, averaged over 200 points per week through the first three weeks, sitting 15th overall. Lavender Fleas is now dead.
Woulda Coulda Shoulda Award: Entry 105026 was eliminated in Week 1 but has averaged 189 since then.
Notable Teams:
QBs: Big Shuffy, Entry 113318, is still hanging in there with 10 QBs.
RBs: We lost another 12-RB team. Three of the original six are still around.
WRs: Same as last week: two 13-WR teams remain, The Dogs of War (Entry 107531) and Entry 102255.
TEs: Same as last week: three teams with 7 TEs survive.
PKs: Same as last week: 15-Kicker Guy survives.![]()
![]()
![]()
![]()
DEFs: We're down to one team with 8 defenses, Entry 113411.
And me, you ask? With a strong week, I moved up over 700 places and am currently sitting in 1315th among living teams.
More to come later...
Iggy, Not to steal jdkapow's thunder, but any way you could add a cumulative team score page for overall standings (or am I missing it)?I don't think this is exactly what you're asking for, but I added a few columns of output to the 2014 player querier: http://o.ffense.com/fbg35k/currquerier/index.phpHey Iggy, maybe an interesting metric will be how many points that counted each player scored.(e.g. points times number of teams that used him)Random trivia:
Demarco Murray and Martellus Bennett are the only two players who have counted every single week for every single entry that owns them.
Antonio Brown comes in at 99.9% - there were 16 entries that didn't use his 17 points in week 2.
-QG
Where it says "Show all player stats for week..." if you pick a week and submit, you'll now see all the players in the contest, their score for that week, how many teams entered the week with that player, how many teams started that player, and how many teams with that player were eliminated that week.
So you could grab that data for any week and do (points scored) x (# or % started) or whatever it is you'd like to see.
I've added a page with the top 500 overall cumulative scores for the season here: http://o.ffense.com/fbg35k/overall.phpIggy, Not to steal jdkapow's thunder, but any way you could add a cumulative team score page for overall standings (or am I missing it)?
Thanks!Ignoratio Elenchi said:I've added a page with the top 500 overall cumulative scores for the season here: http://o.ffense.com/fbg35k/overall.phpapalmer said:Iggy, Not to steal jdkapow's thunder, but any way you could add a cumulative team score page for overall standings (or am I missing it)?
This is something I'd like to add, and it would (theoretically) be as simple as re-running the current cutoff calculation but replacing the live stats with final projected stats. I would probably just update it every 15 minutes or so and only during SNF and MNF just to keep things simpler. I think this would involve:I think a "Cut Line Projector" might be a viable item.
Thoughts on methodology?
I don't think you need to over-complicate it. Simply take (real points scored) + (projected points) * (percentage of game remaining).
- While there's a game going on it's more complicated, because I'd need to come up with some hybrid of actual and projected stats. For example, if Dodds has Calvin Johnson projected to score 16 points, and he already has 20 points at halftime, it makes no sense to use either the projected stats or the actual stats. I'd need to revise the projections on the fly based on what's already happened and how much time is left in the game (this is another complication, since this is something else I don't currently pull in). And whatever I came up with would be pretty unscientific - if Calvin was projected for 16, and has 20 at halftime, what do I project his final points to be? 25? 32? 40? If Calvin was projected for 16 and has 0 at halftime, what do I project his final points to be? 0? 8? 16? (This is another issue - if a player gets hurt during the game and won't return, I don't think I'd have any way to account for this on the fly).
). I like the simpler idea of calculating the projected cut line before the Sunday night game and again before the Monday night game using projections for the games that haven't completed yet.Right, that's exactly the kind of calculation I'd end up doing. The nerd in me would prefer a more precise way to do it but this is simple and close enough for our purposes.I don't think you need to over-complicate it. Simply take (real points scored) + (projected points) * (percentage of game remaining).
- While there's a game going on it's more complicated, because I'd need to come up with some hybrid of actual and projected stats. For example, if Dodds has Calvin Johnson projected to score 16 points, and he already has 20 points at halftime, it makes no sense to use either the projected stats or the actual stats. I'd need to revise the projections on the fly based on what's already happened and how much time is left in the game (this is another complication, since this is something else I don't currently pull in). And whatever I came up with would be pretty unscientific - if Calvin was projected for 16, and has 20 at halftime, what do I project his final points to be? 25? 32? 40? If Calvin was projected for 16 and has 0 at halftime, what do I project his final points to be? 0? 8? 16? (This is another issue - if a player gets hurt during the game and won't return, I don't think I'd have any way to account for this on the fly).
If Dodds projects 16 and Calvin Johnson has 20 at half: (20) + (16) * (.5) = projected 28
If Dodds projects 16 and Calvin Johnson has 0 at half: (0) + (16) * (.5) = projected 8
If Dodds projects 16 and Calvin Johnson has 20 at 0:00 Q3: (20) + 16 * (.25) = projected 24
I wouldn't worry about hurt players or overtime potential. Just base the time remaining on 60 minute games. If Q1, there are (45 + min_remaining_in_quarter)/(60.0) left in the game.
This is much easier, but less fun. I'm not sure yet which one I feel more strongly about.I think the projected cut line calculation during the game is overkill (although a fun problem to figure out). I like the simpler idea of calculating the projected cut line before the Sunday night game and again before the Monday night game using projections for the games that haven't completed yet.
I believe the best pts/$ performer to date at each skill position are:I haven't done exactly the calculation you propose, but I think you'll find that Kelvin Benjamin owns the per $ category. A little harder to gauge the other one, but either Antonio Brown or Jay Cutler look like the most likely contenders.QB
Jake Locker $7 22.70 1042 439Thanks Iggy, yeah using the example above 439 people actually used Jake Locker and he got 22.70
So his impact on the contest was 9,965.3
His per $ impact on the conest was 1,423.61 for this week
At some point I'll try to sift through this all and maybe we can get an MVP (both total and per $)![]()
-QG
But you could also think of the MVP as that guy that gives his teams the biggest boost relative to the cut line. This would be a huge performer owned on very few teams, who therefore get the most out of every point he scores. I think you'll find that those guys are Delanie Walker (overall) and Matt Asiata (per dollar).
Well, you can tell I went for the 'easier' approach. Loading projections sounds like a lot of work for very little benefit, since projections themselves are also a crapshoot.This is much easier, but less fun. I'm not sure yet which one I feel more strongly about.I think the projected cut line calculation during the game is overkill (although a fun problem to figure out). I like the simpler idea of calculating the projected cut line before the Sunday night game and again before the Monday night game using projections for the games that haven't completed yet.
![]()