-
Notifications
You must be signed in to change notification settings - Fork 10
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 topomaps. #130
Fixing topomaps. #130
Conversation
Rebased with main, fixed conflicts from changes in this PR. I always accepted the changes in THIS PR, and formated with black after accepting the change.
These last couple fixes will make our topomaps look like MNEs. It mainly had to do with some logic to handle the cmap and vmin/vmax
I pushed a couple commits to get this PR over the line, our topoplots now match those produced by MNE. Using one of our pylossless test files:
MNE: and then selecting @christian-oreilly just give me a thumbs up if you agree that this looks like it solves the problem. FYI see commit 3dd5988 for the code I added. Then there's just a failure in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor suggestions
Note: that there is also a typo here (color should be |
We should initiate the cmap as None instead of "Red_bl" (sic), so that our code logic can handle the color scheme based on the IC values just like MNE does
Nice job. Yes, I agree, these topomaps now seem to be identical. I suspect that the CI issue is the same one discussed in the context of the "rejection policy" PR, which seems to have nothing to do with either PR. |
The test failure is related to this PR: It was caused by the change committed to |
Oh... sorry about that. I just assumed. I should not have assumed without taking some time to check. I must say that I don't remember why I changed it that way. I think our tests should guide us there... I'd go with your reverting of this change if it allows all tests to pass. We can always change this back later (adding corresponding tests) if we come up with a use case that requires this change... |
No worries, it has been quite some time since we worked on this! I already checked, and reverting the specific change to |
Codecov Report
@@ Coverage Diff @@
## main #130 +/- ##
==========================================
- Coverage 77.63% 68.33% -9.30%
==========================================
Files 12 14 +2
Lines 921 960 +39
==========================================
- Hits 715 656 -59
- Misses 206 304 +98
... and 6 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
I'm trying to get our code coverage to be ever increasing and there are missed lines in the added code. Will have to loop back to this when we have time. |
@scott-huberty Can we merge this? I need it to be merged before forking this repo to start splitting the dash components into CONIE. |
@christian-oreilly sure, but can you commit my suggestions before? Note that |
Co-authored-by: Scott Huberty <[email protected]>
Co-authored-by: Scott Huberty <[email protected]>
Co-authored-by: Scott Huberty <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed and committed suggestions.
Fix #129