9 of 9 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 9 have no contract verdict; 0 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2106.05735.json · badge: /api/ran/2106.05735.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| tamerthamoqa/3D-mri-brain-tumour-image-segmentation-medical-decathlon-tensorflow | community (classifier label) classifier basis not recorded on the link |
9 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| dice_coefficient | Ran ran on a synthesized input |
tamerthamoqa/3D-mri-brain-tumour-image-segmentation-medical-decathlon-tensorflow/segmentation_losses.py code served (permissive licence) · get_code("55c491331fb03c16") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned SymbolicTensor. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| dice_coefficient_binary | Ran ran on a synthesized input |
tamerthamoqa/3D-mri-brain-tumour-image-segmentation-medical-decathlon-tensorflow/segmentation_losses.py code served (permissive licence) · get_code("429dba7efc52d89d") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned SymbolicTensor. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| dice_loss | Ran ran on a synthesized input |
tamerthamoqa/3D-mri-brain-tumour-image-segmentation-medical-decathlon-tensorflow/segmentation_losses.py code served (permissive licence) · get_code("a036a5593e08b1b0") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned SymbolicTensor. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| generate_model_prediction | Ran ran on a synthesized input |
tamerthamoqa/3D-mri-brain-tumour-image-segmentation-medical-decathlon-tensorflow/generate_prediction_files_for_challenge_submission.py code served (permissive licence) · get_code("3712ead23ff0f9b1") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned ndarray, ndim 3, dtype family int, shape (4, 5, 6) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| set_tensorflow_mirrored_strategy_gpu_devices_list | Ran ran on a synthesized input |
tamerthamoqa/3D-mri-brain-tumour-image-segmentation-medical-decathlon-tensorflow/train_unet_segmentation_model.py code served (permissive licence) · get_code("ba859058bfab9035") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned list, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| standardize | Ran ran on a synthesized input |
tamerthamoqa/3D-mri-brain-tumour-image-segmentation-medical-decathlon-tensorflow/generate_prediction_files_for_challenge_submission.py code served (permissive licence) · get_code("4e50db17fbb87fc5") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned ndarray, ndim 4, dtype family float, shape (4, 3, 2, 5) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| unet_3d_conv3dtranspose_dropout | Ran ran on a synthesized input |
tamerthamoqa/3D-mri-brain-tumour-image-segmentation-medical-decathlon-tensorflow/model.py code served (permissive licence) · get_code("85683318706e43ef") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Functional. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| unet_3d_upsampling_batchnormalization | Ran ran on a synthesized input |
tamerthamoqa/3D-mri-brain-tumour-image-segmentation-medical-decathlon-tensorflow/model.py code served (permissive licence) · get_code("0364327269701c67") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Functional. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| unet_3d_upsampling_dropout | Ran ran on a synthesized input |
tamerthamoqa/3D-mri-brain-tumour-image-segmentation-medical-decathlon-tensorflow/model.py code served (permissive licence) · get_code("533b4851f6eba632") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Functional. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
Of 9 samples lifted from this paper's linked repositories, 9 carry a function identity and 0 do not. Of the 9 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 9 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
International challenges have become the de facto standard for comparative assessment of image analysis algorithms given a specific task. Segmentation is so far the most widely investigated medical image processing task, but the various segmentation challenges have typically been organized in isolation, such that algorithm development was driven by the need to tackle a single specific clinical problem. We hypothesized that a method capable of performing well on multiple tasks will generalize well to a previously unseen task and potentially outperform a custom-designed solution. To investigate the hypothesis, we organized the Medical Segmentation Decathlon (MSD) - a biomedical image analysis challenge, in which algorithms compete in a multitude of both tasks and modalities. The underlying data set was designed to explore the axis of difficulties typically encountered when dealing with medical images, such as small data sets, unbalanced labels, multi-site data and small objects. The MSD challenge confirmed that algorithms with a consistent good performance on a set of tasks preserved their good average performance on a different set of previously unseen tasks. Moreover, by monitoring the MSD winner for two years, we found that this algorithm continued generalizing well to a wide range of other clinical problems, further confirming our hypothesis. Three main conclusions can be drawn from this study: (1) state-of-the-art image segmentation algorithms are mature, accurate, and generalize well when retrained on unseen tasks; (2) consistent algorithmic performance across multiple tasks is a strong surrogate of algorithmic generalizability; (3) the training of accurate AI segmentation models is now commoditized to non AI experts.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2106.05735")
get_code_for_paper("2106.05735")
have("2106.05735")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2106.05735.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2106.05735)
Connect an agent — have() is free.