Skip to content
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] KIT data now goes in the meg folder #187

Closed

Conversation

monkeyman192
Copy link
Contributor

@monkeyman192 monkeyman192 commented Mar 28, 2019

PR Description

closes #186

Merge checklist

Maintainer, please confirm the following before merging:

  • All comments resolved
  • This is not your own PR
  • All CIs are happy
  • PR title starts with [MRG]
  • whats_new.rst is updated
  • PR description includes phrase "closes <#issue-number>"
  • Commit history does not contain any merge commits

@codecov-io
Copy link

codecov-io commented Mar 28, 2019

Codecov Report

Merging #187 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #187      +/-   ##
==========================================
- Coverage   95.48%   95.46%   -0.02%     
==========================================
  Files          17       17              
  Lines        1218     1214       -4     
==========================================
- Hits         1163     1159       -4     
  Misses         55       55
Impacted Files Coverage Δ
mne_bids/tests/test_mne_bids.py 99.55% <ø> (-0.01%) ⬇️
mne_bids/mne_bids.py 94.77% <100%> (ø) ⬆️
mne_bids/io.py 98.48% <100%> (-0.07%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a5475df...e27b681. Read the comment docs.

@monkeyman192 monkeyman192 changed the title KIT data now goes in the meg folder [MRG] KIT data now goes in the meg folder Mar 28, 2019
@jasmainak
Copy link
Member

how is the CI passing? is the validator already updated? and if so, how was it passing before?

@monkeyman192
Copy link
Contributor Author

I think the validator can handle having raw files in a sub-folder or not. I don't think it was coded to require KIT data to be specifically in a sub-folder (haven't checked the code though, just assuming because it does pass...)

@sappelhoff
Copy link
Member

I think the validator can handle having raw files in a sub-folder or not. I don't think it was coded to require KIT data to be specifically in a sub-folder

I think so as well ... the validator is not checking thoroughly in some parts ... and for other parts it's annoyingly accurate ...

@jasmainak
Copy link
Member

right, but then all the discussion is a waste since nothing forces them to stick one way or another ...

but since we have round trip I/O now, we don't rely on validator that much for the tests. So, I'm okay merging this.

@@ -685,7 +685,8 @@ def write_raw_bids(raw, bids_basename, output_path, events_data=None,
channels_fname = make_bids_basename(
subject=subject_id, session=session_id, task=task, run=run,
acquisition=acquisition, suffix='channels.tsv', prefix=data_path)
if ext not in ['.fif', '.ds', '.vhdr', '.edf', '.bdf', '.set']:
if ext not in ['.fif', '.ds', '.vhdr', '.edf', '.bdf', '.set', '.con',
'.sqd']:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should eventually just change it to ext in blah. This is so confusing ...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the only ext now that should be in that list is .pdf right? Just wanting to finish off this PR...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so ...

@sappelhoff
Copy link
Member

right, but then all the discussion is a waste since nothing forces them to stick one way or another ...

yes, we should make an issue on the validator :-) (go for it!)

@sappelhoff
Copy link
Member

What's the status on this issue @jasmainak @monkeyman192 ?

@jasmainak
Copy link
Member

We need to:

  1. need to update the conditional
  2. make an issue on bids validator to check this

@teonbrooks
Copy link
Member

@jasmainak @sappelhoff, we should get this included in the release.

@jasmainak
Copy link
Member

jasmainak commented Apr 26, 2019 via email

@sappelhoff
Copy link
Member

I'll include it in #196 but @jasmainak --> what do you mean by "need to update the conditional"? In your comment

@sappelhoff sappelhoff mentioned this pull request Apr 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove sub-folder generation for a number of manufacturers
5 participants