OSCR

Superior frontal regions reflect the dynamics of task engagement and theta band-related control processes in time-on task effects.

This page is built on request from the registry's record of the paper. The 6,000 most recent papers have a fuller page, built ahead of time, with the Code ↔ Paper reader, the tracing map and its validation, the record's versions, how to cite it and similar papers. This paper is older: its record, its code, its data and the requests about it are below.

Code

32 files of its code read; 10 matches between paragraphs and code. The Code ↔ Paper reader is built for the 6,000 most recent papers only: this paper's code is read at its source.

OSF afyux

License: none: the authors keep all their rights
State: the link answers
Copies: kept by the registry: this license allows it

Code blocks with an identifier

Each block below is lines of the authors' code linked to a paragraph of this paper, with an identifier given for good: it is never reused nor deleted, and its page says what it names and how to cite it. What a block identifier is.

  • oscr:b:1932D6KCZBH3S-6: analysis scripts and EEG Data/Scripts.zip/Eyetracking_Synchronization.m, lines 11 to 118 (paragraphs 40, 46)
  • oscr:b:SV3YWBZNY3D89-G: analysis scripts and EEG Data/Scripts.zip/Define_Trials_EEG.m, lines 1 to 56 (paragraph 40)
  • oscr:b:Z6RAN5SD7KPT1-P: analysis scripts and EEG Data/Scripts.zip/step3_beamforming_Contrast_GA.m, lines 259 to 276 (paragraph 43)
  • oscr:b:9MYPRFTPH2S2T-I: analysis scripts and EEG Data/Scripts.zip/step2_beamforming_Contras.m, lines 303 to 320 (paragraphs 45, 43)
  • oscr:b:BN3K2ER7J44PH-Y: analysis scripts and EEG Data/Scripts.zip/step5_lcmv.m, lines 1 to 69 (paragraphs 21, 45)
  • oscr:b:J7AQNVG9Q6SPF-9: analysis scripts and EEG Data/Scripts.zip/Cluster_based_permutation.m, lines 54 to 142 (paragraph 41)
  • oscr:b:QRTG29D8KX2MZ-X: analysis scripts and EEG Data/Scripts.zip/Behavior_Analysis.m, lines 143 to 206 (paragraph 39)

Overview

Authors: Shijing Yu, Moritz Mückschel, Christian Beste
Published: 17 January 2022
Type: Research article
Status: code verified (how the code is found and verified)
License: CC BY

Data

No dataset cited, and no data link found.

Contribute

The authors of this paper can claim it and correct its record, and the maintainers of its code (its owner, or a public member of its organization) correct what it says of their repository; anyone signed in can ask for its removal. Every request goes to the registry's own machine, which answers it; your account page follows them.

Sign in with ORCID to claim this paper as one of its authors or correct its record: when the paper's metadata lists your ORCID iD, you are recognized at once. Maintainers of its code: sign in with GitHub, then claim the repository on your account page.

Add the badge to the code's README

OSCR: the badge of this paper

Authors and maintainers of this paper's code: the badge says what OSCR knows of the paper and links the code to this page. Paste one of these under the README's title. Keep the two marks around it: they let the badge be replaced in place, never added twice. Nothing is changed for you.

Markdown
<!-- oscr-badge:start -->
[![OSCR](https://openscicode.org/badge/doi/10.1038/s41598-022-04972-y.svg)](https://openscicode.org/badge/doi/10.1038/s41598-022-04972-y)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/doi/10.1038/s41598-022-04972-y.svg
   :target: https://openscicode.org/badge/doi/10.1038/s41598-022-04972-y
   :alt: OSCR

.. oscr-badge:end
HTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1038/s41598-022-04972-y"><img src="https://openscicode.org/badge/doi/10.1038/s41598-022-04972-y.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->

Or let it be kept for you, once you choose it: oscr badge --write from the command line, or the GitHub Action in your repository's workflows. Every other form is on the badge page.

Request its removal

To ask for this record, the copies of its authors' scripts or its tracing map to be removed, use the removal request page: signed in, you say who you are, what to remove and why, then review and confirm the request. Published rules decide every request (how).