-
Notifications
You must be signed in to change notification settings - Fork 69
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
Improve documentation and config validation of loose
and depth
parameters; drop support for loose=None
#915
Conversation
Eventually we could pretty easily add support for volumetric source estimates I think. So I'm not sure it's worth getting rid of |
I agree about keeping the loose and depth parameters, we do use them sometimes. |
loose
and depth
parameters; drop support for loose=None
@larsoner @SophieHerbst This, of course, introduces an inconsistency with MNE, which allows for Thoughts? |
loose
and depth
parameters; drop support for loose=None
loose
and depth
parameters; drop support for loose=None
I have always found the options for those parameters a bit confusing, so I am fine with removing the None. |
Okay with me to remove |
Co-authored-by: Eric Larson <larson.eric.d@gmail.com>
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.
Marking for merge when green, thanks in advance @SophieHerbst !
Whoops wrong PR comment, thanks @hoechenberger ! |
* upstream/main: change default for info to use for inverse mne-tools#905 (mne-tools#919) Improve documentation and config validation of `loose` and `depth` parameters; drop support for `loose=None` (mne-tools#915) enhance documentation of caching, continuation of mne-tools#914 (mne-tools#918) [pre-commit.ci] pre-commit autoupdate (mne-tools#917) Restructure configuration options documentation sections (mne-tools#914) Try to fix documentation deployment (mne-tools#913) Do not show `Annotated` types in configuration options documentation (mne-tools#911) Add number of subjects to grand-average report (cont'd) (mne-tools#910) MAINT: Ensure input changes cause output changes (mne-tools#904) Render type annotations in the documentation again (mne-tools#909)
@larsoner @SophieHerbst WDYT?
We currently don't support volumetric or mixed source spaces anyway, so I thought we could simplify things a little.
I was even considering entirely removing the
loose
anddepth
settings but then wasn't sure if some of you might be using them sometimes? Personally I never touch those.Before merging …
docs/source/changes.md
)