#1 By: Michael C, June 25th, 2018 21:57
Hey all - the past couple days I've started to get into the swing of things, and have been firing up articles and apps to do research. I've been trying to use the customized projection app and keep getting this error though: "dims [product 1] do not match the length of object ". Is anyone else getting this? I've tried with different browsers on different computers, so it seems to be a website issue. Could the guys at Rotoviz look into it? Thanks.
#2 By: hrr5010, June 26th, 2018 09:14
@jaybizz The projection machine on the site or the Excel tool? If it's the Excel tool, I believe @dcaban can help out.
#3 By: Michael C, June 26th, 2018 09:58
@hrr5010 thanks for the reply, it's the app on the site that I'm referencing though
#4 By: hrr5010, June 26th, 2018 10:03
@jaybizz i believe that has been replaced by the following suite of tools: http://rotoviz.com/excel-tools/
Check them out. I'm working through the projection tool right now, and it's pretty sweet.
#5 By: William Russell, June 27th, 2018 15:55
@hrr5010 @Cort the tools by @dcaban are really great, but I do miss being able to use the MFL10 ADP and Customised Projection apps.
Any idea if they'll be updated or whether the functionality can be recreated using the Excel tools? I've not had much time to play around with them and I ask because the customised projections app would have been ideal for the Scott Fish competition...
#6 By: Daniel Schultz, July 10th, 2018 13:14
Is Rotoviz going to update/reactivate the Customized Cheat Sheet and Projection Wizard? I realize the Projection Machine gives us the ability to create our own projections, but I believe the Customer Cheat Sheet and Projection Wizard was an average of multiple Rotoviz writers. Is that going to be available or will there be a way to download the projections directly to the draft kit? Or will we need to create projections ourself in the excel projections machine.
#7 By: hrr5010, July 12th, 2018 14:19
Hey badger. The RotoViz team did create tiers for the Draft Dashboard, so they're already pre-loaded into the draft kit.
Check out this post for a better look at the tiers: http://rotoviz.com/2018/07/rotoviz-wr-tiers-behind-the-scenes/
I will say that i'm in the process of updating my projections, and once that process is complete i'll be tweaking my tiers. I doubt much changes, but once it does i'm certain Dave will update with that info.
I encourage creating your own projections (doesn't have to be a full suite, doing it for a handful of teams will be fine) if only to get a good sense of how this stuff flows together. the Excel suite is intuitive and it doesn't take much time to come up with a solid projection per team.
The reason i say this is because it's a solid way to becoming a better fantasy player. No projections are accurate, but i found that once I created my own set of projections i'm able to pinpoint where i'm wrong. or i'm able to find soft situations to exploit during drafts. It's also a solid way to look at changing situations or what needs to occur before things change and how likely it is. This leads you to find cheap dynasty buys/solid best ball values/guys you want to roster when it's draft season.
Unsure if this is the process @FF_Contrarian or @DaveCabanFF utilize, but it's how i approach it.
Also - feel free to tag me with any player related questions you might have! I'll do my best to answer them.
#8 By: Daniel Schultz, July 13th, 2018 09:10
Thanks for the response. Based on the reply, it sounds like there won't be numbers projections associated with the tiers though I hope I am wrong. For myself, I use VBD even if I know there is a lot of error in those projections. Just as there are errors into which tiers players are placed. I've heard the arguments against them, but I also take into account that as I draft and have been fairly successful using it for about 4-5 years.. If nothing else, I think the projections help determine the worth of players at different positions based on different scoring systems. Every league I play in, QB TDs are 6 points. In one league, the pts/yds are halved so while waiting on a QB in most leagues running 4 pts is wise, you won't win in that particular league being so TD dependent. The projections along with VBD help me determine the various worth between positions in a way that tiers do not. What tier at QB is worth a 3 or 4 tier RB or WR? I realize Dave's program allows you to adjust importance of positions, but without a gage to go off of, is a RB worth 25%, 35% or 50%? At this point, I hope I have assumed incorrectly and there actually will be "points" projections available. If not, I think that is a step backward.
#9 By: DaveCabanFF, July 14th, 2018 00:22
We do plan on publishing projections. However, they will need to be imported into the draft tool using the data import function. One of the underlying concepts of the tool was to not include projections. So they can be included, but are not encouraged. Those of us contributing to the tiers that are preloaded in the tool all do separate sets of projections to explore ranges of outcomes. These are significant inputs when putting our tiers together. Having said that, in my experience with building projections and tiering players, very rarely do these change a player's overall outlook - range of outcomes - and the tier that he would be placed into. Anyway, as I had mentioned, the projections can then be used to determine baselines for VBD, and drop the +/- into one of the custom metrics columns.
For anyone that is interested, I think one important caveat that needs to be made is that the reason for using tiers as opposed to VBD is not that tiers are more accurate. On the contrary, they are more so embracing the fact that we will not be perfect when prognosticating for the coming season. As a result, when using them you are not drafting off an inherently flawed decision tree, or at least to the same degree. Whereas with VBD, when you make a pick, not only is the player you are drafting based off extremely sensitive variables but the position that you are drafting is also based off of them. So it's not really evaluating the worth of each position against each other. It's comparing the +/- of the highest projected players at each position, at each pick against each other's spread. So, even if QBs are scoring 600 points, if the highest projected TE is +10 based on a projection of 150, VBD would say to draft him over the QB with 554 points but only a +4. But what if the points at QB drop off by 30 - 40 points after the next 2 QBs Now, a drafter should be aware of this and adapt accordingly, but is this really doing a better job of comparing positions than a drafter is able to do by understanding the quality of players that make up the tiers and considering them in the context of their league? More importantly, VBD really struggles with leagues that include Flex positions as the baseline process becomes more of a challenge and loses meaning. Another thing to consider is opportunity cost. Perhaps later in the draft, the spreads will be much more significant. One of the things I like the most about tiers is that they help to facilitate roster construction. Anyway, I just wanted to share my thoughts there. I'm not saying that mine or the RV approach is the absolute perfect approach and that you have to use it. Just wanted to provide some further thoughts on VBD and kind of stress that one of our major philosophies has been providing tools and analysis that encourage self-sufficiency.
#10 By: Daniel Schultz, July 14th, 2018 17:06
I’m thrilled to hear the projections will remain so I’ll simply download that along with my own VBD numbers into your draft tool. You have done a great job in making it easily adaptable for those that want to look at other data. And I really look forward to having a tool such as this with so much info available.
#11 By: Russell Davis, July 16th, 2018 09:57
Dave, I am an old fart and presently trying to learn enough about Excel to use your magnificent app. When I try to use the projection app to generate projections for the FFDRAFTPREP I keep getting this error message:dims [product 1] do not match the length of object . I have no clue what I am doing wrong. Please give me some direction. Thanks
#12 By: Russell Davis, July 16th, 2018 10:00
RIF, Reading is Fundamental. Sorry, I just reread the OP and realized I just asked the same thing. Sorry.