The relationship between ERP components and EEG spatial complexity in a visual Go/Nogo task
Bibliographic record
Abstract
The ERP components and variations of spatial complexity or functional connectivity are two distinct dimensions of neurophysiological events in the visual Go/Nogo task. Extensive studies have been conducted on these two distinct dimensions; however, no study has investigated whether these two neurophysiological events are linked to each other in the visual Go/Nogo task. The relationship between spatial complexity of electroencephalographic (EEG) data, quantified by the measure omega complexity, and event-related potential (ERP) components in a visual Go/Nogo task was studied. We found that with the increase of spatial complexity level, the latencies of N1 and N2 component were shortened and the amplitudes of N1, N2, and P3 components were decreased. The anterior Go/Nogo N2 effect and the Go/Nogo P3 effect were also found to be decreased with the increase of EEG spatial complexity. In addition, the reaction times in high spatial complexity trials were significantly shorter than those of medium and low spatial complexity trials when the time interval used to estimate the EEG spatial complexity was extended to 0∼1,000 ms after stimulus onset. These results suggest that high spatial complexity may be associated with faster cognitive processing and smaller postsynaptic potentials that occur simultaneously in large numbers of cortical pyramidal cells of certain brain regions. The EEG spatial complexity is closely related with demands of certain cognitive processes and the neural processing efficiency of human brain. NEW & NOTEWORTHY: The reaction times, the latencies/amplitudes of event-related potential (ERP) components, the Go/Nogo N2 effect, and the Go/Nogo P3 effect are linked to the electroencephalographic (EEG) spatial complexity level. The EEG spatial complexity is closely related to demands of certain cognitive processes and could reflect the neural processing efficiency of human brain. Obtaining the single-trial ERP features through single-trial spatial complexity may be a more efficient approach than traditional methods.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".