spelling

fieldtrip · Jun 1, 2024 · 3210214 · 3210214
1 parent 2f6d470
commit 3210214
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 2 deletions.
diff --git a/assets/wordlist-ignore.txt b/assets/wordlist-ignore.txt
@@ -389,6 +389,7 @@ Cz
 Czienskowski
 DAC
 DANDI
+DAQ
 DBS
 DCBT
 DCC
@@ -1040,9 +1041,13 @@ Lashkari
 Lastname
 Lau
 Laure
+Layx
+Layy
+Layz
 Lazar
 Ldistance
 Leahy
+Lef
 Lehmann
 Lehre
 Leijten
@@ -1234,6 +1239,7 @@ Microsystems
 MidiToBuffer
 Mikkel
 Miklody
+Mikmak
 MinGW
 Mingzhou
 Mislocalization
@@ -1418,13 +1424,17 @@ OHBM
 OOP
 RIA
 RSA
+Rig
+Sofie
 Spotify
 TRFs
 appenddim
 appendsource
 biopac
+eetbar
 fieldname
 paxinos
+triaxial
 
 OPM
 OPMEG

diff --git a/getting_started/cerca.md b/getting_started/cerca.md
@@ -9,7 +9,7 @@ tags: [dataformat, meg, opm, cerca, bids]
 
 There are some differences which are relevant for processing Cerca data - and OPM data as a whole. One difference is how events or triggers are represented and detected. Another difference is in the procedure used to record the position of the OPM sensors relative to the head, which is relevant for topographic plotting and for the co-registration between MEG and MRI. Furthermore, Cerca OPM systems use either dual axis or triaxial systems, and so displaying data at a sensor-level requires some further considerations.
 
-The example data provided on the FieldTrip [download server](https://download.fieldtriptoolbox.org/example/cerca/) includes a self-contained version of the data in the `.fif` format organized according to the [BIDS standard](https://www.bids-standard.org). This includes sensor locations that are already co-registered to a 3D digitisation of the participant. An additional folder includes the raw files if you wish to develop a co-registration pipeline separately from what is provided. All files are detailed in the `README.txt`.
+The example data provided on the FieldTrip [download server](https://download.fieldtriptoolbox.org/example/cerca/) includes a self-contained version of the data in the `.fif` format organized according to the [BIDS standard](https://www.bids-standard.org). This includes sensor locations that are already co-registered to a 3D digitization of the participant. An additional folder includes the raw files if you wish to develop a co-registration pipeline separately from what is provided. All files are detailed in the `README.txt`.
 
 ## Read and visualize the continuous data
 
@@ -160,7 +160,7 @@ For topographic plotting, the channel names (in data.label) should match the loc
 
 ## Co-registration
 
-There is a dedicated tutorial elsewhere that deals with various ways to co-register the OPM sensors with the head and the anatomical MRI. In this demonstration, the .fif file already contains a digitisation that the sensors have been co-registered to (using the dev2head transform `hdr.orig.dev_head_t`). However, the raw digitisation files and CAD file for the helmet have been provided (see the README.txt). The co-registration of the sensors to the digitisation was performed as described in Figure 2b in [Hill et al. 2020](https://doi.org/10.1016/j.neuroimage.2020.116995). 
+There is a dedicated tutorial elsewhere that deals with various ways to co-register the OPM sensors with the head and the anatomical MRI. In this demonstration, the .fif file already contains a digitization that the sensors have been co-registered to (using the dev2head transform `hdr.orig.dev_head_t`). However, the raw digitization files and CAD file for the helmet have been provided (see the README.txt). The co-registration of the sensors to the digitization was performed as described in Figure 2b in [Hill et al. 2020](https://doi.org/10.1016/j.neuroimage.2020.116995). 
 
 ## See also