OSCR

Improved prediction of glioma-related aphasia by diffusion MRI metrics, machine learning, and automated fiber bundle segmentation.

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

The Code ↔ Paper reader is built for the 6,000 most recent papers only: this paper's code is read at its source.

CUBIGL/Predicting_aphasia_based_on_diffusion_MRI_metrics_using_ML_with_automatic_fiber_bundle_segmentation

License: none: the authors keep all their rights
State: the link is dead

CUB-IGL/Predicting_aphasia_based_on_diffusion_MRI_metrics_using_ML_with_automatic_fiber_bundle_segmentation

License: none: the authors keep all their rights
State: the link is dead

Overview

Authors: Boshra Shams, Klara Reisch, Peter Vajkoczy, Christoph Lippert, Thomas Picht, Lucius S Fekonja
Journal: Human brain mapping
Published: 15 June 2023
Type: Research article
Status: dead link (how the code is found and verified)
DOI: 10.1002/hbm.26393
License: CC BY-NC
Institutions: Humboldt-Universität zu Berlin (Germany), Cluster of Excellence "Matters of Activity. Image Space Material" (Germany), Charité – Universitätsmedizin Berlin (Germany), Hasso Plattner Institute (Germany), University of Potsdam (Germany), Icahn School of Medicine at Mount Sinai (United States)
Categories: structural MRI / diffusion (modality), human (organism), other condition (population)

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.1002/hbm.26393.svg)](https://openscicode.org/badge/doi/10.1002/hbm.26393)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/doi/10.1002/hbm.26393.svg
   :target: https://openscicode.org/badge/doi/10.1002/hbm.26393
   :alt: OSCR

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

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).