...
The output datatype of the App that detects bad channels is meg/fif-override (see https://brainlife.io/datatype/608195ce89df435fd26893c1), but as pointed out here Où stocker l'information "bad channels", MNE Python functions used the info stored in raw.info['bads']. So, we need to update raw.info['bads']with the info of channels.tsv. If raw.info['bads'] is not compliant with the info of channels.tsv, a warning is displayed to the user to tell him that, by default, only bad channels from channels.tsv are considered as bad: the info of his MEG file will be updated with those channels. The comparison between channels.tsv and raw.info['bads'] is performed at the beginning of each App thanks to helper.py (see Create a helper.py file).
Is it a good idea to display this warning message? It can confused the users (they don’t have to know that channels info can be stored in raw.info.
Events.tsv
The events info is stored in raw.info['events'], but this info shouldn’t be manually changed, it is changed by the MNE Python function:
...