We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am trying to run a k simulations with more than two teams and am receiving this error:
ValueError: Shape of passed values is (30, 2), indices imply (30, 3)
I tracked it down to this line in _battle.simulate_k
runs = np.zeros((k, 2), dtype=np.int64)
it is assuming the results have only two teams. I think a quick fix is to change to the below which is the number of teams:
runs = np.zeros((k, np.unique(self._teams).shape[0]), dtype=np.int64)
the team_counts results returned by simulate_battle contain a records for each unique team in M.
This appears to work for up to 30+ teams/allegiances
The text was updated successfully, but these errors were encountered:
Fix Error in simulate_k with more than two teams #4
d6f2f6c
Thank you for this issue.
Changes have been made as you suggested:
Please pull the latest, and re-build your version using the Anaconda instructions, or via pip3 install . within a suitable environment.
pip3 install .
Sorry, something went wrong.
No branches or pull requests
I am trying to run a k simulations with more than two teams and am receiving this error:
ValueError: Shape of passed values is (30, 2), indices imply (30, 3)
I tracked it down to this line in _battle.simulate_k
runs = np.zeros((k, 2), dtype=np.int64)
it is assuming the results have only two teams. I think a quick fix is to change to the below which is the number of teams:
runs = np.zeros((k, np.unique(self._teams).shape[0]), dtype=np.int64)
the team_counts results returned by simulate_battle contain a records for each unique team in M.
This appears to work for up to 30+ teams/allegiances
The text was updated successfully, but these errors were encountered: