Skip to content

Emotiv ERP Setup - #251

Merged
thamha-emotiv merged 1 commit into
masterfrom
EmotivERPSetup
Nov 13, 2026
Merged

thamha-emotiv merged 1 commit into
masterfrom
EmotivERPSetup

Conversation

@hoangphamemotiv

Copy link
Copy Markdown
Contributor

No description provided.

@thamha-emotiv
thamha-emotiv merged commit 7c42d50 into master Nov 13, 2026
4 of 6 checks passed
@thamha-emotiv
thamha-emotiv deleted the EmotivERPSetup branch November 13, 2026 09:34

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

The guide still needs to clarify that interval recording must wait for endpoint-update acknowledgments and distinguish counter sampling and platform-dependent resolution from actual stimulus-onset accuracy.

2 open issues
What changed in this PR

This PR adds ERP experiment setup guidance for the Python marker example and switches clock synchronization and marker timestamp generation to time.perf_counter().

Changes:

  • Documents headset setup, clock synchronization, marker workflows, and record export.
  • Uses the performance counter consistently for synchronization requests and marker timestamps.
File Description
python/​marker.py Uses time.perf_counter() to calculate marker timestamps.
python/​Emotiv_ERP_Setup.md Adds hardware setup and software workflow guidance for ERP experiments.
python/​cortex.py Uses time.perf_counter() in headset clock synchronization requests.

Review effort: Balanced

- **Step 4b:** When the event ends, call `update_marker(marker_id, end_time)` to set the end of the interval, converting the instance marker into an interval marker.

### Step 5: Stop Record and Wait for Post-Processing (Warning Code 30)
Once all markers have been injected, the application calls `self.stop_record()`.

| Component | Unit | Description |
| :--- | :---: | :--- |
| `time.perf_counter()` | Seconds (`float`) | High-resolution monotonic performance counter captured at the exact moment the event occurs (uses `QueryPerformanceCounter` on Windows with `100 ns` resolution, avoiding the `15.625 ms` tick quantization of `GetTickCount64`). |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants