remove degenerate _scans.tsv files?

[yarikoptic]

reading bids specification https://bids-specification.readthedocs.io/en/stable/common-principles.html#compulsory-optional-and-additional-data-and-metadata

It is RECOMMENDED that non-compulsory metadata fields (like `notch` in `channels.tsv` files)
and/or files (like `events.tsv`) are fully omitted *when they are unavailable or unapplicable*,
instead of specified with an `n/a` value, or included as an empty file
(for example an empty `events.tsv` file with only the headers included).

it is just RECOMMENDED so we do not really have to do that ;)

[jungheejung]

@yarikoptic That's interesting. Thanks for the heads up. Do you think this is realistic though? We're getting BIDS warnings for missing _scans.tsv files.

FAQ. Why would a complete _bold but 'n/a' filled _scans.tsv be a valid case? Not every analysis requires a _scans.tsv metadata. We had a discussion with other data users - Given that some are interested in naturalistic paradigms and hyperalignment, these analyses are not contingent on scans.tsv files. Users were in favor of more data, rather than deleting bold due to a degenerate scans.tsv