VeNet: a lightweight neural network for efficient brain vessel segmentation in endovascular robotic surgery.
Paper
Loaded from Europe PMC by your browser; OSCR does not store it: doi.org · Europe PMC
The paper is loaded when this pane is shown.
The authors' code
Python · 9 lines · 195 B · no license
- from .vnet import VNET
- from .unet import UNET
- from .fcn import FCN
- from .net import Network
- from . import layers
- from . import metrics
- from . import losses
- from . import misc
- from . import utils
__init__.py at commit 93dbe34, no license · at the source
Overview
- Neurosputnik LLC, Moscow, 101000 Russia
Abstract
The abstract is not reproduced here: the paper's license (CC BY-NC-ND) does not allow it. Read it in the paper, at the publisher or on Europe PMC.
Repositories
Its files are read in the Code ↔ Paper reader above.
git.scinalytics.com/rebis/vessel-segmentator
Availability: 1 check, the latest on 28 September 2026: the link answers (HTTP 200)
- 28 September 2026: the link answers (HTTP 200)
giesekow/deepvesselnet
93dbe3436764da0fc6f7ad7f78cda5a8174728ed, 7 July 2023Availability: 1 check, the latest on 28 September 2026: the link answers
- 28 September 2026: the link answers
13 files
- dvn/
__init__.py , Python, 9 lines - dvn/
fcn.py , Python, 122 lines - dvn/
layers.py , Python, 155 lines - dvn/
losses.py , Python, 75 lines - dvn/
metrics.py , Python, 35 lines - dvn/
misc.py , Python, 9 lines - dvn/
net.py , Python, 263 lines - dvn/
unet.py , Python, 221 lines - dvn/
utils.py , Python, 227 lines - dvn/
vnet.py , Python, 236 lines - example.py, Python, 18 lines
- setup.py, Python, 12 lines
- README.md, Text, 26 lines
Code availability statement
The paper has a code availability statement. Its license (CC BY-NC-ND) does not allow reproducing it here; in short, from what the harvester recognized in it:
- it points to the authors' code: git.scinalytics.com/
rebis/ vessel-segmentator
Read it in the paper: doi.org/10.1038/s41598-026-54176-x.
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:
- 2 repositories of the authors' code, each at its verified commit, with its license and how the link was found in the paper;
- 12 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
Datasets cited
- openneuro:ds003949, at OpenNeuro; found in the references
Data availability statement
The paper has a data availability statement. Its license (CC BY-NC-ND) does not allow reproducing it here; in short, from what the harvester recognized in it:
- no repository, dataset or request procedure was recognized in it
Read it in the paper: doi.org/10.1038/s41598-026-54176-x.
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, 28 September 2026: the first record
Recorded: type, language, journal, volume, issue, pages, dates, 1 author, 20 keywords, 7 MeSH terms, 23 references.
Cite
This paper
Bernadotte, A. (2026). VeNet: a lightweight neural network for efficient brain vessel segmentation in endovascular robotic surgery. Scientific reports, 16(1), 24566. https://
BibTeX
@article{bernadotte2026v
author = {Bernadotte, Alexandra},
title = {{VeNet: a lightweight neural network for efficient brain vessel segmentation in endovascular robotic surgery}},
journal = {Scientific reports},
year = {2026},
month = may,
volume = {16},
number = {1},
pages = {24566},
publisher = {Nature Publishing Group},
issn = {2045-2322},
doi = {10.1038/
url = {https://
pmid = {42215575},
pmcid = {PMC13454300}
}
RIS
TY - JOUR
AU - Bernadotte, Alexandra
TI - VeNet: a lightweight neural network for efficient brain vessel segmentation in endovascular robotic surgery
T2 - Scientific reports
J2 - Sci Rep
PY - 2026
DA - 2026/
VL - 16
IS - 1
SP - 24566
SN - 2045-2322
PB - Nature Publishing Group
DO - 10.1038/
UR - https://
LA - en
ER -
CSL-JSON
{
"id": "10.1038/
"type": "article-journal",
"title": "VeNet: a lightweight neural network for efficient brain vessel segmentation in endovascular robotic surgery",
"container-title": "Scientific reports",
"author": [
{
"family": "Bernadotte",
"given": "Alexandra"
}
],
"container-title-short":
"volume": "16",
"issue": "1",
"page": "24566",
"DOI": "10.1038/
"PMID": "42215575",
"PMCID": "PMC13454300",
"ISSN": "2045-2322",
"publisher": "Nature Publishing Group",
"URL": "https://
"language": "en",
"issued": {
"date-parts": [
[
2026,
5,
29
]
]
}
}
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.1038/s41597-025-06354-1 [code]
- Semi-automatic annotation of brain vessels in magnetic resonance angiography images.Journal: Scientific dataIn common: Matplotlib, NumPy, 15 references, author Alexandra Bernadotte
- [2] doi:10.1007/s12021-022-09597-0 [code]
- Towards Automated Brain Aneurysm Detection in TOF-MRA: Open Data, Weak Labels, and Anatomical Knowledge.Journal: NeuroinformaticsIn common: SimpleITK, TensorFlow, scikit-learn, 2 other tools, OpenNeuro ds003949, 1 reference
- [3] doi:10.1016/j.nicl.2025.103835 [code]
- Assessing workflow impact and clinical utility of AI-assisted brain aneurysm detection: A multi-reader study.Journal: NeuroImage. ClinicalIn common: SimpleITK, scikit-learn, Matplotlib, 1 other tool, OpenNeuro ds003949, 1 reference
- [4] doi:10.1186/s41747-024-00512-7 [code]
- Quantitative modeling of lenticulostriate arteries on 7-T TOF-MRA for cerebral small vessel disease.Journal: European radiology experimentalIn common: SimpleITK, Keras, TensorFlow, 3 other tools, 1 reference
- [5] doi:10.1002/hbm.25788 [code]
- Privacy-preserving quality control of neuroimaging datasets in federated environments.Journal: Human brain mappingIn common: Matplotlib, NumPy, OpenNeuro ds003949, 1 reference
- [6] doi:10.7554/elife.81217 [code]
- A generalizable brain extraction net (BEN) for multimodal MRI data from rodents, nonhuman primates, and humans.Journal: eLifeIn common: SimpleITK, Keras, TensorFlow, 2 other tools, 2 references
- [7] doi:10.1371/journal.pone.0291946 [code]
- U-Net based vessel segmentation for murine brains with small micro-magnetic resonance imaging reference datasets.Journal: PloS oneIn common: Keras, TensorFlow, scikit-learn, 2 other tools, 2 references
- [8] doi:10.1111/acel.70656 [code]
- Deep Learning Predicts Hematopoietic Stem Cell Aging From 3D Chromatin Images.Journal: Aging cellIn common: SimpleITK, Keras, TensorFlow, 3 other tools, 1 reference
- [9] doi:10.1038/s41598-024-59529-y [code]
- Streamlining neuroradiology workflow with AI for improved cerebrovascular structure monitoring.Journal: Scientific reportsIn common: Matplotlib, NumPy, 4 references
- [10] doi:10.1038/s43856-024-00452-8 [code]
- Multi-scale V-net architecture with deep feature CRF layers for brain extraction.Journal: Communications medicineIn common: Keras, TensorFlow, scikit-learn, 2 other tools, 2 references
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: 2 repositories of the authors' code, each at its verified commit and with its license, 12 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:1cca39e8c9248fe1…
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.1038/s41598-026-54176-x)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1038/s41598-026-54176-x.svg
:target: https://openscicode.org/badge/doi/10.1038/s41598-026-54176-x
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1038/s41598-026-54176-x"><img src="https://openscicode.org/badge/doi/10.1038/s41598-026-54176-x.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.
