Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIX] Remove father-level for meg filetypes other than BTi/4D data #19

Merged
merged 3 commits into from
Mar 28, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 13 additions & 34 deletions src/99-appendices/06-meg-file-formats.md
Original file line number Diff line number Diff line change
Expand Up @@ -155,12 +155,11 @@ More about the 4D neuroimaging/BTi data organization at:

## KIT/Yokogawa/Ricoh

Each experimental run on a KIT/Yokogawa/Ricoh system yields a raw (`.sqd`,
`.con`) file with its associated marker coil file (`.mrk`), which contains coil
positions in the acquisition system’s native space. Head points and marker
points in head space are acquired using third-party hardware. One SHOULD
rename/create a father run specific directory and keep the original files for
each run inside.
Each experimental run on a KIT/Yokogawa/Ricoh system yields a raw
(`.sqd`, `.con`) file with its associated marker coil file (`.mrk`), which
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should add that .sqd is a valid marker file extension also

contains coil positions in the acquisition system’s native space. Head
points and marker points in head space are acquired using third-party
hardware.

Example:

Expand All @@ -174,14 +173,8 @@ sub-control01/
sub-control01_ses-001_task-rest_run-01_meg
sub-control01_ses-001_task-rest_run-01_meg.json
sub-control01_ses-001_task-rest_run-01_channels.tsv
```

Where:

```Text
sub-control01_ses-001_task-rest_run-01_meg/
sub-control01_ses-001_task-rest_run-01_markers.<mrk,sqd>
sub-control01_ses-001_task-rest_run-01_meg.<con,sqd>
sub-control01_ses-001_task-rest_run-01_markers.<mrk,sqd>
sub-control01_ses-001_task-rest_run-01_meg.<con,sqd>
```

More about the KIT/Yokogawa/Ricoh data organization at:
Expand Down Expand Up @@ -213,15 +206,9 @@ sub-control01/
sub-control01_ses-001_task-rest_run-01_meg
sub-control01_ses-001_task-rest_run-01_meg.json
sub-control01_ses-001_task-rest_run-01_channels.tsv
```

Where:

```Text
sub-control01_ses-001_task-rest_run-01_meg/
sub-control01_ses-001_task-rest_run-01_meg.chn
sub-control01_ses-001_task-rest_run-01_meg.kdf
sub-control01_ses-001_task-rest_run-01_meg.trg
sub-control01_ses-001_task-rest_run-01_meg.chn
sub-control01_ses-001_task-rest_run-01_meg.kdf
sub-control01_ses-001_task-rest_run-01_meg.trg
```

## ITAB
Expand All @@ -232,9 +219,7 @@ header that contains detailed information about the data acquisition system,
followed by binary data. The associated binary header file contains part of the
information from the ASCII header, specifically the one needed to process data,
plus other information on offline preprocessing performed after data acquisition
(e.g., sensor position relative to subject’s head, head markers, stimulus
information). One should rename/create a father run specific directory and keep
the original files for each run inside.
(e.g., sensor position relative to subject’s head, head markers, stimulus information).

Example:

Expand All @@ -246,14 +231,8 @@ sub-control01/
sub-control01_ses-001_task-rest_run-01_meg
sub-control01_ses-001_task-rest_run-01_meg.json
sub-control01_ses-001_task-rest_run-01_channels.tsv
```

Where:

```Text
sub-control01_ses-001_task-rest_run-01_meg/
sub-control01_ses-001_task-rest_run-01_meg.raw
sub-control01_ses-001_task-rest_run-01_meg.raw.mhd
sub-control01_ses-001_task-rest_run-01_meg.raw
sub-control01_ses-001_task-rest_run-01_meg.raw.mhd
```

## Aalto MEG–MRI
Expand Down