Switch from epoch_data to data for TFR array functions
#12308
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.
Follow-up of #12305.
As discussed, I have just switched the
epoch_dataparameter for thetfr_array_morletandtfr_array_multitaperfunctions todata, and have added aFutureWarningifepoch_data is not None.The
_compute_tfrfunction which is called internally has theepoch_dataparameter, but I haven't touched that here.mne-python/mne/time_frequency/tfr.py
Lines 417 to 431 in b1dd84c