Step 2 — Data Acquisition¶

Create a mapping file in accordance to the ANC file naming convention¶

Since data on the Sinuhe should not be renamed and the MEG Export requires some specific format a .csv file with the filename mapping between the name on the Sinuhe and our naming conventions needs to be provided.

Example CSV:

original_filename	new_filename
12345678abcd_fancytask_block1.fif	auditory__my-anc-project__12345678abcd__01__fancytask__1.fif
12345678abcd_fancytask_block1.fif	auditory__my-anc-project__12345678abcd__01__fancytask__2.fif
12345678abcd_resting.fif	auditory__my-anc-project__12345678abcd__01__rest__1.fif

Filename convention¶

The conversion pipeline parses subject, session, task, and run information from the .fif filename. Files must follow this naming format:

group__slug__subject__session__task__run.fif

Component	Description	Example
`group`	The group slug of your research group on the ANC`\|`auditory`
`slug`	Your project slug — must match the key in `.meg_conversion_config.yml`	`my-meg-study`
`subject`	Participant identifier	`001`
`session`	Session label	`1`
`task`	Task name (please do not use spaces, hypens or underscores). If you have resting state data the taskname needs to be `rest`.	`audiobook` or `rest`
`run`	Block number	`1`

Example:

auditory__my-meg-study__001__1__audiobook__1.fif

Example for resting state data:

auditory__my-meg-study__001__1__rest__1.fif

Double underscores are the separator

Components are separated by two underscores (__). A single underscore within a component is fine (e.g. ses_1), but do not use double underscores within a component name.

If there is only one run¶

Even if you only performed one run, please still add the run number:

auditory__my-meg-study__001__1__audiobook__1.fif

What to check during acquisition¶

Verify the trigger channel is active and sending the expected codes. You can inspect channels STI001–STI008 live during recording.
Confirm the filename is correct before saving — the pipeline cannot rename files after the fact.
For multi-run tasks, increment the run number for each file.

After acquisition¶

Once recording is complete, the .fif files are ready for the MEG BIDS conversion pipeline.