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

Fix the data set dimensions for the sdvplot. #1130

Merged
merged 6 commits into from
Oct 10, 2017

Conversation

drvinceknight
Copy link
Member

@drvinceknight drvinceknight commented Oct 9, 2017

This closes #1129.

I could not find anything in the release notes
http://matplotlib.org/users/whats_new.html however I think this is due to the fact that mpl 2.1 got rid of the ability to handle the unflattened sub list (so this fix will still work with previous versions of mpl).

This closes #1129.

I could not find anything in the release notes
<http://matplotlib.org/users/whats_new.html> however I think this is due to the fact that mpl 2.1 got rid of the availability to handle the unflatten sub list (so this fix will still work with previous versions of mpl).
@drvinceknight
Copy link
Member Author

Investigating why coverage would have dropped...

This version seems to cover all our needs and is still ensuring
coverage. As hypothesis seems to be developing/changing this just makes
things easier for us.
axelrod/plot.py Outdated
@@ -112,7 +112,8 @@ def _sd_ordering(self):
@property
def _sdv_plot_dataset(self):
ordering = self._sd_ordering
diffs = self.result_set.score_diffs
diffs = [[diff for repetition in diffs for diff in repetition]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is confusing, can we use different iteration variables?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I picked these in an attempt to not be confusing but happy to take any suggestions.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

91a3ee8 renames them to what is hopefully less confusing but still happy to change further if you think it can be improved 👍 :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's still a little confusing since player and opponent usually indicate instances of Player classes. But it's better than before in that I can see what it's doing now.

@@ -255,8 +255,8 @@ def _run_parallel(self, processes: int=2) -> bool:
"""
# At first sight, it might seem simpler to use the multiprocessing Pool
# Class rather than Processes and Queues. However, this way is faster.
work_queue = Queue()
done_queue = Queue()
work_queue = Queue() # type: Queue
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I think it's supposed to be two spaces before the #.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. Have fixed.

@drvinceknight
Copy link
Member Author

Merging. Will do a new release :+1

@drvinceknight drvinceknight merged commit 446a3b9 into master Oct 10, 2017
@marcharper marcharper deleted the fix-matplotlib-incompatibility branch August 17, 2018 02:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Plot incompatibility with mpl 2.1
3 participants