Let's say I plug all my league's info into a reliable fantasy baseball site - with league size, roster requirements, scoring system, and everything else. And let's say I do this on two different fantasy/roto baseball sites. And because each site has different statistical projections and weigh things differently - they each produce suggested/recommended auction dollar values that are obviously different from each other.
On to the question:
If I like both sites and think they each bring valuable things to the table when making their projections, should I combine the two lists to get an average?
Example:
If one site comes up with an auction dollar value of $33 for Player A; and the other site comes up with $41 for Player A - should I just take the average of $37?
Part of me thinks this is a great move. Afterall, I am taking the exact average of two different sets of data.
However, part of me fears this will change the dynamic of the list so much, that I won't be accounting for my total auction budget.
Is it is a good idea to combine them? Or am I better of just using one over the other?
---------------
On a separate matter, does anyone have any advice how to create a cheatsheet on one of these types of sites if our league values different scoring categories differently?
Example:
If 12 teams, then in the hits category - the top team gets 12, the next best gets 11, and so on thru the fantasy team with the fewest hits getting 1.
But what about if hits count as 1 (as just stated), but runs count as 2? Meaning, the fantasy team with the most runs gets 24 points, the next best gets 22, and all the way through to the team with the fewest runs getting 2 points. How would I account for a weighted roto setup?
Really appreciate any insight. Thanks.
On to the question:
If I like both sites and think they each bring valuable things to the table when making their projections, should I combine the two lists to get an average?
Example:
If one site comes up with an auction dollar value of $33 for Player A; and the other site comes up with $41 for Player A - should I just take the average of $37?
Part of me thinks this is a great move. Afterall, I am taking the exact average of two different sets of data.
However, part of me fears this will change the dynamic of the list so much, that I won't be accounting for my total auction budget.
Is it is a good idea to combine them? Or am I better of just using one over the other?
---------------
On a separate matter, does anyone have any advice how to create a cheatsheet on one of these types of sites if our league values different scoring categories differently?
Example:
If 12 teams, then in the hits category - the top team gets 12, the next best gets 11, and so on thru the fantasy team with the fewest hits getting 1.
But what about if hits count as 1 (as just stated), but runs count as 2? Meaning, the fantasy team with the most runs gets 24 points, the next best gets 22, and all the way through to the team with the fewest runs getting 2 points. How would I account for a weighted roto setup?
Really appreciate any insight. Thanks.
Especially if it's a keeper league. In keeper leagues other peoples' dollar values are worthless as anything but a general indication of how well they think players will do in a given year.The best exercise you can do is create a spreadsheet that includes a spot for every player at every position to be purchased for your league. For example if you're in a standard 12 team, 23 man roster, $260 cap league you need a spot on your spreadsheet for 12*9 pitchers (108) 12*2 catchers (24)12*1 1B (12)12*1 3B (12)12*1 2B (12)12*1 SS (12)12*1 1B/3B (12)12*1 2B/SS (12)12*1 DH/UTIL (12)12*5 OF (60) for a total of: 12*23 (276) and: 12*$260 = $3120 total budgetYou then fill in all kept players, with their salaries, subtracting them from the initial total budget. The difference remaining is what's available to be spent in your league. You then fill in all the players at the remaining position slots that you believe will be worth at least $1 (sometimes there aren't that many, but you have to put somebody in there because players will be purchased for $1). You adjust your prices up from there until all the remaining money is allocated to values for unkept players.The trick is determining the formula by which you allocate money beyond $1. This is where your projections will apply - everybody's got different formulas (accounting for position scarcity, age, etc.) , but for this to work your formulas need to result in assigning a percentage of the available money to every player you have input as being bid on, not absolute dollars - the individual values of the available players will fall out automatically.As the auction goes along, you'll see players go for more or less than your projected values - you have to adjust on the fly by adding or subtracting $$ from the remaining players to be bid on. Your player valuation calculations should automatically update the values for the remaining players if you've used a percentage based valuation as you adjust the remaining available total budget subsequent to players being purchased.You can try to use other peoples' valuations and back out the percentage based value of the players based on their assigned dollar amount and thus use them as a reference in your valuation, but that is only possible if you know the parameters of the league they're creating the valuations for - namely roster size, position requirements, scoring system and total dollars available. I think most valuations just throw dollars out there without considering any of those things, which makes them essentially useless as anything more than conversation pieces for discussions of this guy thinks player X is better than player Y.I've often thought I should just write this up as a program instead of copying my tired old spreadsheet every year, something like the DD, I've even started coding it a few times, but eventually I realize I've got better things to do with my life, and I figure there's something out there like this already anyway.![[icon]](/data/avatars/m/5/5167.jpg?1660313464){kind=avatar}