Papers › Deep Residual Learning for Instrument Segmentation in Robotic Surgery

Deep Residual Learning for Instrument Segmentation in Robotic Surgery

24 Mar 2017arXiv:1703.08580archive 2025-07-28

Daniil Pakhomov, Vittal Premachandran, Max Allan, Mahdi Azizian, Nassir Navab

Detection, tracking, and pose estimation of surgical instruments are crucial tasks for computer assistance during minimally invasive robotic surgery. In the majority of cases, the first step is the automatic segmentation of surgical tools. Prior work has focused on binary segmentation, where the objective is to label every pixel in an image as tool or background. We improve upon previous work in two major ways. First, we leverage recent techniques such as deep residual learning and dilated convolutions to advance binary-segmentation performance. Second, we extend the approach to multi-class segmentation, which lets us segment different parts of the tool, in addition to background. We demonstrate the performance of this method on the MICCAI Endoscopic Vision Challenge Robotic Instruments dataset.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 16 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 7 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 16 samples from 1 repository, 9 ran (9 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

warmspringwinds/tf-image-segmentation officialmentioned in papertfMITSyntology: 16 samples, 9 ran (0 instrument-failed) · 7 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

16 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 7 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

9ran
7unverified

Licence: 0 of the 16 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from warmspringwinds/tf-image-segmentation. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

warmspringwinds/tf-image-segmentation official repository 16 samples, 9 ran (0 instrument-failed) · 7 unverified
adapt_network_for_any_size_input tf_image_segmentation/utils/inference.py ran MIT (permissive) · 4359515ade0190b2 · report fixture: signature network_definition:callable/0/?, multiple:int/0/int · returned function · level recorded 2026-09-25
extract_resnet_v1_101_mapping_without_logits tf_image_segmentation/models/resnet_v1_101_16s.py ran MIT (permissive) · 1ca308b0e3d3840e · report fixture: signature resnet_v1_101_variables_mapping:dict/0/? · returned dict · level recorded 2026-09-25
extract_resnet_v1_101_mapping_without_logits tf_image_segmentation/models/resnet_v1_101_8s.py ran MIT (permissive) · dce7e9ebac981a57 · report fixture: signature resnet_v1_101_variables_mapping:dict/0/? · returned dict · level recorded 2026-09-25
extract_resnet_v1_50_mapping_without_logits tf_image_segmentation/models/resnet_v1_50_16s.py ran MIT (permissive) · e538d54ccfc701f8 · report fixture: signature resnet_v1_50_variables_mapping:dict/0/? · returned dict · level recorded 2026-09-25
extract_resnet_v1_50_mapping_without_logits tf_image_segmentation/models/resnet_v1_50_8s.py ran MIT (permissive) · 61fc650a7f68fc4a · report fixture: signature resnet_v1_50_variables_mapping:dict/0/? · returned dict · level recorded 2026-09-25
extract_vgg_16_mapping_without_fc8 tf_image_segmentation/models/fcn_32s.py ran MIT (permissive) · 11feb12c23a9f03c · report fixture: signature vgg_16_variables_mapping:dict/0/? · returned dict · level recorded 2026-09-25
get_pascal_segmentation_images_lists_txts tf_image_segmentation/utils/pascal_voc.py ran fingerprinted MIT (permissive) · c405b340e7f4e858 · report fixture: signature pascal_root:str/0/str · returned list · level recorded 2026-09-25
readlines_with_strip tf_image_segmentation/utils/pascal_voc.py ran MIT (permissive) · e9e203e4d1704515 · report fixture: signature filename:str/0/str · returned map · level recorded 2026-09-25
readlines_with_strip_array_version tf_image_segmentation/utils/pascal_voc.py ran MIT (permissive) · 8a2c544abbc18524 · report fixture: signature filenames_array:list/1/str · returned map · level recorded 2026-09-25
flip_randomly_left_right_image_with_annotation tf_image_segmentation/utils/augmentation.py unverified MIT (permissive) · c4a68881ddce43a9 · report
get_labels_from_annotation tf_image_segmentation/utils/training.py unverified MIT (permissive) · 5fefe8dd75043606 · report
get_labels_from_annotation_batch tf_image_segmentation/utils/training.py unverified MIT (permissive) · 8eec1ab0d186c23a · report
get_valid_entries_indices_from_annotation_batch tf_image_segmentation/utils/training.py unverified MIT (permissive) · 1628f33956d273dd · report
read_image_annotation_pairs_from_tfrecord tf_image_segmentation/utils/tf_records.py unverified MIT (permissive) · b8697c1aeb6fcad3 · report
read_tfrecord_and_decode_into_image_annotation_pair_tensors tf_image_segmentation/utils/tf_records.py unverified MIT (permissive) · d7acb3c7d6d07504 · report
scale_randomly_image_with_annotation_with_fixed_size_output tf_image_segmentation/utils/augmentation.py unverified MIT (permissive) · 87f8012060afbcb8 · report

Tasks

Pose EstimationSegmentation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections