> For the complete documentation index, see [llms.txt](https://emotiv.gitbook.io/emotivpro-analyzer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emotiv.gitbook.io/emotivpro-analyzer/understanding-analyzer-outputs/csv-outputs.md).

# csv outputs

The Analyzer csv outputs for each pipeline contains some columns which are the same as in the raw data exported from EmotivPRO. This is detailed in the [EmotivPRO manual](https://emotiv.gitbook.io/emotivpro-v3/managing-your-eeg-data-recordings/exporting-an-eeg-data-recording/csv-files#eeg-quality). 

In addition to these, the Analyzer outputs will include different columns depending on the pipeline.

**Basic EEG Processing:**

| Key                                                                                                                                                                                                                                    | Value                                                          |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| latency\_\_desc                                                                                                                                                                                                                        | Time since the start of the recording in seconds               |
| <p>eeg.\<sensor><br>Examples: eeg.af3, eeg.f7</p>                                                                                                                                                                                      | Processed EEG data for each EEG sensor, in microvolts.         |
| <p>sq.sampleratequality</p><p>sq.overallsensorquality</p><p>sq.pm </p><p>sq.signalmagnitudequality sq.internalsignalmagnitudequality </p><p>sq.sensorqualityscore sq.internalsensorqualityscore </p><p>sq.likelihood </p><p>sq.rms</p> | These columns are for internal use for calculating EEG Quality |

**EEG transformation and Band Power Reports (Individual and Grouped) :**

| Key                                        | Value                                                                                                                                                          |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| stamp\_i\_\_desc                           | timestamp of the start of the Fourier transform window                                                                                                         |
| stamp\_f\_\_desc                           | timestamp of the end of the Fourier transform window                                                                                                           |
| latency\_i\_\_desc                         | time of the beginning of the Fourier transform window relative to the beginning of the recording                                                               |
| latency\_f\_\_desc                         | time of the beginning of the Fourier transform window relative to the end of the recording.                                                                    |
| eeg.\[ch]\_\[low\_f]\_\[high\_f]Hz\_\_feat | The bandpowers in decibels (ie 10\*log10 (band\_power per hertz) in the channel ch in the band from low\_f to high\_f (including low\_f and excluding high\_f) |
| minimum\_cq\_\_desc                        | Contact quality score of the worst channel in the Fourier transform window                                                                                     |
| maximum\_rms\_\_desc                       | The largest root mean square(RMS) over the Fourier transform window.                                                                                           |
| data\_fixed\_\_desc                        | A flag to say that there was data missing or other problem in the Fourier transform window.                                                                    |
| marker\_label\_\_desc                      | The event marker or event label name                                                                                                                           |
| phasename\_\_desc                          | The phase name - This is typically only found in records created with Emotiv Builder/Emotiv LABS experiments                                                   |
| record\_title                              | Title or name of the record                                                                                                                                    |
| subject\_id                                | subject identification number                                                                                                                                  |


---

# 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://emotiv.gitbook.io/emotivpro-analyzer/understanding-analyzer-outputs/csv-outputs.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.