[MRG] Adding status_description to channels.tsv files defaulting to n/a for now

[adam2392]

PR Description

Closes: #348

Defaults to n/a for now to allow for easy grepping as @jasmainak suggested. Future improvements can be made that allow the status to change, pending an addition to mne-python, or implementation of #458

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-commenter]

Codecov Report

Merging #489 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #489   +/-   ##
=======================================
  Coverage   92.79%   92.79%           
=======================================
  Files          14       14           
  Lines        1970     1971    +1     
=======================================
+ Hits         1828     1829    +1     
  Misses        142      142           

Impacted Files	Coverage Δ
mne_bids/write.py	96.75% <100.00%> (+<0.01%)	⬆️

---

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 fd2fa56...343d318. Read the comment docs.

[hoechenberger]

I missed the discussion in #348, but since I've started working on #491 I'm wondering why you would want to fill it with n/a instead of empty strings?That's what I'm doing in #491 and I feel that that's the "better" way, because … well I feel that this string field should be empty if there's no explicit value set …

[adam2392]

I missed the discussion in #348, but since I've started working on #491 I'm wondering why you would want to fill it with n/a instead of empty strings?That's what I'm doing in #491 and I feel that that's the "better" way, because … well I feel that this string field should be empty if there's no explicit value set …

I think either value works, so can change it. That should pass the bids-validator right?

[hoechenberger]

I think either value works, so can change it.

Let's see what the others think :)

That should pass the bids-validator right?

Hah, thanks for the reminder. I forgot to include BIDS validation in #491. Let's see…

[hoechenberger]

Hah, thanks for the reminder. I forgot to include BIDS validation in #491. Let's see…

Ok so this is resolved now… won't pass the validation with an empty cell, so I'm using n/a now in #491 too as a default! :)

[hoechenberger]

LGTM!

[hoechenberger]

@sappelhoff Feel free to merge if you're happy

[agramfort]

+0 on my side. I did not follow discussion.

@sappelhoff @jasmainak ball is in your hands

[sappelhoff]

LGTM -> doesn't hurt and will come in helpful when we have TSV + JSON updating functions

won't pass the validation with an empty cell, so I'm using n/a

yes, n/a is good here. 👍

[sappelhoff]

thanks @adam2392