Data leakage in feature selection invalidates reported classification accuracy for autism diagnosis from fMRI.
An expression of concern has been published about this paper: the notice, 42555373, from Europe PMC.
Overview
Abstract
No abstract was found for this paper: the paper, at the publisher.
Code
No file of the authors' code could be read here: it is described below, and read at its source.
v1dya/XAI-for-ASD
Availability: 1 check, the latest on 27 September 2026: the link is dead
- 27 September 2026: the link is dead
Tracing map
Proposed by the machine: these links were found in the paper and verified at the source, without human review. The map will receive a Zenodo DOI once one of the paper's authors has validated it with their ORCID.
What the map holds:
- 1 repository of the authors' code, each at its verified commit, with its license and how the link was found in the paper;
- 0 scripts, each with its path and the digest of its content;
- no match between paragraphs and code yet;
- neither the text of the paper nor the code itself.
Its JSON (tracing-map.json) is deposited on Zenodo with its DOI once the map is validated.
Data
No dataset and no data link were found in the paper.
Versions
The history of this record: each version stored by the harvester or made by a correction of its authors or of the maintainers of its code, and what changed in its facts. The texts of the paper (its abstract, its availability statements) are not part of it; versions that changed only those are not listed.
Version 1, 27 September 2026: the first record
Recorded: type, language, journal, volume, pages, dates, 2 authors, 3 references, 1 integrity notice.
Cite
This paper
Kurkin, S., & Hramov, A. (2026). Data leakage in feature selection invalidates reported classification accuracy for autism diagnosis from fMRI. EClinicalMedicine, 97, 104049. https://
BibTeX
@article{kurkin2026data,
author = {Kurkin, Semyon and Hramov, Alexander},
title = {{Data leakage in feature selection invalidates reported classification accuracy for autism diagnosis from fMRI}},
journal = {EClinicalMedicine},
year = {2026},
month = jun,
volume = {97},
pages = {104049},
publisher = {Elsevier},
issn = {2589-5370},
doi = {10.1016/
url = {https://
pmid = {42518934},
pmcid = {PMC13382443}
}
RIS
TY - JOUR
AU - Kurkin, Semyon
AU - Hramov, Alexander
TI - Data leakage in feature selection invalidates reported classification accuracy for autism diagnosis from fMRI
T2 - EClinicalMedicine
J2 - EClinicalMedicine
PY - 2026
DA - 2026/
VL - 97
SP - 104049
SN - 2589-5370
PB - Elsevier
DO - 10.1016/
UR - https://
LA - en
ER -
CSL-JSON
{
"id": "10.1016/
"type": "article-journal",
"title": "Data leakage in feature selection invalidates reported classification accuracy for autism diagnosis from fMRI",
"container-title": "EClinicalMedicine",
"author": [
{
"family": "Kurkin",
"given": "Semyon"
},
{
"family": "Hramov",
"given": "Alexander"
}
],
"container-title-short":
"volume": "97",
"page": "104049",
"DOI": "10.1016/
"PMID": "42518934",
"PMCID": "PMC13382443",
"ISSN": "2589-5370",
"publisher": "Elsevier",
"URL": "https://
"language": "en",
"issued": {
"date-parts": [
[
2026,
6,
24
]
]
}
}
The tracing map gets a citation of its own once an author has validated it and it has a DOI.
Similar papers
The papers with a page that share the most with this one: the tools found in their code, their categories, datasets, cited references and authors, the rarest counting most.
- [1] doi:10.3390/s23146420
- Perceptual Integration Compensates for Attention Deficit in Elderly during Repetitive Auditory-Based Sensorimotor Task.Journal: Sensors (Basel, Switzerland)In common: author Semyon Kurkin
- [2] doi:10.1093/gigascience/giaf091 [code]
- High-precision machine learning identifies a reproducible functional connectivity signature of autism spectrum diagnosis in a subset of individuals.Journal: GigaScienceIn common: autism, fMRI, clinical / translational, 1 reference
- [3] doi:10.1038/s41598-024-71174-z
- Twinned neuroimaging analysis contributes to improving the classification of young people with autism spectrum disorder.Journal: Scientific reportsIn common: autism, fMRI, clinical / translational, 1 reference
- [4] doi:10.3390/bioengineering10010056 [code]
- Understanding the Role of Connectivity Dynamics of Resting-State Functional MRI in the Diagnosis of Autism Spectrum Disorder: A Comprehensive Study.Journal: Bioengineering (Basel, Switzerland)In common: autism, fMRI, clinical / translational, 1 reference
- [5] doi:10.3390/diagnostics16172746
- Benchmarking Synolitic Graphs for Autism Classification from Multisite Resting-State fMRI.Journal: Diagnostics (Basel, Switzerland)In common: autism, fMRI, 1 reference
- [6] doi:10.1038/s41598-026-50461-x [code]
- MACAFNet transformer-based multi-atlas fusion framework for autism spectrum disorder classification using functional connectivity.Journal: Scientific reportsIn common: autism, fMRI, 1 reference
- [7] doi:10.3390/brainsci16030277 [code]
- A Dual-Stream Transformer with Self-Supervised Contrastive Training for fMRI-Based Autism Spectrum Disorder Classification.Journal: Brain sciencesIn common: autism, fMRI, 1 reference
- [8] doi:10.3390/brainsci16020181 [code]
- Multi-Site Classification of Autism Spectrum Disorder Using Spatially Constrained ICA on Resting-State fMRI Networks.Journal: Brain sciencesIn common: autism, fMRI, 1 reference
- [9] doi:10.3390/brainsci15111136 [code]
- M&
lt;sup& gt;3& lt;/ sup& gt;ASD: Integrating Multi-Atlas and Multi-Center Data via Multi-View Low-Rank Graph Structure Learning for Autism Spectrum Disorder Diagnosis. Journal: Brain sciencesIn common: autism, fMRI, 1 reference - [10] doi:10.1002/hbm.70190 [code]
- A Framework for Comparison and Interpretation of Machine Learning Classifiers to Predict Autism on the ABIDE Dataset.Journal: Human brain mappingIn common: autism, fMRI, 1 reference
Contribute
The authors of this paper can claim it, correct its record and validate its tracing map, 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 OSCR's own machine, which answers it; your account page follows them.
Sign in with ORCID to claim this paper as one of its authors, correct its record or validate its tracing map: 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.
Claim this paper
Correct its record
Say what each link of this record is, remove the ones that are not the paper's, add the ones that are missing. The correction becomes a new version of the record, in its Versions section.
Validate its tracing map
You validate the map as this page shows it: 1 repository of the authors' code, each at its verified commit and with its license, 0 scripts, and 0 matches between paragraphs and code (see the Code and Map sections). It then receives a DOI on Zenodo, with you (your ORCID iD) and OSCR as its creators; the code itself is not deposited.
The map's fingerprint: sha256:dc708fe056d510c6…
Add the badge to the code's README
If you are an author or a maintainer of this paper's code, you can add this badge. It says what OSCR knows of the paper (its code, its validated tracing map) and links the code to this page. Paste one of these snippets under the README's title. Keep the two marks around it, so that the badge can be replaced in place and is never added twice. OSCR changes nothing in your repository.
Markdown
<!-- oscr-badge:start -->
[](https://openscicode.org/badge/doi/10.1016/j.eclinm.2026.104049)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1016/j.eclinm.2026.104049.svg
:target: https://openscicode.org/badge/doi/10.1016/j.eclinm.2026.104049
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1016/j.eclinm.2026.104049"><img src="https://openscicode.org/badge/doi/10.1016/j.eclinm.2026.104049.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->On GitHub, open the README, choose Edit (the pencil), paste the snippet under the title, then "Commit changes".
If you choose to, you can have the badge kept up to date for you, with oscr badge --write from the command line or with the GitHub Action in your repository's workflows. Every other form and option (a card, AsciiDoc, LaTeX, shields.io) is on the badge page.
Request its removal
To ask OSCR to remove this record, the copies of its authors' scripts or its tracing map, 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).
Discussion, reproductions, activity
Discussion: code errors and mismatches between the code and the paper about this paper and its code, from readers and its authors, beside the paper and its tracing map.
Report a mismatch between the code and the paper · Report a code error (signed in)
Reproductions: reports from readers who ran the authors' code and did not get the paper's result, what they ran, with which environment, commit and data.
Report a reproduction failure (signed in)
Versions of its code: the releases of its code tied to a version of this paper (the preprint, the accepted manuscript, the version of record…), each with the tracing map versioned with it.
Activity: what happens around this paper: new versions of its record, its map's validation, discussions and reproductions. It opens with sign-in.
