MRG: Suppress MaxShield warning in many places #1000
Merged
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.
When reading FIFF files that contain Neuromag data recorded with active shielding enabled, MNE-Python by default raises an exception unless
allow_maxshield
is specified. We used to set it toTrue
in all applicable places. However, this would still issue a warning.Setting it to
'yes'
instead suppresses this warning.Consequently, I've changed all but one occurance of
allow_maxshield
to'yes'
now. The only exception is inread_raw_bids()
, where I believe it still makes sense to issue the warning. For all other places,like
write_raw_bids()
,get_head_mri_trans()
etc., the warning is gone now.Merge checklist
Maintainer, please confirm the following before merging: