Robert Oostenveld
Robert Oostenveld
We should check what the consequences of https://github.com/Lestropie/bids-specification/pull/5 or https://github.com/bids-standard/bids-specification/pull/1003 would be for FieldTrip.
This makes it more clear that there is a 2mm and a 1mm version.
The following code does not result in the expected visualization. This relates to test_bug3375.m and http://bugzilla.fieldtriptoolbox.org/show_bug.cgi?id=3375. It seems that not all data objects are expressed in the same coordinate system....
On https://bids-specification.readthedocs.io/en/stable/04-modality-specific-files/02-magnetoencephalography.html#sidecar-json-_megjson under Manufacturer it specifies `Elekta/Neuromag`, whereas on https://bids-specification.readthedocs.io/en/stable/99-appendices/07-meg-systems.html#appendix-vii-meg-systems it specifies `Neuromag/Elekta/Megin`. I believe the latter to be more appropriate.
@schoffelen I wonder whether we should do this more explicitly for other file formats as well. We don't encounter this problem very often, but this certainly not the first time....
This fixes #2084 as for `cfg.README` it now includes the default template from the starter kit.
- added check that the user did not specify leadfield options in case the input already contains the leadfield - added check that the user did not specify a regularization...
Following https://github.com/fieldtrip/website/issues/723 I wanted to add the FieldLine alpha1 layout to the website, which made me realize that the https://www.fieldtriptoolbox.org/template/layout/ page was not well organized. The ToC on the right...