move question conversion nifti

bids-standard · Jun 28, 2024 · 46f600b · 46f600b
1 parent fa221cb
commit 46f600b
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 1 deletion.
diff --git a/docs/datasets/index.md b/docs/datasets/index.md
@@ -172,7 +172,7 @@ DO NOT EDIT DIRECTLY.
 | name                                                                                                | description                                                             | datatypes   | suffixes                                                             | link to full data                              | maintained by                                            |
 |:----------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------|:------------|:---------------------------------------------------------------------|:-----------------------------------------------|:---------------------------------------------------------|
 | [fnirs_automaticity](https://github.com/bids-standard/bids-examples/tree/master/fnirs_automaticity) | 24 subjects performing (non-)automatic finger tapping and foot stepping | nirs        | channels, coordsystem, events, nirs, optodes, practicelogbook, scans | [link](https://doi.org/10.34973/vesb-mh30)     | [@robertoostenveld](https://github.com/robertoostenveld) |
-| [fnirs_tapping](https://github.com/bids-standard/bids-examples/tree/master/fnirs_tapping)           | Example fNIRS measurement with three conditions from five subjects      | nirs        | channels, coordsystem, events, nirs, optodes, scans                  | [link](https://doi.org/10.5281/zenodo.5529797) | [@rob-luke](https://github.com/rob-luke)                 |
+| [fnirs_tapping](https://github.com/bids-standard/bids-examples/tree/master/fnirs_tapping)           | Example fNIRS measurement with three conditions from five subjects      | nirs        | channels, coordsystem, events, nirs, optodes, scans                  | [link](https://doi.org/10.5281/zenodo.5529797) | [@rob_luke](https://github.com/rob_luke)                 |
 
 ### PET
 

diff --git a/faq/general/convert-nifti.question.md → faq/mri/convert-nifti.question.md b/faq/general/convert-nifti.question.md → faq/mri/convert-nifti.question.md
@@ -45,6 +45,13 @@ For `func` files you only need `TaskName` and `RepetitionTime`
 and the former you can decide what it is and the latter should be in the Nifti header.
 So you should be OKish there too.
 
+```json
+{
+  "TaskName": "name_of your task",
+  "RepetitionTime": your repetition time value
+}
+```
+
 Obviously you will be missing some metadata that would be required
 for some type of preprocessing (like slice timing info).