Skip to content

Noisy resolution matrix - #11092

Open
olafhauk wants to merge 39 commits into
mne-tools:mainfrom
olafhauk:noisy_resolution_matrix
Open

olafhauk wants to merge 39 commits into
mne-tools:mainfrom
olafhauk:noisy_resolution_matrix

Conversation

@olafhauk

Copy link
Copy Markdown
Contributor

Thanks for contributing a pull request! Please make sure you have read the
contribution guidelines
before submitting.

Please be aware that we are a loose team of volunteers so patience is
necessary. Assistance handling other issues is very welcome. We value
all user contributions, no matter how minor they are. If we are slow to
review, either the pull request needs some benchmarking, tinkering,
convincing, etc. or more likely the reviewers are simply busy. In either
case, we ask for your understanding during the review process.

Again, thanks for contributing!

Reference issue

Implements #11058

What does this implement/fix?

Added "noisy resolution matrix" for inverse operators.

Additional information

Work in progress, just for initial review.

@drammock
drammock marked this pull request as draft August 26, 2022 09:18
@olafhauk

Copy link
Copy Markdown
Contributor Author

This is just to get started where I left off last year.

@olafhauk
olafhauk marked this pull request as ready for review November 14, 2023 09:33
@olafhauk
olafhauk marked this pull request as draft November 14, 2023 09:34
@larsoner

Copy link
Copy Markdown
Member

@olafhauk would it help if I pushed a commit to fix the conflicts so that locally you can do git pull origin noisy_resolution_matrix and have no more conflicts? Conflict resolution is probably the worst part about git/GitHub...

@wmvanvliet wmvanvliet left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks super good already @olafhauk! Just some questions.

Comment thread mne/minimum_norm/resolution_matrix.py Outdated
Note: If the resolution matrix is computed with a noise covariance
matrix then only its columns, i.e. PSFs, can meaningfully be
interpreted. It must not be used to compute CTFs or resolution metrics
for CTFs!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps this explanation of the role of the noise parameter is best moved to the "main" section of the documentation, above the Parameters subheading. Right now, the main section is only a single line, and then the lines describing the parameters and return values are filed with a large amount of text.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll think about this later. I agree currently it may be confusing.

Comment thread mne/minimum_norm/resolution_matrix.py
idx_ch_types = {}
idx_ch_types["eeg"] = pick_types(info, eeg=True, meg=False)
idx_ch_types["mag"] = pick_types(info, eeg=False, meg="mag")
idx_ch_types["gra"] = pick_types(info, eeg=False, meg="grad")

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would there ever be a scenario that there would be other sensor types as well? Perhaps not.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know - are there other sensor types? How are OPMs dealt with?
Is there a method to get all sensor types from info and loop through them?

@olafhauk

Copy link
Copy Markdown
Contributor Author

@olafhauk would it help if I pushed a commit to fix the conflicts so that locally you can do git pull origin noisy_resolution_matrix and have no more conflicts? Conflict resolution is probably the worst part about git/GitHub...

@olafhauk olafhauk closed this Nov 15, 2023
@olafhauk

Copy link
Copy Markdown
Contributor Author

I just managed to close the pull request. Is there a way to reopen it, or should I create a new one?

@larsoner larsoner reopened this Nov 15, 2023
@larsoner

Copy link
Copy Markdown
Member

In principle I think you also had a "Reopen pull request" button but in case you didn't, I did so I used it :)

@olafhauk

Copy link
Copy Markdown
Contributor Author

In principle I think you also had a "Reopen pull request" button but in case you didn't, I did so I used it :)

Thank you. Good to be back ;-)

Comment thread mne/minimum_norm/resolution_matrix.py Outdated
Comment thread mne/minimum_norm/resolution_matrix.py Outdated
Comment thread mne/minimum_norm/resolution_matrix.py
@olafhauk
olafhauk marked this pull request as ready for review November 21, 2023 12:42
@wmvanvliet

Copy link
Copy Markdown
Contributor

@wmvanvliet wmvanvliet self-assigned this Jan 29, 2026
@wmvanvliet wmvanvliet added the ENH label Jan 29, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants