# Computer slows down after volume is oversampled

**URL:** <https://discourse.slicer.org/t/computer-slows-down-after-volume-is-oversampled/15743>\
**Category:** Support\
**Tags:** segmentation\
**Created:** [January 30, 2021, 6:38am UTC](https://discourse.slicer.org/t/computer-slows-down-after-volume-is-oversampled/15743 "2021-01-30T06:38:16Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [February 5, 2021, 4:15am UTC](https://discourse.slicer.org/t/computer-slows-down-after-volume-is-oversampled/15743/21 "2021-02-05T04:15:12Z")

</div>

> [@Jason\_Wong](#):
>
> Also, are there any peer-reviewed journals or articles where the oversampling algorithm was first introduce?

Oversampling is fairly straightforward (simple image resampling). It is probably mentioned in this segmentation infrastructure paper:

Pinter, C., Lasso, A., & Fichtinger, G. (2019). Polymorph segmentation representation for medical image computing. Computer Methods and Programs in Biomedicine, 171, 19–26. [Redirecting](https://doi.org/10.1016/j.cmpb.2019.02.011)

[Previous page](https://discourse.slicer.org/t/computer-slows-down-after-volume-is-oversampled/15743.md?page=1)