-
Notifications
You must be signed in to change notification settings - Fork 34
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
[WIP] Enable save/read, simplify "combine" kwarg and allow symmetric RAM optimization #20
Conversation
Looks like I'm getting hit by an error that I can't reproduce locally, but only on Ubuntu and some Mac distros:
Will need to do some googling... |
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.
Regarding the error: looks like the attributes are making trouble?
conn = EpochTemporalConnectivity( | ||
data=corr, | ||
names=names, | ||
times=times, | ||
method='envelope correlation', | ||
indices=indices, | ||
indices='symmetric', |
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.
Why do you set it explicitly here when it is only set to 'symmetric'
if indices is None
in line 166? If output is always symmetric, are line 165-166 even needed?
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.
I was thinking of enabling indices
to allow for a subset to be computed, since any connectivity function that is a bivariate function f(signal_1, signal_2)
can allow for indices
to define a subset.
Then this line would be needed since the default would be "all-to-all symmetric". WDYT?
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.
Ah, so you are anticipating future functionality?
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.
Yep!
Well... now that you bring it up, I probably should've just implemented it first. But yeah figured this is the way the code will look like once I add lines to account for indices = ([...], [...])
.
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.
Going to try adding now that I've addressed the other comments.
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.
Actually, upon re-reading the code, idk if that's worth doing.
Envelope correlation is already very easy to get, so idk if it's worth adding the indices
unless it comes up.
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.
Going to table this and move onwards w/ other connectivity functions and examples. I figure we can add these niceties if ppl really want them later on.
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.
Sounds good!
Co-authored-by: Eric Larson <larson.eric.d@gmail.com> Co-authored-by: Britta Westner <britta.wstnr@gmail.com>
Ah looks like "netcdf4" library needs to be added into the requirements files :p |
…RAM optimization (mne-tools#20) * Adding reading/writing capability with netCDF4 files * simplified "combine" argument in `envelope_correlation` * allow storage of symmetric connectivity
PR Description
Closes: #16
Closes: #18
Closes: #10
combine
in theenvelope_correlation
function intoEpochXXX
Merge checklist
Maintainer, please confirm the following before merging: