FIX: set_montage behavior for DigMontage + deprecate the rest.#6765
Merged
larsoner merged 57 commits intomne-tools:masterfrom Sep 19, 2019
Merged
FIX: set_montage behavior for DigMontage + deprecate the rest.#6765larsoner merged 57 commits intomne-tools:masterfrom
larsoner merged 57 commits intomne-tools:masterfrom
Conversation
4a4a12f to
6598d41
Compare
Codecov Report
@@ Coverage Diff @@
## master #6765 +/- ##
=========================================
+ Coverage 88.23% 89.53% +1.3%
=========================================
Files 421 422 +1
Lines 76301 76408 +107
Branches 12478 12490 +12
=========================================
+ Hits 67325 68415 +1090
+ Misses 6174 5183 -991
- Partials 2802 2810 +8 |
b05bd2c to
1e11b77
Compare
massich
commented
Sep 13, 2019
larsoner
reviewed
Sep 14, 2019
agramfort
reviewed
Sep 14, 2019
agramfort
reviewed
Sep 14, 2019
agramfort
reviewed
Sep 14, 2019
agramfort
reviewed
Sep 14, 2019
f2f0231 to
0469e8b
Compare
|
This pull request introduces 1 alert when merging a3c7d69 into 2545faf - view on LGTM.com new alerts:
|
massich
commented
Sep 16, 2019
7cc31bc to
2fc5963
Compare
agramfort
reviewed
Sep 17, 2019
agramfort
reviewed
Sep 18, 2019
agramfort
reviewed
Sep 18, 2019
agramfort
reviewed
Sep 18, 2019
agramfort
reviewed
Sep 18, 2019
agramfort
reviewed
Sep 18, 2019
agramfort
reviewed
Sep 18, 2019
859d6f8 to
021198f
Compare
jasmainak
reviewed
Sep 18, 2019
3326cff to
bbbf5f6
Compare
bbbf5f6 to
e7f05a2
Compare
Contributor
Author
|
@larsoner This should be good to go, can you do a pass? Thx This PR only deprecates parts of |
Contributor
Author
|
This PR blocks #6764 |
Contributor
Author
|
Does anyone know how can I pinpoint |
Member
|
Failures appear real |
larsoner
reviewed
Sep 19, 2019
Member
|
You are probably running a recent enough Python that dict iteration order is guaranteed. On 3.5 it's not |
8 tasks
larsoner
reviewed
Sep 19, 2019
23aa211 to
046e289
Compare
agramfort
reviewed
Sep 19, 2019
Member
agramfort
left a comment
There was a problem hiding this comment.
besides this LGTM +1 for MRG if CIs are happy
alexrockhill
pushed a commit
to alexrockhill/mne-python
that referenced
this pull request
Oct 1, 2019
…ools#6765) * TST: reveal issues * TST: Add a test describing current status * Add example modifying montage names * TST: Add test showing how to set mismatching montages * TST: set up the sub/super set behavior * WIP: set_montage for DigMontage (with and without ref) * ENH: use view * TST, BUG-FIX: Adapt tests to the new set_montage. (new is good) * WIP, TST: start working with getting a propper info_'dig'_ * wip (I'm doing something wrong) * wip * done. todo: fix deprecationwarn in generator * fix: StopIteration Deprecation warning * wip * FIX: HPI was FIFF_EEG_CH, but somewhere I've seen EEEG_REF being same * clean up * WIP: remove the generator * check set_dig * FIX: test_fif_dig_montage * WIP: bypass set_montage in egi test * WIP: bypass set_montage in bvct * wip: fix bvct (second test) * WIP: better error handling. it will simplify the TST + backcompat * wip * WIP: I can do pick_types with including the bad channels * Fix * FIX: just selecting all eeg_like should make the trick * WIP: Add transformation to head in set_montage when necessary * TST: revert the funky _egi_set_montage and do a pass on the egi test * TST: revert the funky _set_montage for bvct * WIP: fix some * FIX: fieldtrip, but it might be a BUG * wip * FIX: avoid using _coord_frame * remove example * WIP: Add deprecation * FIX some deprecations * BUG: Brainvision * wip * wip * WIP: use _fix_montage in eeglab * wip * wip * wip * wip: eeglab * wip: fixing more * revert * montage is not needed to test ica * ups I deleted the wrong file * FIX: deprecations * thats funny * update whats_new * clean-up * FIX: A few more * FIX: Old NumPy * FIX: More * FIX: Old NumPy is annoying
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR reviews the behavior of setting a DigMontage:
1 - what happens if
info['ch_names']andmontage.ch_namesare different versions of the same (i.e:'EEG 001'and'EEG001')?crashes. This needs to be taken care of by the user.
2 - what happens when montage is a sub/super set of info?
* supper set case: warns, sets up
info['ch_pos']andinfo['dig']for the ch_names already in info* subset case: crashes.
3 - requires
montageto be in'head'(or being able to be transformed in'head'). Crashes otherwise.cc: @agramfort, @larsoner