OSCR

A rapid streamline-based extension of Tractfinder for white matter tract segmentation.

Code ↔ Paper

The paper beside its authors' code: matches between them have not been computed for this paper yet.

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 · 103 lines · 3.5 KB · no license

  1. # Copyright (c) 2008-2019 the MRtrix3 contributors.
  2. #
  3. # This Source Code Form is subject to the terms of the Mozilla Public
  4. # License, v. 2.0. If a copy of the MPL was not distributed with this
  5. # file, You can obtain one at http://mozilla.org/MPL/2.0/.
  6. #
  7. # Covered Software is provided under this License on an "as is"
  8. # basis, without warranty of any kind, either expressed, implied, or
  9. # statutory, including, without limitation, warranties that the
  10. # Covered Software is free of defects, merchantable, fit for a
  11. # particular purpose or non-infringing.
  12. # See the Mozilla Public License v. 2.0 for more details.
  13. #
  14. # For more details, see http://www.mrtrix.org/.
  15. import os, sys
  16. try:
  17. # since importlib code below only works on Python 3.5+
  18. # https://stackoverflow.com/a/50395128
  19. if sys.version_info < (3,5):
  20. raise ImportError
  21. import importlib.util
  22. def imported(lib_path):
  23. try:
  24. spec = importlib.util.spec_from_file_location('mrtrix3', os.path.join (lib_path, 'mrtrix3', '__init__.py'))
  25. module = importlib.util.module_from_spec (spec)
  26. sys.modules[spec.name] = module
  27. spec.loader.exec_module (module)
  28. return True
  29. except (ImportError, FileNotFoundError):
  30. return False
  31. except ImportError:
  32. try:
  33. import imp
  34. except ImportError:
  35. print ('failed to import either imp or importlib module!')
  36. sys.exit(1)
  37. def imported(lib_path):
  38. success = False
  39. fp = None
  40. try:
  41. fp, pathname, description = imp.find_module('mrtrix3', [ lib_path ])
  42. imp.load_module('mrtrix3', fp, pathname, description)
  43. success = True
  44. except ImportError:
  45. pass
  46. finally:
  47. if fp:
  48. fp.close()
  49. return success
  50. # First: check the MRTRIX_HOME environment variable
  51. if imported (os.path.join (os.environ['MRTRIX_HOME'], 'lib')) \
  52. if 'MRTRIX_HOME' in os.environ else False:
  53. pass
  54. # Can the MRtrix3 Python modules be found based on their relative location to this file?
  55. # Note that this includes the case where this file is a softlink within an external module,
  56. # which provides a direct link to the core installation
  57. elif not imported (os.path.normpath (os.path.join ( \
  58. os.path.dirname (os.path.realpath (__file__)), os.pardir, 'lib') )):
  59. # If this file is a duplicate, which has been stored in an external module,
  60. # we may be able to figure out the location of the core library using the
  61. # build script.
  62. # case 1: build is a symbolic link:
  63. if not imported (os.path.join (os.path.dirname (os.path.realpath ( \
  64. os.path.join (os.path.dirname(__file__), os.pardir, 'build'))), 'lib')):
  65. # case 2: build is a file containing the path to the core build script:
  66. try:
  67. with open (os.path.join (os.path.dirname(__file__), os.pardir, 'build')) as fp:
  68. for line in fp:
  69. build_path = line.split ('#',1)[0].strip()
  70. if build_path:
  71. break
  72. except IOError:
  73. pass
  74. if not imported (os.path.join (os.path.dirname (build_path), 'lib')):
  75. # Last resort: find the MRtrix3 library via mrconvert on the PATH
  76. import shutil
  77. _mrconvert = shutil.which ('mrconvert')
  78. if not (_mrconvert and imported (os.path.normpath (os.path.join (
  79. os.path.dirname (os.path.realpath (_mrconvert)), os.pardir, 'lib')))):
  80. sys.stderr.write('''
  81. ERROR: Unable to locate MRtrix3 Python modules
  82. For detailed instructions, please refer to:
  83. https://mrtrix.readthedocs.io/en/latest/tips_and_tricks/external_modules.html
  84. ''')
  85. sys.stderr.flush()
  86. sys.exit(1)

mrtrix3.py at commit 2475f4b, no license · at the source

Overview

Authors: Dana Kanel1, Fiona Young2, Kiran K Seunarine1, Chris A Clark1, Kristian Aquilina3, Jonathan D Clayden1
  1. Developmental Imaging and Biophysics Section, UCL GOS Institute of Child Health, London, United Kingdom
  2. Software Engineering and Artificial Intelligence Science Technology Platform, The Francis Crick Institute, London, United Kingdom
  3. Department of Neurosurgery, Great Ormond Street Hospital for Children, London, United Kingdom
Institutions: University College London (United Kingdom); The Francis Crick Institute (United Kingdom); Great Ormond Street Hospital (United Kingdom)
Journal: Frontiers in neuroimaging, volume 5, article 1873040
Dates: received 5 May 2026; accepted 22 June 2026; published online 6 July 2026
Type: Methods article · Language: English
License: CC BY
Identifiers: DOI 10.3389/fnimg.2026.1873040 · PMID 42519527 · PMCID PMC13381243 · OpenAlex W7167459982
Open access: gold, a free copy (OpenAlex)
Status: code verified (how the code is found and verified)
Categories: structural MRI / diffusion (modality), other condition (population), methods / tools (subfield)
Methods: Connectivity, fMRI & imaging, Physiology & signal measures
Keywords: dMRI, paediatric brain tumours, pre-operative, tract segmentation, tractography
Topic: Advanced Neuroimaging Techniques and Applications (Radiology, Nuclear Medicine and Imaging, Medicine), according to OpenAlex
Citations: not cited yet (Europe PMC); 20 references in the paper

Abstract

Accurate delineation of white matter tracts is critical in the pre-operative assessment of paediatric brain tumour patients, where preservation of eloquent pathways directly influences surgical planning and functional outcomes. Tractfinder is a recently introduced automated method for white matter tract segmentation in tumour patients, but its voxel-based (mask) outputs limit compatibility with streamline-based tractography tools, visualisation workflows, and downstream analytical frameworks. Here we introduce Tractfinder-constrained Tractography (TcT), a streamline-based extension that constrains probabilistic tractography to the probability maps produced by Tractfinder, generating streamline representations while preserving the speed and automation that make Tractfinder clinically appealing. We evaluated TcT in ten pre-operative paediatric patients with supratentorial tumours, targeting three clinically relevant tracts – the corticospinal tract, arcuate fasciculus, and optic radiation. Spatial agreement between TcT and conventional tractography was assessed using Bundle Adjacency (BA). Mean BA scores across all three tracts ranged from 2.1 to 2.6 mm, comparing favourably against published inter-protocol benchmarks for conventional probabilistic tractography (4.3 mm), and approaching within-protocol variability. The TcT pipeline was fully automated, required no manual region-of-interest placement, and completed in approximately 5–15 min per subject compared to 1–2 h for conventional tractography. These results demonstrate that TcT produces streamline-based tract segmentations with good spatial agreement to conventional tractography, while offering substantially reduced processing time and operator burden.

Reproduced under the paper's license (CC BY), from the paper cited above.

Repositories

Its files are read in the Code ↔ Paper reader above.

tractfinder/tractfinder

License: none: the authors keep all their rights
State: the link answers, verified on 27 September 2026
Evidence: files inventoried
Commit: 2475f4bd82013cb3e265c5aee9a294636273cd7d, 5 June 2026
Languages: Python (6)
Size: 13 files, 6 scripts
Software Heritage: not archived
Found in: “Data availability statement”
Holds: README, environment (pyproject.toml, uv.lock)
Not found: license file, CITATION.cff, tests, continuous integration, documentation
Tools: NumPy (3 files), MRtrix3 (2 files), scikit-image (1 file), SciPy (1 file)
Availability: 1 check, the latest on 27 September 2026: the link answers
  • 27 September 2026: the link answers
7 files

fionaEyoung/tractfinder

License: none: the authors keep all their rights
State: the link answers, verified on 29 October 2026
Evidence: files inventoried
Commit: cae273ff731ae16652de572ed18e858c42b804db, 13 October 2026
Languages: Python (6)
Size: 13 files, 6 scripts
Software Heritage: not archived
Found in: the Zenodo archive record
Holds: README, environment (pyproject.toml, uv.lock)
Not found: license file, CITATION.cff, tests, continuous integration, documentation
Tools: NumPy (3 files), MRtrix3 (2 files), scikit-image (1 file), SciPy (1 file)
Availability: 2 checks, the latest on 29 October 2026: the link answers
  • 29 October 2026: the link answers
  • 27 September 2026: the link answers
7 files

The paper's code and data availability statement is in the Data section.

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

No dataset and no data link were found in the paper.

Data availability statement

Scripts for running Tractfinder and generating custom tract atlases are available at: https://github.com/tractfinder/tractfinder. Tract orientation atlases (and corresponding training streamlines) for the AF, CST, and OR are openly available for non-commercial use: https://doi.org/10.5281/zenodo.10149873. The clinical neuroimaging data from Great Ormond Street Hospital cannot be publicly shared to maintain patient confidentiality. Requests to access these datasets should be directed to .

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 National Institute for Health and Care Research; CHILDREN with CANCER UK: 23-353; Great Ormond Street Institute of Child Health

Version 1, 27 September 2026: the first record

Recorded: type, language, journal, volume, pages, dates, 6 authors, 5 keywords, 18 references.

Cite

This paper

Kanel, D., Young, F., Seunarine, K. K., Clark, C. A., Aquilina, K., & Clayden, J. D. (2026). A rapid streamline-based extension of Tractfinder for white matter tract segmentation. Frontiers in neuroimaging, 5, 1873040. https://doi.org/10.3389/fnimg.2026.1873040

BibTeX

@article{kanel2026rapid,
author = {Kanel, Dana and Young, Fiona and Seunarine, Kiran K and Clark, Chris A and Aquilina, Kristian and Clayden, Jonathan D},
title = {{A rapid streamline-based extension of Tractfinder for white matter tract segmentation}},
journal = {Frontiers in neuroimaging},
year = {2026},
month = jul,
volume = {5},
pages = {1873040},
publisher = {Frontiers Media SA},
issn = {2813-1193},
doi = {10.3389/fnimg.2026.1873040},
url = {https://doi.org/10.3389/fnimg.2026.1873040},
pmid = {42519527},
pmcid = {PMC13381243}
}

RIS

TY - JOUR
AU - Kanel, Dana
AU - Young, Fiona
AU - Seunarine, Kiran K
AU - Clark, Chris A
AU - Aquilina, Kristian
AU - Clayden, Jonathan D
TI - A rapid streamline-based extension of Tractfinder for white matter tract segmentation
T2 - Frontiers in neuroimaging
J2 - Front Neuroimaging
PY - 2026
DA - 2026/07/06
VL - 5
SP - 1873040
SN - 2813-1193
PB - Frontiers Media SA
DO - 10.3389/fnimg.2026.1873040
UR - https://doi.org/10.3389/fnimg.2026.1873040
LA - en
ER -

CSL-JSON

{
"id": "10.3389/fnimg.2026.1873040",
"type": "article-journal",
"title": "A rapid streamline-based extension of Tractfinder for white matter tract segmentation",
"container-title": "Frontiers in neuroimaging",
"author": [
{
"family": "Kanel",
"given": "Dana"
},
{
"family": "Young",
"given": "Fiona"
},
{
"family": "Seunarine",
"given": "Kiran K"
},
{
"family": "Clark",
"given": "Chris A"
},
{
"family": "Aquilina",
"given": "Kristian"
},
{
"family": "Clayden",
"given": "Jonathan D"
}
],
"container-title-short": "Front Neuroimaging",
"volume": "5",
"page": "1873040",
"DOI": "10.3389/fnimg.2026.1873040",
"PMID": "42519527",
"PMCID": "PMC13381243",
"ISSN": "2813-1193",
"publisher": "Frontiers Media SA",
"URL": "https://doi.org/10.3389/fnimg.2026.1873040",
"language": "en",
"issued": {
"date-parts": [
[
2026,
7,
6
]
]
}
}

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.1002/hbm.26578 [code]
Fibre orientation atlas guided rapid segmentation of white matter tracts.
Journal: Human brain mapping
In common: MRtrix3, scikit-image, SciPy, 1 other tool, methods / tools, structural MRI / diffusion, other condition, 13 references, author Kristian Aquilina
[2] doi:10.1007/s11548-022-02617-z
Fibre tract segmentation for intraoperative diffusion MRI in neurosurgical patients using tract-specific orientation atlas and tumour deformation modelling.
Journal: International journal of computer assisted radiology and surgery
In common: methods / tools, structural MRI / diffusion, other condition, 6 references, author Kristian Aquilina
[3] doi:10.1002/hbm.26239 [code]
Integrated diffusion image operator (iDIO): A pipeline for automated configuration and processing of diffusion MRI data.
Journal: Human brain mapping
In common: MRtrix3, scikit-image, SciPy, 1 other tool, methods / tools, structural MRI / diffusion, 7 references
[4] doi:10.1038/s41597-021-01080-w [code]
CHIASM, the human brain albinism and achiasma MRI dataset.
Journal: Scientific data
In common: MRtrix3, SciPy, NumPy, methods / tools, structural MRI / diffusion, other condition, 8 references
[5] doi:10.3389/fninf.2022.777853 [code]
Assessing the Reliability of Template-Based Clustering for Tractography in Healthy Human Adults.
Journal: Frontiers in neuroinformatics
In common: MRtrix3, SciPy, NumPy, methods / tools, structural MRI / diffusion, 7 references
[6] doi:10.1002/hbm.70491 [code]
Multi-Centre Reproducibility of DTI and NODDI in White Matter Tracts Segmented Using TractFinder Across Three MRI Scanners of the Same Model.
Journal: Human brain mapping
In common: MRtrix3, methods / tools, structural MRI / diffusion, 7 references
[7] doi:10.1162/imag.a.49 [code]
Mapping the aggregate g-ratio of white matter tracts using multi-modal MRI.
Journal: Imaging neuroscience (Cambridge, Mass.)
In common: MRtrix3, scikit-image, SciPy, 1 other tool, structural MRI / diffusion, 6 references
[8] doi:10.1162/imag_a_00125 [code]
Optimization and validation of the DESIGNER preprocessing pipeline for clinical diffusion MRI in white matter aging.
Journal: Imaging neuroscience (Cambridge, Mass.)
In common: MRtrix3, scikit-image, SciPy, 1 other tool, methods / tools, structural MRI / diffusion, 5 references
[9] doi:10.1162/netn_a_00330 [code]
The human brain connectome weighted by the myelin content and total intra-axonal cross-sectional area of white matter tracts.
Journal: Network neuroscience (Cambridge, Mass.)
In common: MRtrix3, SciPy, NumPy, structural MRI / diffusion, 7 references
[10] doi:10.1038/s41467-026-68714-8 [code]
Two axes of white matter development.
Journal: Nature communications
In common: MRtrix3, scikit-image, SciPy, 1 other tool, structural MRI / diffusion, 5 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.

Add the badge to the code's README

OSCR: the badge of this paper

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 -->
[![OSCR](https://openscicode.org/badge/doi/10.3389/fnimg.2026.1873040.svg)](https://openscicode.org/badge/doi/10.3389/fnimg.2026.1873040)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/doi/10.3389/fnimg.2026.1873040.svg
   :target: https://openscicode.org/badge/doi/10.3389/fnimg.2026.1873040
   :alt: OSCR

.. oscr-badge:end
HTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.3389/fnimg.2026.1873040"><img src="https://openscicode.org/badge/doi/10.3389/fnimg.2026.1873040.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.