Sub-region-based patching for improved sub-region-based brain tumor segmentation in 3D MRI scans


Abstract

Early diagnosis of brain tumors is imperative to save lives. However, automated diagnosis faces several challenges, such as the use of 3D MRI scans, which demand substantial computational resources especially since medical images are highly prone to class imbalance, making models biased toward the majority class. Various patching techniques, such as fixed, random, and random biased, have been employed to address these issues. However, they often fail to effectively preserve the entire tumor due to cropped tumor regions. Conversely, overlapping patches that preserve tumor regions exacerbate class imbalance because of redundant background pixels. Furthermore, the number of patches increases as the overlap decreases, resulting in a nonlinear relationship that introduces redundancy and affects overall segmentation performance. Moreover, these techniques do not enable the model to focus on regions of interest corresponding to specific tumor subregions.In this study, we propose a novel subregion based patching technique that selects patches from both the whole tumor region (WT Patch) and the core tumor region (TC Patch) without relying on ground-truth information, thereby making it suitable for inference in segmentation tasks. This patching methodology centers the tumor within each patch, effectively preserving its overall morphology and preventing cropped tumor boundaries. The proposed approach enhances model training by enabling independent learning from distinct subregions. We evaluate our method against state-of-the-art patching methodologies and conduct extensive experiments using the BraTS 2020 dataset. Our findings demonstrate substantial improvements, achieving Dice scores of 96\% for the whole tumor, 90\% for the core tumor, and 92\% for the enhancing tumor region, outperforming existing state-of-the-art methods.
Ask to review this manuscript

Notes for potential reviewers

  • Volunteering is not a guarantee that you will be asked to review. There are many reasons: reviewers must be qualified, there should be no conflicts of interest, a minimum of two reviewers have already accepted an invitation, etc.
  • This is NOT OPEN peer review. The review is single-blind, and all recommendations are sent privately to the Academic Editor handling the manuscript. All reviews are published and reviewers can choose to sign their reviews.
  • What happens after volunteering? It may be a few days before you receive an invitation to review with further instructions. You will need to accept the invitation to then become an official referee for the manuscript. If you do not receive an invitation it is for one of many possible reasons as noted above.

  • PeerJ Computer Science does not judge submissions based on subjective measures such as novelty, impact or degree of advance. Effectively, reviewers are asked to comment on whether or not the submission is scientifically and technically sound and therefore deserves to join the scientific literature. Our Peer Review criteria can be found on the "Editorial Criteria" page - reviewers are specifically asked to comment on 3 broad areas: "Basic Reporting", "Experimental Design" and "Validity of the Findings".
  • Reviewers are expected to comment in a timely, professional, and constructive manner.
  • Until the article is published, reviewers must regard all information relating to the submission as strictly confidential.
  • When submitting a review, reviewers are given the option to "sign" their review (i.e. to associate their name with their comments). Otherwise, all review comments remain anonymous.
  • All reviews of published articles are published. This includes manuscript files, peer review comments, author rebuttals and revised materials.
  • Each time a decision is made by the Academic Editor, each reviewer will receive a copy of the Decision Letter (which will include the comments of all reviewers).

If you have any questions about submitting your review, please email us at [email protected].