Daniel McCloy
Daniel McCloy
thx @larsoner
> An alternative would be to just store the taper weights in the `*TFR` objects, which is similar to how this is now handled for `*Spectrum` objects. However, the weights...
> Just to clarify, for the proposed connectivity function changes, users would still only be able to pass in arrays of epoched timeseries data, not epoched coefficients. If we change...
> So if we wanted to return the weights computed in `_make_dpss()` to the `*TFR` object, a new param would be needed in `tfr_array_multitaper()`. I find this acceptable. The `tfr_array_*()`...
> since this is a distinct thing to adding a `weights` attr, I wasn't sure if people would prefer these in separate PRs, or should I handle all of this...
internally, default (plotting/axis-label) unit for `pupil` is µm https://github.com/mne-tools/mne-python/blob/6ad882335644fb80f8744e508387c52f7231553a/mne/defaults.py#L96 and accordingly the default scaling is 1e6: https://github.com/mne-tools/mne-python/blob/6ad882335644fb80f8744e508387c52f7231553a/mne/defaults.py#L125 therefore `_handle_default("scalings", None)` (which is what `to_data_frame()` method uses internally when no scalings...
This may not be very easy I suspect. The page elements that end up shown under "on this page" are `h2`, `h3` etc. The class methods are `dt` elements. This...
> About making `_XdawnTransformer` class public: I moved it to decoding and removed the `_`. But if I understood you correctly the last time, there are additional steps in making...
Creative commons licenses are appropriate for data(bases). https://creativecommons.org/faq/#can-databases-be-released-under-cc-licenses
> What would speak against having individual licenses for each "dataset"? nothing is in principle wrong with that. But we'd still need to track down the contributors to find out...