This library really hasn't done much with sets of lineups - there were some attempts in 2018 to do cumulative ownership (mins and maxes). My take after doing that was people have lots of different ideas on expected behavior when it comes to aggregate settings for say 150 lineups in a mini-MAX DK contest.
Rather than try to address all those opinions, I think starting with a basic LineupSet object may make sense and adding some read-only properties like:
player_frequency (frequency dictionary)
team_frequency
And maybe funcs like:
appearance_frequency(**players)
This to an extent is already there with the run_multi work, but I think there could at least be some clean up and docs additions.
This library really hasn't done much with sets of lineups - there were some attempts in 2018 to do cumulative ownership (mins and maxes). My take after doing that was people have lots of different ideas on expected behavior when it comes to aggregate settings for say 150 lineups in a mini-MAX DK contest.
Rather than try to address all those opinions, I think starting with a basic
LineupSetobject may make sense and adding some read-only properties like:player_frequency(frequency dictionary)team_frequencyAnd maybe funcs like:
appearance_frequency(**players)This to an extent is already there with the
run_multiwork, but I think there could at least be some clean up and docs additions.