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
MRG, BUG: Fix EDF header parsing #8558
Conversation
Looks good, thanks for this! The part you're asking about refers to this section: # Populate edf_info
edf_info.update(
ch_names=ch_names, data_offset=header_nbytes,
digital_max=digital_max, digital_min=digital_min,
highpass=highpass, sel=sel, lowpass=lowpass, meas_date=meas_date,
n_records=n_records, n_samps=n_samps, nchan=nchan,
subject_info=patient, physical_max=physical_max,
physical_min=physical_min, record_length=record_length,
subtype=subtype, tal_idx=tal_idx) In my local copy, I added Also, if you want to do some more extensive testing of the new header parsing you can base it off the tests I wrote for mne-bids here: The MNE test .edf and .bdf files I looked at don't seem to have any of those header fields actually filled out, so manually adding the header info pre-test might be useful! EDIT: To answer your other question, yes the Github link you used for me is fine! |
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.
LGTM, let me know if you want me to take a look at the missing feature once you've implemented it.
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.
LGTM overall once Clemens' comments are taken into account
It gets passed into a dict that ends up living only in a private attribute |
@cbrnr made the tests more complete, should cover what you asked about |
@larsoner did you push the changes? |
nope, forgot the |
gitter
(1 line)XXX
for carrying overedf_info['subject_info']
toraw.info['subject_info']
, which we should probably do to the extent possible (but in another PR)@a-hurst the one thing I didn't follow was (what is keeping this WIP from my end):
Can you take a look, and clarify what needs to change in / be added to this PR? And let me know if you're happy with the GitHub URL I put for your name link?
@sappelhoff @cbrnr can you look to see if this makes sense in light of discussions in #8544?
Closes #8544
Closes #8551