# Bilateral Filter not working

**URL:** <https://discourse.slicer.org/t/bilateral-filter-not-working/9797>\
**Category:** Support\
**Created:** [January 13, 2020, 9:45pm UTC](https://discourse.slicer.org/t/bilateral-filter-not-working/9797 "2020-01-13T21:45:15Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [January 16, 2020, 9:13pm UTC](https://discourse.slicer.org/t/bilateral-filter-not-working/9797/9 "2020-01-16T21:13:50Z")

</div>

> [@blowekamp](#):
>
> The basic filters ( the ones that don’t have a mini-pipeline internally ) only reports progress when the a thread is completely done

Wow, this is a significant regression. If the performance improvement is marginal (such as in case of bilateral filter’s 272sec vs 283sec - 5% faster) then probably many people would prefer the old behavior (slightly slower but with consistent progress reporting) for interactive use. I’ve start a discussion on this on the ITK forum ([No progress reporting in ITK5 - Engineering - ITK](https://discourse.itk.org/t/no-progress-reporting-in-itk5/2630)).

---

_[View the full topic](https://discourse.slicer.org/t/bilateral-filter-not-working/9797)._