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

Fixing problem with inconsistent signal line colours #48

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

eshwen
Copy link
Contributor

@eshwen eshwen commented Oct 19, 2020

Fix for #42

Very small change, but I think requires a colour to be tied to the signal process (e.g., with an entry in the dataset_colours block or in the dataset_order block) to work properly. I don't think it will default to using the "original" colours (i.e., from matplotlib's tab10 colourmap) if neither of the above blocks are specified

…re colours defined in plotting configs for signal
@@ -140,7 +140,7 @@ def __call__(self, col, **kwargs):
width = self.linewidth
style = "-"
else:
color = None
color = color
Copy link
Contributor

Choose a reason for hiding this comment

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

Could you do something like color if color else None?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, I can try that. Seems like an easy enough change

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ahh, that doesn't work as intended. If there's no colour tied to a dataset, it's given one from the default colourmap (nipy-spectral, not tab10)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants