Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team 25 match predictions #6

Open
7 of 13 tasks
spencerng opened this issue Feb 19, 2019 · 0 comments
Open
7 of 13 tasks

Team 25 match predictions #6

spencerng opened this issue Feb 19, 2019 · 0 comments
Assignees
Labels

Comments

@spencerng
Copy link
Member

spencerng commented Feb 19, 2019

  • Write a method in EventReport that outputs a text file containing the quick alliance report of all alliances in our (team 25's) future matches. To do this, you may
    • Determine the "current" match number based on the scout entries
    • Read from (and download if necessary and Internet is available) the match schedule CSV file
    • Determine the teams on our alliance and the teams on the opposing alliance using string splitting
    • Create a new AllianceReport with those teams and call the method to return a quick status string (this isn't finished right now, but assume it works)
    • Concatenate the quick status strings into one string
    • Include headers indicating the match number of the two alliance predictions between each set of predictions
    • Output the string to a text file called Predictions - M<current match number> - <event key>.txt
  • Write a method in EventReport that outputs the expected number of ranking points earned by each team in future matches
    • Once again, read the match schedule CSV as a string and parse through it
    • For each alliance, assume that a method getExpectedRankingPoints() exists in the AllianceReport class that returns a double
    • Add up the future ranking points for each team based on their alliances. You may want to use a HashMap to help with this
    • Output a text file with the predicted ranking points, with one team on each line, followed by their expected number of RP. This list should be sorted in descending order (by predicted RP)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants