Multimodal brain MRI and clinical data in olfactory groove meningioma: a prospective data report.
The 2 matches · 1 of them tie a paragraph to a whole file, not to given lines: a weak match, whose lines are not tinted
- [1] § Methods › Data records ↔ dcm2bids/utils/scaffold.py, the whole file · a weak match · score 0.63 · participants.tsv, clinical information, variables, BIDS
- [2] § Methods › Data records ↔ dcm2bids/cli/dcm2bids_scaffold.py, lines 44–115 · score 0.59 · participants.json, participants.tsv, platform, BIDS
Paper
Loaded from Europe PMC by your browser, not stored by OSCR: doi.org · Europe PMC
The paper is loaded when this pane is shown.
The authors' code
Python · 214 lines · 6.6 KB · GPL-3.0 · 1 match
- # -*- coding: utf-8 -*-
- class bids_starter_kit(object):
- CHANGES = """Revision history for your dataset
- 1.0.0 DATE
- - Initialized study directory
- """
- dataset_description = """{
- "Name": "",
- "BIDSVersion": "BIDS_VERSION",
- "License": "",
- "Authors": [
- ""
- ],
- "Acknowledgments": "",
- "HowToAcknowledge": "",
- "Funding": [
- ""
- ],
- "ReferencesAndLinks": [
- ""
- ],
- "DatasetDOI": ""
- }
- """
- participants_json = """{
- "age": {
- "LongName": "",
- "Description": "age of the participant",
- "Units": "years"
- },
- "sex": {
- "LongName": "",
- "Description": "sex of the participant as reported by the participant",
- "Levels": {
- "M": "male",
- "F": "female"
- }
- },
- "group": {
- "LongName": "",
- "Description": "experimental group the participant belonged to",
- "Levels": {
- "control": "control",
- "patient": "patient"
- }
- }
- }
- """
- participants_tsv = """participant_id age sex group
- sub-01 34 M control
- sub-02 12 F control
- sub-03 33 F patient
- """
- README = """# README
- The README is usually the starting point for researchers using your data
- and serves as a guidepost for users of your data. A clear and informative
- README makes your data much more usable.
- In general you can include information in the README that is not captured by some other
- files in the BIDS dataset (dataset_description.json, events.tsv, ...).
- It can also be useful to also include information that might already be
- present in another file of the dataset but might be important for users to be aware of
- before preprocessing or analysing the data.
- If the README gets too long you have the possibility to create a `/doc` folder
- and add it to the `.bidsignore` file to make sure it is ignored by the BIDS validator.
- More info here: https://neurostars.org/t/where-in-a-bids-dataset-should-i-put-notes-about-individual-mri-acqusitions/17315/3
- ## Details related to access to the data
- - [ ] Data user agreement
- If the dataset requires a data user agreement, link to the relevant information.
- - [ ] Contact person
- Indicate the name and contact details (email and ORCID) of the person responsible for additional information.
- - [ ] Practical information to access the data
- If there is any special information related to access rights or
- how to download the data make sure to include it.
- For example, if the dataset was curated using datalad,
- make sure to include the relevant section from the datalad handbook:
- http://handbook.datalad.org/en/latest/basics/101-180-FAQ.html#how-can-i-help-others-get-started-with-a-shared-dataset
- ## Overview
- - [ ] Project name (if relevant)
- - [ ] Year(s) that the project ran
- If no `scans.tsv` is included, this could at least cover when the data acquisition
- starter and ended. Local time of day is particularly relevant to subject state.
- - [ ] Brief overview of the tasks in the experiment
- A paragraph giving an overview of the experiment. This should include the
- goals or purpose and a discussion about how the experiment tries to achieve
- these goals.
- - [ ] Description of the contents of the dataset
- An easy thing to add is the output of the bids-validator that describes what type of
- data and the number of subject one can expect to find in the dataset.
- - [ ] Independent variables
- A brief discussion of condition variables (sometimes called contrasts
- or independent variables) that were varied across the experiment.
- - [ ] Dependent variables
- A brief discussion of the response variables (sometimes called the
- dependent variables) that were measured and or calculated to assess
- the effects of varying the condition variables. This might also include
- questionnaires administered to assess behavioral aspects of the experiment.
- - [ ] Control variables
- A brief discussion of the control variables --- that is what aspects
- were explicitly controlled in this experiment. The control variables might
- include subject pool, environmental conditions, set up, or other things
- that were explicitly controlled.
- - [ ] Quality assessment of the data
- Provide a short summary of the quality of the data ideally with descriptive statistics if relevant
- and with a link to more comprehensive description (like with MRIQC) if possible.
- ## Methods
- ### Subjects
- A brief sentence about the subject pool in this experiment.
- Remember that `Control` or `Patient` status should be defined in the `participants.tsv`
- using a group column.
- - [ ] Information about the recruitment procedure
- - [ ] Subject inclusion criteria (if relevant)
- - [ ] Subject exclusion criteria (if relevant)
- ### Apparatus
- A summary of the equipment and environment setup for the
- experiment. For example, was the experiment performed in a shielded room
- with the subject seated in a fixed position.
- ### Initial setup
- A summary of what setup was performed when a subject arrived.
- ### Task organization
- How the tasks were organized for a session.
- This is particularly important because BIDS datasets usually have task data
- separated into different files.)
- - [ ] Was task order counter-balanced?
- - [ ] What other activities were interspersed between tasks?
- - [ ] In what order were the tasks and other activities performed?
- ### Task details
- As much detail as possible about the task and the events that were recorded.
- ### Additional data acquired
- A brief indication of data other than the
- imaging data that was acquired as part of this experiment. In addition
- to data from other modalities and behavioral data, this might include
- questionnaires and surveys, swabs, and clinical information. Indicate
- the availability of this data.
- This is especially relevant if the data are not included in a `phenotype` folder.
- https://bids-specification.readthedocs.io/en/stable/03-modality-agnostic-files.html#phenotypic-and-assessment-data
- ### Experimental location
- This should include any additional information regarding the
- the geographical location and facility that cannot be included
- in the relevant json files.
- ### Missing data
- Mention something if some participants are missing some aspects of the data.
- This can take the form of a processing log and/or abnormalities about the dataset.
- Some examples:
- - A brain lesion or defect only present in one participant
- - Some experimental conditions missing on a given run for a participant because
- of some technical issue.
- - Any noticeable feature of the data for certain participants
- - Differences (even slight) in protocol for certain participants.
- ### Notes
- Any additional information or pointers to information that
- might be helpful to users of the dataset. Include qualitative information
- related to how the data acquisition went.
- """
scaffold.py at commit 7f5ecf1, under GPL-3.0 · at the source
Overview
- Federal Neurosurgical Center, Novosibirsk, Russia
- Novosibirsk State Medical University, Novosibirsk, Russia
- Novosibirsk State University, Novosibirsk, Russia
- Novosibirsk State Technical University, Novosibirsk, Russia
Abstract
Olfactory groove meningiomas are uncommon skull base tumors that often present at advanced stages and may cause persistent cognitive and behavioral disturbances despite successful surgical treatment. Neuroimaging studies of this tumor entity have been limited, and publicly available multimodal MRI datasets remain scarce. Here, we present a prospective, single-center dataset comprising multimodal magnetic resonance imaging and longitudinal clinical data from patients with olfactory groove meningiomas acquired before and after surgical intervention. The dataset includes high-resolution structural MRI, diffusion MRI with tensor-derived metrics, resting-state functional MRI, tumor and peritumoral edema segmentation masks, and detailed clinical and neuropsychological assessments. Imaging data were acquired using a standardized protocol and processed with reproducible pipelines, including quality control and de-identification procedures, and organized in a BIDS format. This dataset is intended to support reproducible research and secondary analyses focused on tumor-related brain alterations, imaging biomarker development, and postoperative recovery in neuro-oncology.
Reproduced under the paper's license (CC BY), from the paper cited above.
Repository
Its files are read in the Code ↔ Paper reader above, with 2 matches between paragraphs and lines of code.
UNFmontreal/Dcm2Bids
7f5ecf18775444d16685624f6c3906ec8b36acf8, 16 September 2026Availability: 1 check, the latest on 28 September 2026: the link answers
- 28 September 2026: the link answers
32 files
- dcm2bids/
__init__.py , Python, 1 line - dcm2bids/
acquisition.py , Python, 330 lines - dcm2bids/
cli/ , Python, 1 line__init__.py - dcm2bids/
cli/ , Python, 186 linesdcm2bids.py - dcm2bids/
cli/ , Python, 120 linesdcm2bids_helper.py - dcm2bids/
cli/ , Python, 119 lines, 1 matchdcm2bids_scaffold.py - dcm2bids/
dcm2bids_gen.py , Python, 230 lines - dcm2bids/
dcm2niix_gen.py , Python, 155 lines - dcm2bids/
participant.py , Python, 101 lines - dcm2bids/
sidecar.py , Python, 623 lines - dcm2bids/
utils/ , Python, 1 line__init__.py - dcm2bids/
utils/ , Python, 48 linesargs.py - dcm2bids/
utils/ , Python, 95 linesio.py - dcm2bids/
utils/ , Python, 59 lineslogger.py - dcm2bids/
utils/ , Python, 214 lines, 1 matchscaffold.py - dcm2bids/
utils/ , Python, 691 linesschema.py - dcm2bids/
utils/ , Python, 14 linesschema_data/ __init__.py - dcm2bids/
utils/ , Python, 336 linestools.py - dcm2bids/
utils/ , Python, 251 linesutils.py - dcm2bids/
version.py , Python, 21 lines - tests/
__init__.py , Python, 1 line - tests/
test_cli_dcm2bids.py , Python, 152 lines - tests/
test_dcm2bids.py , Python, 713 lines - tests/
test_dcm2niix.py , Python, 56 lines - tests/
test_helper.py , Python, 96 lines - tests/
test_scaffold.py , Python, 19 lines - tests/
test_schema.py , Python, 650 lines - tests/
test_sidecar.py , Python, 48 lines - tests/
test_structure.py , Python, 39 lines - tests/
test_version.py , Python, 13 lines - LICENSE.txt, License, 678 lines
- README.md, Text, 100 lines
Code availability
We utilized openly available code to run FSL's topup and eddy, as well as MRIQC without generating any specific scripts for the data analysis.
Reproduced under the paper's license (CC BY), from the paper cited above.
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;
- 30 scripts, each with its path and the digest of its content;
- 2 matches between paragraphs of the paper and lines of the code (method lexical-v1);
- 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
Datasets cited
- openneuro:ds007345, at OpenNeuro; found in “Data availability statement”
Data availability statement
The datasets presented in this study can be found in online repositories. The names of the repository/
Reproduced under the paper's license (CC BY), from the paper cited above.
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 2, 28 September 2026
- Funding: added Russian Science Foundation
Version 1, 28 September 2026: the first record
Recorded: type, language, journal, volume, pages, dates, 8 authors, 5 keywords, 14 references.
Cite
This paper
Filimonova, E., Pashkov, A., Moysak, G., Martirosyan, A., Kurilov, V., Poptsova, A., Morozova, R., & Rzaev, J. (2026). Multimodal brain MRI and clinical data in olfactory groove meningioma: a prospective data report. Frontiers in radiology, 6, 1809871. https://
BibTeX
@article{filimonova2026m
author = {Filimonova, Elena and Pashkov, Anton and Moysak, Galina and Martirosyan, Azniv and Kurilov, Vladimir and Poptsova, Aleksandra and Morozova, Renata and Rzaev, Jamil},
title = {{Multimodal brain MRI and clinical data in olfactory groove meningioma: a prospective data report}},
journal = {Frontiers in radiology},
year = {2026},
month = may,
volume = {6},
pages = {1809871},
publisher = {Frontiers Media SA},
issn = {2673-8740},
doi = {10.3389/
url = {https://
pmid = {42182936},
pmcid = {PMC13194104}
}
RIS
TY - JOUR
AU - Filimonova, Elena
AU - Pashkov, Anton
AU - Moysak, Galina
AU - Martirosyan, Azniv
AU - Kurilov, Vladimir
AU - Poptsova, Aleksandra
AU - Morozova, Renata
AU - Rzaev, Jamil
TI - Multimodal brain MRI and clinical data in olfactory groove meningioma: a prospective data report
T2 - Frontiers in radiology
J2 - Front Radiol
PY - 2026
DA - 2026/
VL - 6
SP - 1809871
SN - 2673-8740
PB - Frontiers Media SA
DO - 10.3389/
UR - https://
LA - en
ER -
CSL-JSON
{
"id": "10.3389/
"type": "article-journal",
"title": "Multimodal brain MRI and clinical data in olfactory groove meningioma: a prospective data report",
"container-title": "Frontiers in radiology",
"author": [
{
"family": "Filimonova",
"given": "Elena"
},
{
"family": "Pashkov",
"given": "Anton"
},
{
"family": "Moysak",
"given": "Galina"
},
{
"family": "Martirosyan",
"given": "Azniv"
},
{
"family": "Kurilov",
"given": "Vladimir"
},
{
"family": "Poptsova",
"given": "Aleksandra"
},
{
"family": "Morozova",
"given": "Renata"
},
{
"family": "Rzaev",
"given": "Jamil"
}
],
"container-title-short":
"volume": "6",
"page": "1809871",
"DOI": "10.3389/
"PMID": "42182936",
"PMCID": "PMC13194104",
"ISSN": "2673-8740",
"publisher": "Frontiers Media SA",
"URL": "https://
"language": "en",
"issued": {
"date-parts": [
[
2026,
5,
8
]
]
}
}
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.1162/imag.a.1347 [code]
- Neural and behavioural correlates of theory of mind reasoning in five-year-old children born preterm.Journal: Imaging neuroscience (Cambridge, Mass.)In common: Dcm2Bids, PyBIDS, fMRI, other condition
- [2] doi:10.1016/j.dcn.2026.101765 [code]
- Fusiform face area development correlates with development in higher-order social brain regions.Journal: Developmental cognitive neuroscienceIn common: Dcm2Bids, PyBIDS, fMRI
- [3] doi:10.1038/s41467-026-71719-y [code]
- Brain functional-structural gradient coupling reflects development, behavior and genetic influences.Journal: Nature communicationsIn common: Dcm2Bids, dcm2niix
- [4] doi:10.1093/braincomms/fcag220 [code]
- When pain becomes self: limbic-default mode network hyperconnectivity predicts microvascular decompression failure in trigeminal neuralgia.Journal: Brain communicationsIn common: Dcm2Bids, fMRI, structural MRI / diffusion
- [5] doi:10.1162/imag.a.1252 [code]
- Does the brain's E:I balance really shape long-range temporal correlations? Lessons learned from 3T MRI.Journal: Imaging neuroscience (Cambridge, Mass.)In common: Dcm2Bids, fMRI, structural MRI / diffusion
- [6] doi:10.1093/brain/awag032 [code]
- A rostral prefrontal mediolateral gradient predicts creativity in frontotemporal dementia.Journal: Brain : a journal of neurologyIn common: PyBIDS, fMRI, structural MRI / diffusion
- [7] doi:10.1038/s41398-026-04157-5 [code]
- Association of glymphatic function with 40-Hz neural oscillations, systemic metabolic markers, and cognitive performance in healthy aging adults: An EEG and MRI study.Journal: Translational psychiatryIn common: PyBIDS, fMRI, structural MRI / diffusion
- [8] doi:10.3389/fpsyt.2026.1757213 [code]
- A novel music-based real-time fMRI neurofeedback interface modulates interhemispheric connectivity and enhances mood.Journal: Frontiers in psychiatryIn common: Dcm2Bids, fMRI
- [9] doi:10.1002/brb3.71581 [code]
- Blunted Reward Responsiveness During Social Feedback: Associations with Peer Victimization and Anhedonia in Socially Anxious Adolescents.Journal: Brain and behaviorIn common: dcm2niix, structural MRI / diffusion, other condition
- [10] doi:10.1093/brain/awaf412 [code]
- Multimodal multicentre investigation of diagnostic and prognostic markers in disorders of consciousness.Journal: Brain : a journal of neurologyIn common: PyBIDS, structural MRI / diffusion, other condition
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, 30 scripts, and 2 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:cff32307d6f8f6c5…
Add the badge to its README
The badge links the code to this page. Copy one of these into the README of the paper's code: only you decide where it goes, and nothing is changed for you.
Markdown
[, paste the snippet at the top, then “Commit changes…” and, to review it first, “Create a new branch and start a pull request”. You open the pull request; OSCR asks for no permission.
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: questions and error reports about this paper and its code, from signed-in readers and its authors. It opens with sign-in.
Reproductions: reports from readers who ran the authors' code: what they reproduced, with which environment, commit and data. It opens with sign-in.
Activity: what happens around this paper: new versions of its record, its map's validation, discussions and reproductions. It opens with sign-in.
