fplreview
@fplreview.com
FPL planning toolset with integrated projections, multi-period solver & season review capabilities
fplreview.com
fplreview.com
Hey, yes it's a new set of drafts every week
The reason for this is that many drafts will end up being incoherent with the actual moves you played before the deadline- so it resets to your base team each GW
The reason for this is that many drafts will end up being incoherent with the actual moves you played before the deadline- so it resets to your base team each GW
October 25, 2025 at 10:27 AM
Hey, yes it's a new set of drafts every week
The reason for this is that many drafts will end up being incoherent with the actual moves you played before the deadline- so it resets to your base team each GW
The reason for this is that many drafts will end up being incoherent with the actual moves you played before the deadline- so it resets to your base team each GW
Hey, this can happen for 2 reasons:
1- If the tab is changed while the "loading" screen appears.
2- Some browsers/devices seem to trigger this, so trying a different device or browser might solve it
If you send me your team ID, I can manually get the data for you too
1- If the tab is changed while the "loading" screen appears.
2- Some browsers/devices seem to trigger this, so trying a different device or browser might solve it
If you send me your team ID, I can manually get the data for you too
May 28, 2025 at 10:04 PM
Hey, this can happen for 2 reasons:
1- If the tab is changed while the "loading" screen appears.
2- Some browsers/devices seem to trigger this, so trying a different device or browser might solve it
If you send me your team ID, I can manually get the data for you too
1- If the tab is changed while the "loading" screen appears.
2- Some browsers/devices seem to trigger this, so trying a different device or browser might solve it
If you send me your team ID, I can manually get the data for you too
Ludicrous season, well done Stefan!
May 25, 2025 at 10:24 PM
Ludicrous season, well done Stefan!
Just need to refresh the background sample- the NFO-BRE fixture was likely too tight to the next GW deadline, so the data wasn't there when that GW34 background calcs were made.
Will be synced back up following the next GW deadline
Will be synced back up following the next GW deadline
May 15, 2025 at 3:29 PM
Just need to refresh the background sample- the NFO-BRE fixture was likely too tight to the next GW deadline, so the data wasn't there when that GW34 background calcs were made.
Will be synced back up following the next GW deadline
Will be synced back up following the next GW deadline
Basically all his mins are as a winger at the moment
April 23, 2025 at 2:16 AM
Basically all his mins are as a winger at the moment
Going to respond here too (in case any one here stumbles on the same)
Issue relates to an "in conflict" tag and how it interacts with the code.
The 1/99 fix should sort this out for you, until I patch in a fix to get it to stop searching for a fixture removed from the "uncertain" pool
Issue relates to an "in conflict" tag and how it interacts with the code.
The 1/99 fix should sort this out for you, until I patch in a fix to get it to stop searching for a fixture removed from the "uncertain" pool
April 1, 2025 at 11:21 AM
Going to respond here too (in case any one here stumbles on the same)
Issue relates to an "in conflict" tag and how it interacts with the code.
The 1/99 fix should sort this out for you, until I patch in a fix to get it to stop searching for a fixture removed from the "uncertain" pool
Issue relates to an "in conflict" tag and how it interacts with the code.
The 1/99 fix should sort this out for you, until I patch in a fix to get it to stop searching for a fixture removed from the "uncertain" pool
This is a game? I thought we've all been engaging in long running self torment
March 31, 2025 at 10:06 PM
This is a game? I thought we've all been engaging in long running self torment
Hi Mike, it will depend on the timing
For example of you choose GW30 for AM and GW31 + GW32 for WC, there is actually no valid chip plan because the options are in conflict
For example of you choose GW30 for AM and GW31 + GW32 for WC, there is actually no valid chip plan because the options are in conflict
March 31, 2025 at 4:59 PM
Hi Mike, it will depend on the timing
For example of you choose GW30 for AM and GW31 + GW32 for WC, there is actually no valid chip plan because the options are in conflict
For example of you choose GW30 for AM and GW31 + GW32 for WC, there is actually no valid chip plan because the options are in conflict
Two addendums now that I think of it:
- Bear in mind the found chip plans are based on full knowledge of the fixtures. In reality, there will be some value in holding for announcements- so avoid taking too literally
- "Exit Solve" doesn't seem to be linked in, will get to it but not priority atm
- Bear in mind the found chip plans are based on full knowledge of the fixtures. In reality, there will be some value in holding for announcements- so avoid taking too literally
- "Exit Solve" doesn't seem to be linked in, will get to it but not priority atm
March 31, 2025 at 12:57 PM
Two addendums now that I think of it:
- Bear in mind the found chip plans are based on full knowledge of the fixtures. In reality, there will be some value in holding for announcements- so avoid taking too literally
- "Exit Solve" doesn't seem to be linked in, will get to it but not priority atm
- Bear in mind the found chip plans are based on full knowledge of the fixtures. In reality, there will be some value in holding for announcements- so avoid taking too literally
- "Exit Solve" doesn't seem to be linked in, will get to it but not priority atm
I intend to extend the "Chip Plan => Search" capability to regular solves, though I've just completely ran out of steam at this point in the race to be ready for GW30
The next weeks will be aimed at smaller, nagging fixes that are required and also at longer term projects.
The next weeks will be aimed at smaller, nagging fixes that are required and also at longer term projects.
March 31, 2025 at 12:57 PM
I intend to extend the "Chip Plan => Search" capability to regular solves, though I've just completely ran out of steam at this point in the race to be ready for GW30
The next weeks will be aimed at smaller, nagging fixes that are required and also at longer term projects.
The next weeks will be aimed at smaller, nagging fixes that are required and also at longer term projects.
Binary solves was a much requested feature over the past month, the concept has been built out from the analytics discord community over the past months- my understanding is that @jonnyc.bsky.social, OG & Joose all contributed to the various elements so huge credit is deserved on their side!
March 31, 2025 at 12:57 PM
Binary solves was a much requested feature over the past month, the concept has been built out from the analytics discord community over the past months- my understanding is that @jonnyc.bsky.social, OG & Joose all contributed to the various elements so huge credit is deserved on their side!
Chip Plan > Search: You can now choose various GWs for as an option per chip. This is a two-stage process, using literal settings (decay=1.01, ftval=0 etc.) to select chip plan and then reverts to user settings to solve for the root move
Chip Plan > Fixed: Default use, from main planner page
Chip Plan > Fixed: Default use, from main planner page
March 31, 2025 at 12:57 PM
Chip Plan > Search: You can now choose various GWs for as an option per chip. This is a two-stage process, using literal settings (decay=1.01, ftval=0 etc.) to select chip plan and then reverts to user settings to solve for the root move
Chip Plan > Fixed: Default use, from main planner page
Chip Plan > Fixed: Default use, from main planner page
Binary Fixture Solves: Every possible combination of fixture sets is generated (and will update on user input).
For each fixture set, EV is recalculated for each binary schedule and solved individually.
(% weights in tables based on schedule likelihoods)
For each fixture set, EV is recalculated for each binary schedule and solved individually.
(% weights in tables based on schedule likelihoods)
March 31, 2025 at 12:57 PM
Binary Fixture Solves: Every possible combination of fixture sets is generated (and will update on user input).
For each fixture set, EV is recalculated for each binary schedule and solved individually.
(% weights in tables based on schedule likelihoods)
For each fixture set, EV is recalculated for each binary schedule and solved individually.
(% weights in tables based on schedule likelihoods)
It was changed as the feedback found the numerical input a bit unintuitive, but I can see where you coming from it is nice to have that extra granularity
I think the best solution for all will be an annotated slider, to give full control and intuition for input
I think the best solution for all will be an annotated slider, to give full control and intuition for input
March 14, 2025 at 3:57 PM
It was changed as the feedback found the numerical input a bit unintuitive, but I can see where you coming from it is nice to have that extra granularity
I think the best solution for all will be an annotated slider, to give full control and intuition for input
I think the best solution for all will be an annotated slider, to give full control and intuition for input
Just updated that now btw, should be settable up to 1.05
March 13, 2025 at 10:30 AM
Just updated that now btw, should be settable up to 1.05
Glad to have it across in time, just about 😅
March 13, 2025 at 12:17 AM
Glad to have it across in time, just about 😅
Ah, thanks for letting me know that- I'll update that in the morning to let the setting go to 1.01/1.02
March 13, 2025 at 12:05 AM
Ah, thanks for letting me know that- I'll update that in the morning to let the setting go to 1.01/1.02
I would have liked to make these additions earlier, AM was a bit of a bomb going off alongside running into extra tasks with the day-job & some non-work stuff too which made the past months a bit relentless
Fortunately we're back to normality now, and there's plenty of ideas and upgrades to come!
Fortunately we're back to normality now, and there's plenty of ideas and upgrades to come!
March 12, 2025 at 4:51 PM
I would have liked to make these additions earlier, AM was a bit of a bomb going off alongside running into extra tasks with the day-job & some non-work stuff too which made the past months a bit relentless
Fortunately we're back to normality now, and there's plenty of ideas and upgrades to come!
Fortunately we're back to normality now, and there's plenty of ideas and upgrades to come!
Downloadable Results
Downloadable results are a small addition, but beats opening up the snipping tool- I think it would be nice if it printed the solver settings used too to add that bit more context so that can be something for the future
(applies to both solvers)
Downloadable results are a small addition, but beats opening up the snipping tool- I think it would be nice if it printed the solver settings used too to add that bit more context so that can be something for the future
(applies to both solvers)
March 12, 2025 at 4:51 PM
Downloadable Results
Downloadable results are a small addition, but beats opening up the snipping tool- I think it would be nice if it printed the solver settings used too to add that bit more context so that can be something for the future
(applies to both solvers)
Downloadable results are a small addition, but beats opening up the snipping tool- I think it would be nice if it printed the solver settings used too to add that bit more context so that can be something for the future
(applies to both solvers)
Live Output + Exit
This addition really helps with running a few solve lines, as it was a bit frustrating waiting for longer solves with no info. The same goes for sensitivity analysis, as the lack of updates with the non-linear Transfer Solver can leave you wondering if something has gone wrong
This addition really helps with running a few solve lines, as it was a bit frustrating waiting for longer solves with no info. The same goes for sensitivity analysis, as the lack of updates with the non-linear Transfer Solver can leave you wondering if something has gone wrong
March 12, 2025 at 4:51 PM
Live Output + Exit
This addition really helps with running a few solve lines, as it was a bit frustrating waiting for longer solves with no info. The same goes for sensitivity analysis, as the lack of updates with the non-linear Transfer Solver can leave you wondering if something has gone wrong
This addition really helps with running a few solve lines, as it was a bit frustrating waiting for longer solves with no info. The same goes for sensitivity analysis, as the lack of updates with the non-linear Transfer Solver can leave you wondering if something has gone wrong
Solver Setting Interface
This upgrade should make working with the settings a bit more usable as they were a bit cramped as it was.
Equally, the revamp has also made it easier to add settings in future and I suspect they'll be categorised into groups in the future.
(applies to both solvers)
This upgrade should make working with the settings a bit more usable as they were a bit cramped as it was.
Equally, the revamp has also made it easier to add settings in future and I suspect they'll be categorised into groups in the future.
(applies to both solvers)
March 12, 2025 at 4:51 PM
Solver Setting Interface
This upgrade should make working with the settings a bit more usable as they were a bit cramped as it was.
Equally, the revamp has also made it easier to add settings in future and I suspect they'll be categorised into groups in the future.
(applies to both solvers)
This upgrade should make working with the settings a bit more usable as they were a bit cramped as it was.
Equally, the revamp has also made it easier to add settings in future and I suspect they'll be categorised into groups in the future.
(applies to both solvers)
Single Solve Chip Plans
Previously solves were segmented by chip plan, so for example WC32 & FH34 would be
Solve 1: GW29-31
Solve 2 (WC): GW32-38 (exc. GW34)
Solve 3 (FH): GW34
Now rather than having 3 solves, as in the Transfer Solver, there is just 1 solve required that will cover it all.
Previously solves were segmented by chip plan, so for example WC32 & FH34 would be
Solve 1: GW29-31
Solve 2 (WC): GW32-38 (exc. GW34)
Solve 3 (FH): GW34
Now rather than having 3 solves, as in the Transfer Solver, there is just 1 solve required that will cover it all.
March 12, 2025 at 4:51 PM
Single Solve Chip Plans
Previously solves were segmented by chip plan, so for example WC32 & FH34 would be
Solve 1: GW29-31
Solve 2 (WC): GW32-38 (exc. GW34)
Solve 3 (FH): GW34
Now rather than having 3 solves, as in the Transfer Solver, there is just 1 solve required that will cover it all.
Previously solves were segmented by chip plan, so for example WC32 & FH34 would be
Solve 1: GW29-31
Solve 2 (WC): GW32-38 (exc. GW34)
Solve 3 (FH): GW34
Now rather than having 3 solves, as in the Transfer Solver, there is just 1 solve required that will cover it all.
Sensitivity Analysis
Effectively this is creating a number of simulated alternative worlds with some random noise injected. The noise can be controlled for each xMins, player & team ratings and solver settings.
This solves the top line for each world first, before moving onto the next etc.
Effectively this is creating a number of simulated alternative worlds with some random noise injected. The noise can be controlled for each xMins, player & team ratings and solver settings.
This solves the top line for each world first, before moving onto the next etc.
March 12, 2025 at 4:51 PM
Sensitivity Analysis
Effectively this is creating a number of simulated alternative worlds with some random noise injected. The noise can be controlled for each xMins, player & team ratings and solver settings.
This solves the top line for each world first, before moving onto the next etc.
Effectively this is creating a number of simulated alternative worlds with some random noise injected. The noise can be controlled for each xMins, player & team ratings and solver settings.
This solves the top line for each world first, before moving onto the next etc.