-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
ENH: New interface for Coregistration #8833
Comments
@GuillaumeFavelier as the next step, can you separate into blockers for 0.24 and non-blockers for 0.24, perhaps working with @agramfort and @hoechenberger ? To me it's just the initial-startup bug I added to the list. |
Alright, I'll update the original post and take care of this bug in priority 👍 |
@GuillaumeFavelier - thanks so much for this refactoring. I'm really looking forward to leaving behind mayavi for coreg. In updating some of my code, i ran into an issue with the auto coreg method and CTF data. CTF doesn't have unique HPIs (they use nas/lpa/rpa) and the current code assumes these are not None and tries to update them. Below is an MWE that throws
This patch moves past the error allowing CLI coregistration, but I don't know how it interacts with the work you're doing in the GUI or if there is another way you would want to solve the issue so didn't want to open an separate PR.
Best, |
The new gui also has a small backward compatibility issue. The old mayavi GUI supported fif files that only contained dig points. mne-python/mne/gui/_file_traits.py Lines 310 to 318 in b579d32
The new gui has replaced this with a Lines 335 to 336 in dac4f16
which crashes out on these files.
Let me know if you'd like a PR with these two bug fixes, I just don't want to complicate stuff you are already working on. |
I'd say go for it @bloyl ! |
@GuillaumeFavelier given that we plan to cut 0.24 next week (preferably early), do you think the list above marked for 0.24 is realistic? |
Indeed, early next week is unrealistic for all of those. |
Okay, I'll bump those to 1.0. I think it's okay if a few of these features lag |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I removed the item:
assuming that it's among the parameters ( |
This PR summarizes the ideas to implement for
coreg
:Milestone 1.0
project_eeg
parameterscale_by_distance
parametermark_inside
parameterBonus territory:
trans
to mne.gui.coregistration() should automatically derive the MRI fiducials #10208 (comment))trans
is not saved (Coreg GUI should suggest to save fiducials and trans if not saved during interactive session #10236)Milestone 1.1
object_fit='contain'
andobject_position='top'
(ipywidgets) (How to get the correct event position when object_fit='contain'? Kitware/ipyvtklink#35, How to obtain the coordinates of a click on the image when object_fit='contain'? mwcraig/ipyevents#71)Done
add support for the(YAGNI)guess_mri_subject
parameteradd support for the(YAGNI)head_inside
parameterCoregistration()
to require parameters (https://mne.discourse.group/t/mne-coreg-based-on-ctf-data/3022/4)pyvista
(done in ENH: Coreg GUI #9689)Bugs
_configure_status_bar()
(Windows)FIFF
(Windows)trans
(ipywidgets)The text was updated successfully, but these errors were encountered: