OSCR

Block oscr:b:ZH9EKFRCJM77W-K

A block of code linked to a paper, with an identifier OSCR gives it for good: it is never reused nor deleted. What a block identifier is · this block in JSON

Identifier
oscr:b:ZH9EKFRCJM77W-K
Status
Current: the registry links these lines to the paper today.
Paper
doi:10.1038/s41598-021-01681-w · its page here
Code
github.com/imaging-ai-for-health-virtual-lab/slice-level-data-leakage, model_training.py, lines 358 to 449 (train_on_array)
Commit read
ef680d46d156d895f18b15726893aed5a1724137
SWHID
swh:1:cnt:56d3301b3a460cd4e217353476c257b56efad493;origin=https://github.com/imaging-ai-for-health-virtual-lab/slice-level-data-leakage;anchor=swh:1:rev:ef680d46d156d895f18b15726893aed5a1724137;path=/model_training.py;lines=358-449 (the Software Heritage identifier of the file as its authors published it, before any email address is hidden for display; it opens in Software Heritage's archive once the repository is archived there)
In the paper
paragraph 54 (Materials and methods › Model training and validation); paragraph 55 (Materials and methods › Model training and validation)
Linked by
the registry's matching program (lexical-v1), which can be wrong
Identifier given
2026-11-18

Open these lines beside the paper

Cite this block

Copy this text: the identifier and its page first, then the code, the paper and the SWHID.

Code block oscr:b:ZH9EKFRCJM77W-K (https://openscicode.org/b/oscr:b:ZH9EKFRCJM77W-K)
model_training.py, lines 358 to 449, in github.com/imaging-ai-for-health-virtual-lab/slice-level-data-leakage (https://github.com/imaging-ai-for-health-virtual-lab/slice-level-data-leakage), commit ef680d46d156d895f18b15726893aed5a1724137.
Paper: https://doi.org/10.1038/s41598-021-01681-w
SWHID: swh:1:cnt:56d3301b3a460cd4e217353476c257b56efad493;origin=https://github.com/imaging-ai-for-health-virtual-lab/slice-level-data-leakage;anchor=swh:1:rev:ef680d46d156d895f18b15726893aed5a1724137;path=/model_training.py;lines=358-449