Data · dataset · 2021
No evidence of rhythmic visuospatial attention at cued locations in a spatial cuing paradigm, regardless of their behavioral relevance.
Listed in IISH Dataverse and ODISSEI Portal — shown once because both records carry DOI 10.34894/7vp5oa
Recent evidence suggests that visuospatial attention is not sustained but fluctuates in a rhythmic fashion, sampling location after location in each cycle of this rhythm.
Description
However, studies differ in which location rhythmic attention becomes evident: the cued, non-cued location or both. It is also unclear how the behavioral relevance of each sampled location determines the rhythmic sampling patterns.
Here, we aim to elucidate these two issues. First, we aim to find evidence of rhythmic attention at the predicted (i.e. cued) location under moderately informative predictor value, replicating earlier studies. Second, we hypothesize that rhythmic attentional sampling behavior will be affected by the behavioral relevance of the sampled location, ranging from non-informative to fully informative.
Read the rest (2 more)
To these aims, we used a modified Egly-Driver task with three conditions: a fully informative cue, a moderately informative cue (replication condition), and a non-informative cue. We did not find evidence of rhythmic sampling at cued locations, failing to replicate earlier studies. However, we did find attentional rhythmicity at non-cued locations, specifically on different objects.
This effect was only present when the cue was informative, not when the cue was non-informative. These results suggest that the strongest evidence of rhythmic sampling can be found at spatial locations that bear relatively less behavioral relevance. This suggests an occasional dis-engagement mechanism, whereby attention regularly switches from behaviorally relevant locations to less behaviorally relevant locations.
Links
Where it is published
- Dataverse dataset page dataverse.nl/dataset.xhtml?persistentId=doi%3A10.34894%2F7VP5OA ↗
landing page · from datasets iisg amsterdam
- Dataverse dataset page portal.odissei.nl/dataset.xhtml?persistentId=doi%3A10.34894%2F7VP5OA ↗
landing page · from portal odissei nl
- DOI doi.org/10.34894/7vp5oa ↗
DOI / persistent id · from datasets iisg amsterdam
Catalogue records · 2
- Dataverse API dataverse.nl/api/datasets/:persistentId/?persistentId=doi%3A10.34894%2F7VP5… ↗
metadata API · from datasets iisg amsterdam
- Dataverse API portal.odissei.nl/api/datasets/:persistentId/?persistentId=doi%3A10.34894%2F7VP5… ↗
metadata API · from portal odissei nl
Topics
- Stated by source
- Social Sciences · Social Sciences
- From keywords
- Social Science · Social Science
Provenance · 2 source records, 10 field assertions
| Source | Key | Last seen | Raw |
|---|---|---|---|
| IISH Dataverse | doi:10.34894/7VP5OA | 13 d ago | JSON v1 |
| ODISSEI Portal | doi:10.34894/7VP5OA | 9 d ago | JSON v1 |
| Field | Assertion | Extractor | Evidence |
|---|---|---|---|
| concepts[field].dataverse_subject:social-sciences | source · datasets iisg amsterdam | connector:datasets_iisg_amsterdam@1.0.0 | /subjects |
| concepts[field].dataverse_subject:social-sciences | source · portal odissei nl | connector:portal_odissei_nl@1.0.0 | /subjects |
| concepts[field].local:field:social-science | mapping · portal odissei nl | connector:portal_odissei_nl@1.0.0 | /subjects |
| concepts[field].local:field:social-science | mapping · datasets iisg amsterdam | connector:datasets_iisg_amsterdam@1.0.0 | /subjects |
| created_date | source · datasets iisg amsterdam | connector:datasets_iisg_amsterdam@1.0.0 | |
| description | source · datasets iisg amsterdam | connector:datasets_iisg_amsterdam@1.0.0 | /description |
| publication_date | source · datasets iisg amsterdam | connector:datasets_iisg_amsterdam@1.0.0 | |
| title | source · datasets iisg amsterdam | connector:datasets_iisg_amsterdam@1.0.0 | /name |
| updated_date | source · datasets iisg amsterdam | connector:datasets_iisg_amsterdam@1.0.0 | |
| version_label | source · datasets iisg amsterdam | connector:datasets_iisg_amsterdam@1.0.0 |