ADD overview.md #28
ADD overview.md #28
Conversation
overview.md
Outdated
| A “record” in this context refers to a digital media file that contains the audio and visual stimulation presented to a subject while undergoing fMRI scanning for a particular session. | ||
| The goal is to provide one record for every functional acquisition collected at an fMRI research center. | ||
| The merits of collecting such records, if not obvious, are numerous and will be considered in a separate section. | ||
| While the scope of the project is limited to the special circumstances of collecting data at an fMRI research center, we anticipate that future modifications driven by interest and necessity may expand the set of use-cases to include other behavioral and neuroimaging paradigms. |
There was a problem hiding this comment.
with the above note, I think not even worth mentioning this here, and just say that every neuroimaging file (be it fmri, anat, dwi, etc) would have a corresponding stimulus file.
Also -- ultimate goal is to incorporate ReproStim within ReproIn/heudiconv data conversion, so to have all these files placed into BIDS dataset. Worth adding a reference to bids-standard/bids-specification#751 as WiP to possibly enhance BIDS to support per-neuroimaging file stimuli.
And also, such system could also be employed for purely behavioral experiments, and those are supported by BIDS as well.
| Setting up ReproStim requires an initial investment in hardware, including a video capture device, a computer that runs the ReproStim capture server software, | ||
| a USB “sniffer” device to capture scanner trigger pulses for use by the capture service, | ||
| and necessary cables and connectors including audio and video splitter cables. | ||
| [These details will be filled in later, and there is a reasonable sketch of the hardware set up already in the README.md file.] |
There was a problem hiding this comment.
Ok for now, But as we build up this doc, most of the information would be moved from README.md into the docs, and README just to point to them.
There was a problem hiding this comment.
OK. So all details about st-up, configuration, etc. will be removed from the overview. Makes sense.
There was a problem hiding this comment.
will it be done in this PR or you would like to do that in a separate follow up PR?
Co-authored-by: Yaroslav Halchenko <[email protected]>
... Not just for functional acquisitions. added language to indicate intention to collect all stimulations for all types of scans, not just functional scans.
Co-authored-by: Yaroslav Halchenko <[email protected]>
|
Yarick says to merge this here now. |
No description provided.