• How To
    • Win Your DFS League
    • Win Your Auction Draft
    • Win Your Snake Draft
    • Download Projections
    • Scrape Projections
    • Calculate Projections for Your League
    • Examine Accuracy of Projections
    • Identify Sleepers
    • Save Custom Settings
    • Use the API
  • Strategy
    • Fantasy Football is Like Stock Picking
    • Use Projections, Not Rankings
  • Projections
    • Our Projections
    • Who has the Best Projections?
    • Draft the Best Starting Lineup
    • Projections are More Accurate than Rankings
    • Points by Position Rank
    • Players’ Risk Levels
    • Value Over Replacement
    • Bid-Up-To Value
    • Player Value Gap
    • Gold Mining
    • Weekly Variability
    • Are Subscription Sources More Accurate?
  • Statistics
    • How To Learn R
    • R is Better than Excel
    • Do Stats Help in Fantasy Football?
    • Download/Run Our Scripts
    • ffanalytics R Package
  • Apps
    • Auction Draft Optimizer
    • Snake Draft Optimizer
    • Weekly Lineup Optimizer
    • Rankings/Projections for Your League
    • API
    • Other Tools
      • Stock Analysis
    • Error Logging
  • Testimonials
  • About the Site
    • About
    • Authors
      • Isaac Petersen
    • FAQ
    • FFA Insider
    • Privacy Policy
    • Terms of Service
  • Donate

Fantasy Football Analytics

Win Your Daily Fantasy (DFS) League with this Lineup Optimizer

125
  • by Isaac Petersen
  • in FFA Insider · R · Tools · Weekly
  • — 5 Sep, 2016

In this post, we use a Shiny app in R to determine the best possible players to pick in a daily/weekly fantasy football (DFS) league.  The app includes the most accurate fantasy football projections available, and calculates a robust average of more sources of projections than any other website (see here for a list of the sources of projections).  You can even choose how much weight to give each source.  Based on your league settings, it determines which players you should pick to maximize your starting lineup’s projected points.  It also allows you to change your risk tolerance to avoid picking risky players.  Best of all, the app updates the selections automatically with your inputs, and you can download the data for yourself.  So let’s get to it.  Here’s a more thorough description:

To Use the DFS Optimizer App

To use the DFS Optimizer App, you will need to subscribe to FFA Insider (for more info, see here).

How it Works

First, we use a script to scrape player’s projected points from numerous sources using R.  Second, we scrape player prices from various DFS websites.  Third, based on the user’s league scoring settings, we calculate players’ projections using an average of the analysts’ projections (by default, the sources are weighted according to historical accuracy).  You can choose which projection sources to include, modify the weights, and choose to calculate a mean, weighted average, or robust average.  A robust average is less affected by outliers (crazy projections).  Fourth, we calculate players’ risk levels, as defined by the average of: 1) injury risk from Sports Injury Predictor, and 2) the standard deviation of the players’ projected points and rankings across analysts.  Note that risk is standardized to have a mean of 5 and a standard deviation of 2.

Then, based on how many players you need for each position, your cap available, and your maximum risk tolerance, we use the Rglpk package to find your optimal lineup by selecting the remaining players available that maximize the lineup’s sum of projected points while meeting all of the constraints.  For a similar execution using Excel’s Solver function, see here.

We also display the “dropoff” in projected points for the next best 2 players at the same position.  For more info on how projected cost is calculated, see here.

It is generally best to select players with minimal risk to ensure solid, if not superior, performance.  We include players’ upside potential (ceiling) in the output, as defined by the players’ 90th percentile of their projected points across analysts.

Note that VOR, ADP, ECR, and AAV are not shown for weekly projections (only seasonal projections).

Strategy

Strategy to win your DFS league: pick the players with the highest sum of projected points (especially floor), while minimizing risk (i.e., a low risk and a high floor).

User Inputs

Season: which season of projections to use.
Week: which week(s) of projections to use.
Number of Starters by Position: how many players in your starting lineup at each position.
League Scoring: source of DFS scoring settings.
Positions: which positions of players to include in calculations.
Calculation Type: the type of average to calculate: mean, weighted average, or robust average.  By default, a weighted average is used with analysts weighted by their historical accuracy.  You can modify the weights in the weighted average.  The mean is equivalent to a weighted average where all analysts are equally weighted (weight = 1).  The robust average gives less weight to outliers (crazy projections).
Analysts: Select which analysts to include and, if weighted average, the weights for each analyst (i.e., how much weight to give each source of projections when calculating projected points).  For instance, if you want to exclude ESPN projections, you would give them a weight of 0. If you want to give Yahoo projections twice the weight of CBS, you would give Yahoo a weight of 2 and CBS a weight of 1.  The default weights reflect historical accuracy (higher = more accurate).  Note that FantasyPros shows a default weight of zero because we already include all of their sources in our projections, so it would be double counting to give them a weight above 0.  You can certainly do so, though, if you’d like.  FantasyFootballNerd also shows a default weight of zero because it uses the same projections as FantasyData.
Scoring Settings: specify the number of points for each statistical category and position.

Sidebar

Maximum Risk Tolerance: Selects the maximum risk allowed for any player to be considered for inclusion in the optimal starting lineup. Players’ risk levels have a mean of 5 and a standard deviation of 2 (see below for more info on how risk is calculated).
Remaining Cap for Starters: How much cap you have remaining to spend on starters.
Players You Drafted:  Select all players you’ve already picked (click “Pick” button next to player or type player’s name).
Other Players Drafted: Select players to exclude.

Output

Lineup with Highest Points: Players with highest sum of projected points within your league cap and risk tolerance.
Lineup with Highest Floor: Players with highest sum of projected floor within your league cap and risk tolerance.
Lineup with Highest Ceiling: Players with highest sum of projected ceiling within your league cap and risk tolerance.
Pick: Click “Pick” button next to player to add to “Players You Drafted”.
Rank: Overall rank by projected points.
Player (Team): Player name and team. Click player’s name to add to “Other Players Drafted”.
Pos: Position.
Points: Average projected points for a player across analysts.
Ceiling: A player’s upside, calculated as the 90th percentile of a player’s projected points across analysts.
Floor: A player’s downside, calculated as the 10th percentile of a player’s projected points across analysts.
Pos Rank: Position rank.
Dropoff: The “dropoff” in projected points for the next best 2 players at the same position.
Risk: Risk of injury and degree of uncertainty of players’ projected points, calculated as the average of: 1) injury risk from Sports Injury Predictor, and 2) the standard deviation of the players’ projected points and rankings across analysts. Standardized within position to have a mean of 5 and a standard deviation of 2 (higher values reflect greater risk).

Graph

Displays two types of graphs:

  1. A density plot of projected points by analyst
  2. Line plot of each optimal starting lineup by projected points, floor, and ceiling

A density plot shows, for each analyst, what proportion of players are projected to score a given number of points. Density plots can be helpful for comparing analysts and finding analysts with wildly different projections.   In the line plots, the dot represents the average (mean, weighted average, or robust average) estimate of projected points for each player.  The line shows the range from a player’s floor to ceiling.

The DFS Optimizer App

For the DFS Optimizer app, go to:

http://apps.fantasyfootballanalytics.net

DFS Lineup

Share this:

  • Click to share on X (Opens in new window) X
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to email a link to a friend (Opens in new window) Email

Like this:

Like Loading...

Related

Share

Tags: DFSRtoolsweekly

— Isaac Petersen

My name is Isaac and I'm an assistant professor with a Ph.D. in Clinical Psychology. Why am I writing about fantasy football and data analysis? Because fantasy football involves the intersection of two things I love: sports and statistics. With this site, I hope to demonstrate the relevance of statistics for choosing the best team in fantasy football.

125 Comments

  1. Chris says:
    September 5, 2016 at 11:23 pm

    Isaac, it seems there is an issue with the Fanduel Lineup Optimizer. It begins generating the lineup then kicks you back to the default screen without giving you the results.

    Reply
    • Isaac Petersen says:
      September 5, 2016 at 11:26 pm

      Works for me. Are you logged in as an FFA Insider subscriber? You might try disabling your ad blockers, deleting your cache, and/or trying a different browser.

      Reply
  2. Chris says:
    September 5, 2016 at 11:39 pm

    I’m logged in, have disabled popup blocker and deleted cache and still cannot get it to work for me. Which browser are you using?

    Reply
    • Isaac Petersen says:
      September 5, 2016 at 11:48 pm

      You might try signing out and signing back in. Works for me on Chrome.

      Reply
    • Chris says:
      September 5, 2016 at 11:49 pm

      It did not work in Explore or Firefox, but it seems to work just fine in Chrome! Look forward to using this information.

      Reply
  3. Huey (@hueykwik) says:
    September 6, 2016 at 1:33 am

    Isaac, can you tell us which DFS sites you support? Before putting in some money, I’d like to know if you support lineup optimizers for the following sites: Yahoo, DraftKings, FantasyAces, FantasyDraft, Draftpot. Thanks!

    Reply
    • Val Pinskiy says:
      September 6, 2016 at 8:56 am

      We currently support Fanduel, DraftKings, Yahoo, FantasyAces, DraftDay, FantasyScore, and StarsDraft. We have also historically supported DraftPot and FantasyFeud but they did not have NFL contests and had inaccurate players lists respectively. We will look to add more sources if there is sufficient interest from readers.

      Reply
  4. Huey (@hueykwik) says:
    September 6, 2016 at 1:51 am

    Is there an easy way to exclude games? For instance, if I’m only playing Sundays games, I’d want an easy way to exclude players from Thursday and Monday.

    Reply
    • Val Pinskiy says:
      September 6, 2016 at 8:58 am

      We don’t currently have a feature like that (you’d have to exclude players manually) but we can add it to our to-do list!

      Reply
      • Mike says:
        September 10, 2016 at 9:14 am

        Yes, please. That would help!

        Reply
        • Ryan says:
          September 17, 2016 at 7:50 pm

          Isaac, I checked in FAQ’s and says the data will update periodically wed thru Sunday.. does the date in the weekly proj. app on the top right mean that’s the last time the salaries and proj. data was scraped? Or does it mean something else? If so, when do you think we can expect them to be updated before tomorrow’s games? Love this subscription btw. Thanks!

          Reply
          • Isaac Petersen says:
            September 18, 2016 at 12:30 am

            Updated!

      • Fred says:
        October 7, 2016 at 1:07 am

        I am a subscriber and I appreciate the work put into creating these projections, thank you! I just wanted to add something onto Huey’s idea about excluding games. Could you please add “Exclude Team” as well? This way, the projections will not use a single player from the team that is excluded, and being able to exclude an entire team with one-click is much, much, faster than waiting to “see” if someone from that team pops-into the lineup and then have to excluded them, wait for the re-calculate process, and then…you get the idea. This could happen several times for different players from a single team. Thanks again!

        Reply
        • Val Pinskiy says:
          October 7, 2016 at 12:55 pm

          That is definitely something we’re looking to add, we appreciate the input.

          Reply
    • Mike says:
      September 10, 2016 at 4:43 pm

      Huey, I got around this by going into Lineup Optimizer, changed the settings to Fanduel, did the preferred averages and then downloaded custom rankings. I then went into RotoGrinders and downloaded their template .csv file. I merged the data between the FF Analytics and RotoGrinders files using a VLookup. FF Analytics uses the Team Name for DST so you’ll need to add the city. I also had to update Robert Griffin and Kadeem Carey’s names to match those of RotoGrinders. Once I merged the FF Analytics data with RotoGrinders I then uploaded the data to RotoGrinders. Now I can select whichever slates I want. I hope that helps, let me know if you have any questions. Would be glad to help.

      Reply
      • Mike says:
        September 10, 2016 at 4:46 pm

        By the way, I compared optimum lineups from what FF Analytics provided for all games and it was identical in RotoGrinders once I uploaded the data. That tells me both sites are using the same algorithms to generate optimum lineups.

        Reply
        • Huey Kwik says:
          September 28, 2016 at 6:54 pm

          I actually tried doing this, but I got different lineups. Did you download the projections from the projections app?

          Reply
  5. Anand Patel\ says:
    September 6, 2016 at 8:03 pm

    Getting rutime errors. Please fix this..

    Reply
    • Isaac Petersen says:
      September 6, 2016 at 11:58 pm

      Apps should be up now. For more info on why there were down, see here:
      https://fantasyfootballanalytics.net/app-down-heavy-traffic

      Reply
  6. Marc V. says:
    September 7, 2016 at 7:28 am

    Trying to use Fanduel optimizer. Currently getting an error no matter how many different types of ways I tweak the settings. Error reads:

    “nvalid class “MySQLResult” object: invalid object for slot “I’d” in class “MySQLResult”: got class “list”, should be or extend class “integer”
    In call:
    validObject(“,Production server: True

    Extremely frustrating! Never had an issue last year.

    Reply
    • Isaac Petersen says:
      September 7, 2016 at 7:58 am

      Hi Marc,

      Sorry for the trouble! I’m not able to reproduce. Could you give us more info so we can reproduce (see here for more info)?

      Thanks,
      Isaac

      Reply
      • Huey (@hueykwik) says:
        September 9, 2016 at 9:37 pm

        I get a similar error when I change the scoring from DraftDay to Yahoo DFS.

        Other settings: Week 1, 1 QB, 2 RBs, 3 WRs, 1 TE, 1 Flex, 1 DST.

        Reply
        • Isaac Petersen says:
          September 10, 2016 at 8:42 am

          Could you try again without changing the positions (or number of players at each position)? The dialog box isn’t showing the correct positions at the moment, but the app should generate the right positions in the weekly lineups for each source (and you can’t modify them for weekly leagues).

          Reply
          • Mike says:
            September 10, 2016 at 9:16 am

            I got the same thing last night just generating a lineup for Fanduel. I thought maybe it’s because I was using an ipad so I tried my laptop this morning and it works fine. Not sure if OS has anything to do with it.

          • Huey (@hueykwik) says:
            September 10, 2016 at 12:47 pm

            That worked, but then when I switched over to DraftKings, I got the same error again.

          • Isaac Petersen says:
            September 11, 2016 at 8:55 am

            Try these things first:
            https://fantasyfootballanalytics.net/about-the-site/faq#errors

          • Justin says:
            September 14, 2016 at 7:28 pm

            I received the same error on my iMac. I took all four steps you mentioned in the article below and nothing resolved it. Could it be an Apple product issue?

          • Isaac Petersen says:
            September 15, 2016 at 12:00 am

            Possibly, but not sure. We’d need more info to reproduce. What settings are you using (esp. specific changes that you made)? What browser are you using? Some have had success on Chrome, others have had success on Safari. Let us know if you get a chance to test on a PC.

          • Justin says:
            September 15, 2016 at 10:16 am

            The only setting change I made was to change it to week 2, instead of the full season. Chrome is the main browser I use but it hasn’t worked on Safari or Firefox, either.

          • Justin says:
            September 15, 2016 at 1:55 pm

            Update: the optimizer worked for a few hours earlier today on my iPhone. However, now it’s giving me the exact same error as on the comp

          • Isaac Petersen says:
            September 15, 2016 at 11:49 pm

            Could you try Chrome in Incognito mode? What happens when you try to change the salary source for week 2 to a different source?

  7. Tj says:
    September 7, 2016 at 8:41 am

    For the analysts used, right now I see CBS, Fantasy Sharks, NFL, and Yahoo Sports. Will you be adding more?

    Reply
  8. aemil says:
    September 7, 2016 at 1:18 pm

    Anyone know what are the premium features you get by subscribing to the projection app? the language is very vague “Upgrade your account with a monthly subscription and get the full force of our apps behind your player picks! ”

    How is the free account limited compared to the premium account ?

    Reply
    • Isaac Petersen says:
      September 7, 2016 at 8:32 pm

      See here:
      https://fantasyfootballanalytics.net/2016/08/introducing-ffa-insider.html

      Reply
  9. Travis says:
    September 7, 2016 at 1:52 pm

    Hey Isaac, like the App. For some reason there are a few players without salaries for draft kings.. any other people having this issue? Antonio Brown and Jordan Reed were two

    Reply
  10. Huey (@hueykwik) says:
    September 7, 2016 at 8:13 pm

    What’s the difference between your optimizer and others? For instance, I pulled your projections for FantasyAces, put them into RotoGrinders, and got different results. This is surprising, since I imagined that all the optimizers are solving the same math problem.

    Reply
    • Isaac Petersen says:
      September 7, 2016 at 8:38 pm

      Not familiar with RotoGrinders’ optimizer, but our projections are likely different from theirs, so I would expect different results.

      Reply
      • Huey (@hueykwik) says:
        September 7, 2016 at 9:01 pm

        My point is I input your projections into their optimizer and got different results.

        Reply
        • Huey (@hueykwik) says:
          September 7, 2016 at 9:02 pm

          Sorry if that sounded a bit abrupt! All I meant was that since I’m feeding RotoGrinders projections I pulled off the FantasyFootballAnalytics projections tool, I would expect similar lineups. However, perhaps it has something to do with the way you calculate risk. Just curious!

          Reply
        • Isaac Petersen says:
          September 8, 2016 at 7:55 am

          Without knowing the math and code they’re using to optimize, it’s hard to know. Our optimization syntax is open source, so we’re transparent about what optimization we’re doing.

          Reply
          • Huey (@hueykwik) says:
            September 8, 2016 at 4:38 pm

            Where does your optimization syntax live? I couldn’t find it on https://github.com/isaactpetersen/FantasyFootballAnalyticsR

          • Isaac Petersen says:
            September 10, 2016 at 12:01 am

            For example, see here: https://fantasyfootballanalytics.net/2013/08/optimization-simulation.html

  11. Mark Sherrod says:
    September 8, 2016 at 12:54 am

    Hey Issac,

    I just purchased the app and subscribed. 1) can I use the lineup optimizer if my 12 man league doesn’t have caps for our teams? 2) Im having the same problem with it not loading, or the projections. It keeps sailing “There was a problem reaching our servers for user validation.”

    Reply
    • Isaac Petersen says:
      September 8, 2016 at 7:58 am

      What is your league based on? Snake draft? If so, see here: https://fantasyfootballanalytics.net/2013/09/win-your-fantasy-football-snake-draft.html

      We’d need more info to reproduce. What are you doing to get the error? You might try disabling your adblockers, removing your cache, and/or a different browser.

      Reply
  12. Cole says:
    September 8, 2016 at 9:02 am

    Hey Isaac,

    I purchased a subscription and am trying to utilize the Weekly Lineup Optimizer, but it’s still not working. I read the recent comments and understand that within “high activity hours” I could run into trouble. That being said, I’ve been attempting this at all hours since yesterday and it still not working.

    I select “Week 1” and “DraftKings” scoring in the “Change Data Settings” screen, but instead of loading weekly projections, it reverts back to a blank lineup with season long auction value still referenced.

    I have tried logging out, restarting, etc. several times. What are my next steps?

    Reply
    • Isaac Petersen says:
      September 8, 2016 at 8:20 pm

      Hi Cole,

      Very sorry about the trouble! Could you try deleting your cache, disabling your adblockers, and/or a different browser? You might try Chrome if you’re not using it (that’s we test development on), or a different browser if you already are. Let us know if you continue to have problems.

      Thanks,
      Isaac

      Reply
      • Cole says:
        September 9, 2016 at 9:41 am

        I deleted cache, disabled add-blockers, and switched to Chrome yesterday. It was still displaying error messages. But this morning I tried again and it’s working just fine on Chrome! Thank you.

        Reply
  13. Chris says:
    September 8, 2016 at 2:22 pm

    Will you update the projections after the injury reports are finalized?

    Reply
    • Isaac Petersen says:
      September 8, 2016 at 8:30 pm

      https://fantasyfootballanalytics.net/about-the-site/faq#weeklyWhen

      Reply
  14. Jeremy says:
    September 8, 2016 at 3:45 pm

    Would it be possible to make it is so the app can pull a range of weeks instead of individual weeks? Would be useful to be able to load chunks of the data at once rather than have to load every week individually. Thanks.

    Reply
    • Isaac Petersen says:
      September 8, 2016 at 8:31 pm

      We can add that to our to-do list, thanks!

      Reply
  15. Keith A Fetz says:
    September 9, 2016 at 3:14 pm

    Having issues with it now..It generates lineups for Draftkings that are over the salary caps for draftkings which make them useless. It is also giving me the following error: nternalRS_DBI_getconnection:
    Corrupt connection handle. IN call “, productionserver: True

    Reply
    • Isaac Petersen says:
      September 10, 2016 at 1:31 am

      I’m not getting lineups over the salary cap for DraftKings. Could you try deleting cache, disabling your ad blockers, and/or a different browser (esp. Chrome)? We’d need more info to reproduce. What specific changes are you making?

      Reply
  16. David says:
    September 10, 2016 at 3:24 pm

    Is it possible to save the point scoring settings so that we don’t have to enter it in every time? Thanks!

    Reply
    • Isaac Petersen says:
      September 11, 2016 at 8:57 am

      We can add that to our to-do list, thanks!

      Reply
  17. kobybeast says:
    September 11, 2016 at 3:23 am

    Can we also update the tool to allow to choose different slates (e.g., Thu-Mon, Sun-Mon, Sun Only, 1:00EST Games Only, etc) as well as an option to automatically recommend “sleepers.” this would be very useful for GPP systems

    Reply
    • Isaac Petersen says:
      September 11, 2016 at 8:58 am

      We can add that to our to-do list, thanks!

      Reply
  18. Huey (@hueykwik) says:
    September 11, 2016 at 11:33 am

    Getting an error when trying to use Yahoo or FantasyAces:

    An error has occurred:

    “NTEGER() can only be applied to a ‘integer’, not a ‘raw’

    In call:
    “, Production server: True

    Repro steps:

    1. Change Data Settings
    2. Change scoring to Yahoo
    3. Click Load

    Reply
    • Isaac Petersen says:
      September 11, 2016 at 10:08 pm

      We’re not able to replicate. Are you making any scoring or lineup changes? Try these things:
      https://fantasyfootballanalytics.net/about-the-site/faq#errors

      Reply
      • Huey (@hueykwik) says:
        September 14, 2016 at 10:16 pm

        No, not making any lineup or scoring changes. I tried the steps you outlined.

        Today I’m getting this error:

        “nternal error in RS_DBI_getConnection: corrupt connection handle

        In call:
        “, Production server: True

        Reply
        • Isaac Petersen says:
          September 15, 2016 at 12:02 am

          You mean you get this upon initial load? What happens when you try to change the salary source (and which salary source are you looking to use)? What browser are you using?

          Reply
          • Huey (@hueykwik) says:
            September 15, 2016 at 2:50 am

            Ah, I did switch from FanDuel to DraftKings and got the error. I was able to get this working my using Incognito Mode in Chrome.

            Using Chrome 53.0.2785.113 (64-bit) on Mac 10.11.6.

          • Isaac Petersen says:
            September 15, 2016 at 8:12 am

            Good suggestion to use Incognito Mode, I’ll add that to the FAQ. Not sure if that addresses others’ problems. Thanks!

  19. John says:
    September 11, 2016 at 12:12 pm

    I am using the lineup optimizer for Draft Kings and why when I change the data settings to draft kings, I also take the kicker out and add a receiver when I load it the results come up with a kicker everytime and no 3rd receiver. Please help. I have cleared cache and using Chrome

    Reply
    • Isaac Petersen says:
      September 12, 2016 at 7:54 am

      Hi John,

      For the Weekly optimizer, the code does not use the user inputs for positions in the lineup (so you shouldn’t need to change the lineup positions). That is read from the database, which is set at 1QB, 2RB, 3WR, 1Flex and 1 DST for DraftKings, so it shouldn’t return a kicker in the lineup. As far as I can it tell it doesn’t. Let us know if you see otherwise.

      Thanks,
      Isaac

      Reply
  20. nick says:
    September 14, 2016 at 3:59 pm

    does the subscription automatically renew or do you have to manually renew each month?

    Reply
    • Isaac Petersen says:
      September 14, 2016 at 11:46 pm

      Subscriptions renew automatically, so you don’t have to renew manually. Thanks for checking!

      -Isaac

      Reply
  21. Huey (@hueykwik) says:
    September 15, 2016 at 2:37 pm

    Are you guys going to update your projections today? Thursday is an important day for us DFS players!

    Reply
    • Isaac Petersen says:
      September 15, 2016 at 11:50 pm

      Yes, they were updated earlier today.

      Reply
      • Huey says:
        September 22, 2016 at 6:03 pm

        It’s 3pm and the projections aren’t updated yet. What is going on?

        Reply
  22. sanga collins says:
    September 16, 2016 at 9:32 am

    Several players have the same player ID which is wreaking havoc with my R scripts for optimizing lineups. Can this be looked into?

    playerId playername
    2531332 Terrelle Pryor
    2531332 Terrelle Pryor
    2541429 B.J. Daniels
    2541429 B.J. Daniels
    2553652 Chris Harper
    2553652 Chris Harper
    2554138 Kasen Williams
    2554138 Kasen Williams
    2556528 D.J. Foster
    2556528 D.J. Foster

    Reply
    • sanga collins says:
      September 16, 2016 at 9:32 am

      Sorry, here is a better example
      playerId playername position team
      2531332 Terrelle Pryor WR CLE
      2531332 Terrelle Pryor QB CLE
      2541429 B.J. Daniels QB FA
      2541429 B.J. Daniels WR FA
      2553652 Chris Harper WR FA
      2553652 Chris Harper WR FA
      2554138 Kasen Williams WR FA
      2554138 Kasen Williams WR FA
      2556528 D.J. Foster RB NE
      2556528 D.J. Foster WR NE

      Reply
      • Isaac Petersen says:
        September 17, 2016 at 9:41 am

        We’d need more info to reproduce. What line of code are you running? What’s your output from running sessionInfo()?

        Reply
        • sanga collins says:
          October 14, 2016 at 8:39 am

          Sorry i did not configure notifications for this post. This is happening in the projections app

          Reply
  23. James says:
    September 21, 2016 at 2:42 pm

    is there any info on how the optimum lineups did historically – trying to figure out how it would perform if entered into a DK or FD double up each week. One issue it could run into is picking players that are popular picks which could reduce the edge in daily fantasy.

    Reply
    • Isaac Petersen says:
      September 22, 2016 at 11:57 pm

      I don’t play DFS and am not that familiar with it, but we’d welcome an analysis of how our optimums lineup perform. How would we be able to test that (without playing)? Open to suggestions!

      Reply
      • James says:
        September 23, 2016 at 5:01 pm

        I’m not sure if there’s a way to scrub the player start percentages from DraftKings or if they publish that data each week. One thing that would be helpful though would be to see the score actual total score of each optimal lineup which could be compared against score needed to be in the money at the DFS sites.

        It would be helpful to see the three optimal lineups from each week and how they ended up doing. Not sure if you’re able to retroactively call up old optimal lineups though.

        Thanks for everything, love the site.

        Reply
        • Isaac Petersen says:
          September 24, 2016 at 11:52 am

          Hey James,

          Great suggestion. I love the idea. I don’t play DFS, so not sure how to do that. Ideas?

          Thanks,
          Isaac

          Reply
  24. Huey (@hueykwik) says:
    September 21, 2016 at 9:04 pm

    Does the accuracy tab work? I don’t see anything when I click on it.

    Reply
    • Isaac Petersen says:
      September 22, 2016 at 10:56 pm

      Works for me. Use the Projections tool (http://apps.fantasyfootballanalytics.net/) and select a past season before selecting the Accuracy tab. Let us know what happens if that doesn’t work.

      Reply
  25. Garrett Reed says:
    September 22, 2016 at 3:56 pm

    Hello, my optimizer today is telling me last updated 9/20… before I lock things in, will there be another update before tonght? And if not, also before sunday/monday? Thanks!!!

    Reply
  26. h says:
    September 22, 2016 at 4:26 pm

    Projections getting updated today?

    Reply
  27. Huey (@hueykwik) says:
    September 22, 2016 at 6:17 pm

    Where are today’s projections?

    Reply
  28. GetGuud says:
    September 27, 2016 at 1:55 pm

    When do projections update?

    Reply
    • Isaac Petersen says:
      September 28, 2016 at 12:05 am

      https://fantasyfootballanalytics.net/about-the-site/faq#weeklyWhen

      Reply
      • Huey Kwik says:
        September 29, 2016 at 1:09 am

        Second week in a row where the projections are not updated on Wednesday. What’s going on? Last week, you didn’t even get them up on Thursday which is when DFS games start.

        Reply
  29. MD says:
    September 28, 2016 at 10:49 am

    Lineup optimizer for Week 4 DraftKings settings fails with a “An error occurred while updating the data. Please try again.” error. Week 4 FanDuel seems to work fine. I run into errors like this pretty much every week and have to log in/out in fresh browser sessions regularly to get it to work 🙁

    Also, the Ceiling/Floor as currently calculated isn’t very useful IMO (I understand why you do that since you only get point estimates from the underlying data sources). What is useful though are the low/high values representing the actual predicted distribution of points. Based on historical results, setting the 95% conf interval to [0, 1.5*(your calculated ceiling)] is an ugly hack that seems to be pretty predictive so far this season.

    Reply
    • Isaac Petersen says:
      September 29, 2016 at 12:48 am

      Sorry for the trouble! We’d need more info to reproduce. Please try these things first:
      https://fantasyfootballanalytics.net/about-the-site/faq#errors

      Agreed that the actual performance doesn’t always fall within the predicted interval. There is a tradeoff between precision and confidence. We give greater precision with less confidence. We feel that this approach is more useful than an interval that is well calibrated but incredibly wide and that doesn’t tell you much (especially if it includes zero for all players). In general, research has shown that people prefer informativeness over accuracy (Yaniv & Foster, 1995, 1997). We have plans to write an article about the calibration of our prediction intervals:
      http://circ.ahajournals.org/content/115/7/928

      Reply
      • MD says:
        September 29, 2016 at 9:10 pm

        Re: error, the only thing I was doing was logging in (inside a fresh Chrome incognito window), changing data to Week 4, game type to Draft Kings, clicking Apply, and getting the error. Performing the exact same steps later in the day eventually worked, so I assumed it was a data issue. Let me if there’s other info might help for next time.

        Re: article, nice, def looking forward to that!

        Re: intervals, I use the interval for producing predicted point distributions of the lineups for DFS play. Individuals’ ranges are wide but the composite lineup distribution is naturally tighter and seems to be in the right ballpark. With that I can quantify things like “probability this lineup hits at least 140 points”, which (ignoring the underlying hack) is at least for me a more useful risk metric. And can be then fed into chances of making the money, probability distribution of $ expectations, lineup portfolio analysis, etc.

        Which all depends on being able to extract reasonable distributions at the player level.

        Reply
        • Isaac Petersen says:
          September 30, 2016 at 8:06 am

          Agreed that the interval you use depends on the goal. We have decided to use smaller intervals to help people compare the floors and ceilings of players more easily. We can consider computing multiple sets of intervals, to include more calibrated intervals as well.

          Thanks!
          -Isaac

          Reply
  30. brucehao says:
    October 6, 2016 at 1:53 pm

    Hi Issac, as an FFA Insider, I’m having trouble with the app.

    1) I don’t think the app is loading at all. When I click on Sign In, the address bar changes to ‘http://apps.fantasyfootballanalytics.net/projections#signup’, but nothing else changes. Both Projections and Lineup Optimizer are completely blank. It’s the same for all other buttons and links. The URL changes, but the screen does not update.
    2) Chrome / Chrome Incognito (Version 53.0.2785.143); I’ve also tried Safari and IE
    3) Windows 8 and Mac os10 Sierra tested with same results

    Thanks for any help you can provide.

    Reply
  31. Fred says:
    October 7, 2016 at 1:21 am

    Hi Issac, as an FFA insider, I am also having the same issue that Brucehao is having. I have tried Chrome, I.E., and Firefox using windows 10. Here is what is popping up when the page starts to load:

    An error has occurred:
    “onnection with pending rows, close resultSet before continuing

    In call:
    , Production server: True”

    Reply
    • Val Pinskiy says:
      October 7, 2016 at 12:51 pm

      We will look into this error, thanks!

      Reply
  32. Rob says:
    October 14, 2016 at 10:24 am

    I’m getting the following error on the Lineup Optimizer:

    An error has occurred:

    “nvalid class “MySQLResult” object: invalid object for slot “Id” in class “MySQLResult”: got class “character” , should be or extended class “integer”

    In call;
    validObject(“, Production server: True

    Reply
  33. Rob says:
    October 14, 2016 at 3:50 pm

    Guys, I’m continuing to get errors that have rendered the Lineup Optimizer useless. Can you at least confirm you are aware of the issue and are working to fix the problem?

    Reply
    • Val Pinskiy says:
      October 15, 2016 at 12:23 pm

      Hi Rob, thanks for letting us know. We are working to resolve this error now.

      Reply
  34. Fred says:
    October 14, 2016 at 4:22 pm

    Hi guys, I had a similar error to Rob’s last week I believe it was, and I read that using Chrome Incognito may help, and it did! (You may want to give it try Rob). Anyway, I am getting another error (despite) using Chrome incognito as well as not in incognito. I cannot copy/paste it, and I limited time so I cannot type the error all out now, but wanted to make you aware that it is also happening. (I do have the exact same “In call” portion at the bottom of the error as Rob has noted above if it helps.

    Reply
    • Rob says:
      October 14, 2016 at 4:28 pm

      The previous error (that I typed out) has ceased, but I have continued to get new errors

      Reply
  35. Fred says:
    October 16, 2016 at 1:11 am

    Hi guys, it’s almost 1:00 am on Sunday 10/16/16…game day. This is the only time that I have left to myself that I can spend doing the rest of my lineups, and once again, the optimizer throws-up errors regardless of what browser I use…I have used them all, including Chrome incognito,as I know the drill all to well now with these errors. And asking people for “what error” is , at this point is a ridiculous question because there are too many people that have these errors and too often…and these are clearly just not being ironed out. It was working just fine 24 hours ago, but again, here we go with the errors. Why?

    I’m an FFA insider who would gladly pay you any reasonable amount for your monthly fee, even beyond what you currently charge. But the issue is that when I cannot even load the optimizer into any browser more often than not because of these on-going errors, the value becomes zero right? It’s really disappointing that so many people have these errors loading, yet nothing serious has been done to once and for all, just make them stop. Being able to load data is the most basic of requirements to fulfill to your users guys, there’s no other way to say it.

    There should never be an issue loading data from a website 99.99% of the time – period. I literally have no issue loading any other site on the web…ever…literally, ever. I have a brand new computer, am running Windows 10, no hardware issues, three different browsers with no browser issues, and reasonable technical skills. I just don’t understand why this isn’t a MAJOR priority…as in your number one item to fix here before doing another thing on data or otherwise. (As in so that it never ever happens one more to any of your users). If the company I work for, for example ever had a website down for even a minute, it would be major news..and a top priority to not only fix it right now, but to learn why it happened and take measures for it not to happen again for that reason.

    Think of the problem you have like this…if you have a store with the best product available, a great location and good prices and people from all over for miles and miles come to your store to buy, that sounds awesome…a dream right? But if doors to the store is locked when they get there, how are people supposed to get in? They’re looking in the window at you and your product, but you won’t let them in. This is how not taking care of these errors once and for all makes your users feel. We take the time to give you this valuable feedback in an attempt to get it fixed…not today…but for good. Why would you want people to keep telling you every day when they cannot loan data?

    I have had a lot of faith in your analytical skills, no doubt, but this is frustrating guys, just frustrating.

    Reply
    • Travis says:
      October 16, 2016 at 10:56 am

      I was monkeying with this a bit and ran into the same issue. I then went and zeroed out all of the weights for the different sites and it ‘worked’ — it gave no data, but it at least didn’t error out. I suspect one of the sites is not cooperating and zeroing that one out, or excluding it from a weighted average may allow the data to be loaded (minus that one site).

      Reply
    • Val Pinskiy says:
      October 17, 2016 at 4:09 pm

      Hi Fred,

      We apologize sincerely for the issue, we’re working to resolve it now.

      Thanks,
      FFA Team

      Reply
      • Fred says:
        October 22, 2016 at 12:44 am

        So I was working on my lineups for about an hour, and then just after midnight, the errors start popping up again, and now the optimizer doesn’t work again. It was working perfectly for an hour…but right after midnight…it stopped. Hopefully that tells you where to look. It’s definitely not on the users end.

        Reply
        • Fred says:
          October 22, 2016 at 3:23 pm

          Still cannot get past the error:

          I cannot copy and paste it, so I have to type it all out ugh…

          An error has occurred:

          “NTEGER() can only be applied to a ‘integer’, not a “character’

          In call:
          “,Production server:True

          Reply
          • Fred says:
            October 22, 2016 at 3:24 pm

            Forgot to tell you that I am using Windows 10 premium, chrome incognito (as suggested).

  36. Jay says:
    November 2, 2016 at 9:17 pm

    Hello,

    Thank you for the great tools. It seems that no matter how I change the settings the weekly lineup optimizer always gives me 3 RBs and 3 WRs? I’ve tried to get it to give me only 2 RBs and flex in a 4th WR or a second TE but it does not seem to allow me to do this for DFS?

    Thoughts?

    Reply
    • Isaac Petersen says:
      November 3, 2016 at 6:49 am

      The DFS optimizer doesn’t take position inputs because the positions are fixed by site. Pick the site you’re using (e.g., FanDuel, DraftKings), and they should have the correct positions. You can also use our regular lineup optimizer for season-long leagues that allows changing the number of players to draft at each position (just select week=”Full Season” instead of a week).

      Reply
  37. Josh payne says:
    November 19, 2016 at 10:11 am

    I have re-subscribed and it will not log me in as a paying member. I have been trying for two days. What is going on?

    Reply
    • Val Pinskiy says:
      November 21, 2016 at 5:24 pm

      This error should be resolved now. Please let us know if this occurs again.

      Reply
  38. Josh says:
    November 20, 2016 at 10:14 am

    Guys, I have tried to re-subscribe for 4 days now. Each time I pay it doesn’t update and make me a subscriber. Please advise. Thanks.

    Reply
    • Val Pinskiy says:
      November 21, 2016 at 5:27 pm

      Should be fixed now!

      Reply
  39. Josh payne says:
    December 3, 2016 at 12:24 pm

    I am getting an error in both chrome and firefox. Something about a line script. Please advise.

    Reply
  40. Brandon says:
    December 5, 2016 at 10:39 pm

    Yeah the optimizer aren’t working again what’s the deal?

    Reply
    • Val Pinskiy says:
      December 6, 2016 at 5:43 pm

      Please see our troubleshooting tips here: https://fantasyfootballanalytics.net/about-the-site/faq#errors

      Can you provide some more detail on your error?

      Reply
  41. brandon says:
    December 9, 2016 at 2:32 pm

    The projections arent loading at all. I keep getting an in call error and im using chrome and in incagneto

    Reply
    • Val Pinskiy says:
      December 12, 2016 at 11:00 am

      Hi Brandon,

      Can you provide some more detail on your error so we can try to resolve?

      Reply
  42. Jesse says:
    September 15, 2017 at 11:21 am

    When I change the lineup optimizer to week 2 the app freezes. This has been occurring for the past 3 days. Anyone else having this problem?

    Reply
    • Val Pinskiy says:
      September 16, 2017 at 9:51 am

      Week 2 data is now available on the Lineup Optimizer, we apologize for the downtime.

      Reply
  43. autllc says:
    October 12, 2017 at 8:36 pm

    How do I optimize for only the Fanduel Sunday Main slate?

    Reply
  44. JACK says:
    September 9, 2018 at 9:10 am

    Is there a page with better explanation of how to use the lineup optimizer? I am very confused. If I select YahooDFS, the point totals are many times what they should be. For example, today’s projection for Matt Breida is 134.31 points.

    I think I notice that when I select players, the remaining suggested players change based upon what I have selected at left (highest points, highest floor, etc.). I’ve used this in the past with success, but the point totals are all off, no matter what site I select.

    Reply
    • Val Pinskiy says:
      September 9, 2018 at 12:16 pm

      Do you have Week 1 or the full season selected?

      Reply
  45. Tj says:
    September 9, 2018 at 12:35 pm

    I just want to mention the sleepers feature is not working

    Reply
  46. Richard Simonson says:
    August 10, 2019 at 11:06 pm

    I am trying to run the source file/example files you’ve provided in your git hub page. However, I keep getting similar errors essentially stating that certain functions and files do not exist.

    E.g.,

    could not find function “readHTMLTable”

    or

    could not find function “accuracy”

    I’ve already sourced everything into a directory. If the functions are called in the script what might be causing this?

    Thank you

    Reply
    • Isaac Petersen says:
      August 12, 2019 at 12:19 am

      Hi! Make sure you’re using the latest version of the package: https://fantasyfootballanalytics.net/2016/06/ffanalytics-r-package-fantasy-football-data-analysis.html

      Reply
  47. Jacob P Guerriero says:
    September 5, 2019 at 7:52 pm

    Salaries for Yahoo DFS aren’t currently loading on the week 1 Lineup Optimizer.

    Reply
  48. Rob says:
    September 20, 2019 at 9:06 pm

    Hi, I’m having trouble figuring out how to use the Optimizer for the different DFS sites (FD, DK & Yahoo). How do I do that?

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

  • Previous story Introducing FFA Insider
  • Next story PPR League Gold Mining – Week 1
  • Tabs

    • Most Popular
    • Recent Posts
    • The ffanalytics R Package for Fantasy Football Data AnalysisJune 18, 2016
    • 2015 Fantasy Football Projections using OpenCPUMay 28, 2015
    • Win Your Fantasy Football Auction Draft: Determine the Optimal Players to Draft with this AppJune 14, 2013
    • Win Your Fantasy Football Snake Draft with this AppSeptember 1, 2013
    • Post-Combine Mock: Team Needs and TargetsMarch 10, 2025
    • Fantasy Football Weekly Cheat Sheet: Week 18 (2024)January 3, 2025
    • Fantasy Football Weekly Cheat Sheet: Week 17 (2024)December 26, 2024
    • Fantasy Football Weekly Cheat Sheet: Week 16 (2024)December 18, 2024
  • FFA Insider

    Logo
  • Categories

    • About the Authors
    • Articles
    • Auction Drafts
    • Draft Optimizer
    • FFA Insider
    • Gold Mining
    • How To
    • In the Media
    • Luck
    • Package
    • Projections
    • R
    • Risk
    • Theory
    • Tools
    • Trade Strategy
    • Uncategorized
    • Weekly
  • Facebook

  • Twitter

  • Our Partners

    R-bloggers

  • Support us building things... Even a cup of coffee ($1.99) helps us stay awake!

  • Subscribe to the Fantasy Football Analytics mailing list (no spam).
    Loading

        © Fantasy Football Analytics

        %d