Originally posted by irishrebels44
View Post
-
Good question... no, it's not 19+4=23. In order to not have the projections overreact to early performances, we actually have them ignoring early performance altogether. So that's why we're showing 19+4=23 right now. Starting in the next couple of days, we'll blend YTD+Proj projections together. But we're not doing that yet at all, which is why you're seeing what you're seeing. -
I just posted a similar question. If for instance B Belt had a preseason HR projection of 19 for the season. He hits 4 HR in the first week, now his season projection jumps to 23 (19+4)? I am trying to get my arms around this. It seems like an overreaction to week 1 stats, but if that is what you guys say to do then I will be all in on your advise, just let me know for sure, thanks!!Leave a comment:
-
While that might be good in theory, I doubt it would help much for people who have made any transaction since the beginning of the year. For example, if I have to DL Zimmerman and pick up some one to replace him for a few weeks, the tracker can't account for that without a great deal of input.Leave a comment:
-
MACK team tracker--projected stats
If I understand correctly, the projected stats are remainder of season stats. So to get total end of season projections--which are useful for figuring end of season standings projections--I need to add the season so far stats to the projected stats.
For example, if I want to know how many HR my team projects to have come the end of the season, I need to add to the 4 my guys have hit thus far their projected 256 for the remainder of the season.
It might be useful to have the option to generate total season projections as part of a report. I know I would find that useful, although it is hardly a pressing need.
Thanks!
Leave a comment: