> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/bnc-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/bnc-user-manual/xnat-to-bids-intro/converting-non-mr-data/physiological-data.md).

# Physiological data

Physiological data collected at the scanner is automatically exported as single DICOM files alongside each fMRI run. When you [transfer your data to XNAT](/bnc-user-manual/xnat/uploading-data.md), this data will come along, named the same as its associated functional run but with a \_WIP\_PMU suffix (or just \_PMU, before the XA30 scanner software upgrade).

<figure><img src="/files/Ua1dGNU2FqNt4jNWY7Ap" alt="A view of a scanning session’s runs, in the XNAT portal. The functional run (func-bold_task_checks_run+) is followed by its respective physiological data (func-bold_task-checks_run+_WIP_PMU)."><figcaption><p>Paired fMRI and physiological data on XNAT</p></figcaption></figure>

When you use xnat-tools to export your data and convert it to BIDS format, the physiological data should come along and be converted automatically. If you are exporting your data to Oscar, we recommend using our new [Oscar utility script](/bnc-user-manual/xnat-to-bids-intro/using-oscar/oscar-utility-script.md).

When the xnat2bids pipeline has finished, you can find your raw physiological data DICOM files in `export-dir/PI/study-XX/xnat-export/sub-XX/ses-XX/`, along with the DICOMs for your brain data. Xnat-tools will also automatically extract the pulse and respiration traces from the physiological DICOMs and create the cardiac and respiratory .tsv.gz and .json files associated with each functional run in `export-dir/PI/study-XX/bids/sub-XX/ses-XX/func`, as prescribed by the [BIDS specification](https://bids-specification.readthedocs.io/en/stable/04-modality-specific-files/06-physiological-and-other-continuous-recordings.html).

`sub-XX_ses-XX_task-XX_acq-XX_run-01_bold.json`

`sub-XX_ses-XX_task-XX_acq-XX_run-01_bold.nii.gz`

`sub-XX_ses-XX_task-XX_acq-XX_run-01_events.tsv`

`sub-XX_ses-XX_task-XX_acq-XX_run-01_recording-cardiac_physio.json`

`sub-XX_ses-XX_task-XX_acq-XX_run-01_recording-cardiac_physio.tsv.gz`

`sub-XX_ses-XX_task-XX_acq-XX_run-01_recording-respiratory_physio.json`

`sub-XX_ses-XX_task-XX_acq-XX_run-01_recording-respiratory_physio.tsv.gz`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ccv.brown.edu/bnc-user-manual/xnat-to-bids-intro/converting-non-mr-data/physiological-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.