[MRG, MAINT] Move freesurfer functions in mne/source_space.py to mne/_freesurfer.py#9543
[MRG, MAINT] Move freesurfer functions in mne/source_space.py to mne/_freesurfer.py#9543larsoner merged 11 commits intomne-tools:mainfrom
mne/source_space.py to mne/_freesurfer.py#9543Conversation
|
I don't think this should get a |
|
|
You know a lot better about where things go than I do, sounds good as far as naming. |
mne/source_space.py to mne/_freesurfer.py
… freesurfer functions
|
Ok @larsoner, this turned out to take a lot more changes than I thought. Now I get a circular import that |
|
Let's just scale back, there is also a cost to moving things in terms of tracking blame and changes, and the tangible benefit is also small |
|
... but now having read the PR's diff it is nice to have all this stuff in one place. I'll see if I can push a commit to fix the circular import problem |
|
I think the core problem is |
|
there is no public API change here? |
The only one would be that |
| :toctree: generated/ | ||
|
|
||
| get_mni_fiducials | ||
| coreg.get_mni_fiducials |
There was a problem hiding this comment.
That looks like it is the API that it was before, I just corrected it because it would have been a change but instead we just imported and noqa'd to shallow reference it in coreg
agramfort
left a comment
There was a problem hiding this comment.
@larsoner merge if happy
thx @alexrockhill !
|
Thanks @alexrockhill ! |
Helps with refactoring for #9520.
The freesurfer lookup table access seems oddly placed in
source_space.py. I thinkutils.config.pymakes sense because that is whereget_subjects_diris.This would allow the lookup table to be accessed for plotting ROIs in other modules.