Getting started¶
This page takes you from installation to a validated, event-aware biometric workflow in a few minutes.
1. Install¶
The package requires Python 3.11 or newer. 0.1.5 is the stable public release; this documentation is frozen from the validated release source.
2. Load the packaged demo¶
The bundled kiosk dataset contains 36 synthetic participants, four tasks per participant, and 69,120 Gazepoint-like rows at 60 Hz. It is designed for tutorials, smoke tests, and reproducible examples—not for substantive empirical conclusions.
3. Audit before analysing¶
active = gp.detect_gazepoint_active_channels(data)
validity = gp.summarise_gazepoint_biometric_validity(data)
events = gp.extract_gazepoint_ttl_events(data)
print(active)
print(validity)
print(events.head())
A useful default order is:
- identify available channels;
- validate timing and missingness;
- recover events/TTL markers;
- preprocess only the signals that passed the relevant checks;
- align by event, trial, or AOI;
- summarize and plot;
- retain the QC/audit outputs with the analysis.
4. Pick a domain path¶
EDA / SCR
Artifacts, decomposition, SCR events and summaries.
Start EDA →PPG / HRV
Pulse detection, IBI, HRV and toolbox-style cross-checks.
Start PPG →Pupil / gaze
Pupil QC, gaze/AOI summaries and saccade diagnostics.
Start gaze →5. A compact physiological example¶
# pyHRV-style example from IBI in seconds
nni_ms = (
data.loc[data["IBI"].notna(), "IBI"]
.head(500)
.to_numpy()
* 1000
)
hrv = gp.run_gazepoint_pyhrv_style(nni_ms=nni_ms)
# HeartPy-style PPG processing
ppg = gp.process_gazepoint_ppg_heartpy_style(
data,
signal_col="HRP",
time_col="TIME",
)
6. Add optional backends only when needed¶
pip install "gpbiometricspy[mne,lsl]"
pip install "gpbiometricspy[heartpy,neurokit]"
pip install "gpbiometricspy[biosppy,pyhrv]"
pip install "gpbiometricspy[stats]"
The core package does not require these external toolboxes. Interoperability functions report backend/version context so that optional-tool results remain auditable.
Where to go next
Use the workflow map if you know your data modality but not the exact function family. Use the plot gallery if you want to see expected visual outputs first. Use the API reference when you already know the function name.
Interpretation guardrail
Physiological and eye-tracking measurements support signal-level and task-context analyses. They do not, by themselves, establish emotion, stress, preference, cognition, comprehension, clinical state, or diagnosis. See Interpretation guardrails.