# How to compute contours in parallel?

**URL:** https://discourse.paraview.org/t/how-to-compute-contours-in-parallel/7046
**Category:** ParaView Support
**Created:** [April 22, 2021, 5:22pm UTC](https://discourse.paraview.org/t/how-to-compute-contours-in-parallel/7046 "2021-04-22T17:22:01Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![robertsawko](https://discourse.paraview.org/user_avatar/discourse.paraview.org/robertsawko/32/6283_2.png) [@robertsawko](https://discourse.paraview.org/u/robertsawko)
#### Post date: [April 23, 2021, 11:54am UTC](https://discourse.paraview.org/t/how-to-compute-contours-in-parallel/7046/3 "2021-04-23T11:54:44Z")

</div>

Apologies, this is now looking like a mind dump, but writing the previous post I had an epiphany and changed the order of my filters. The reason why ghost cell generator filter wasn’t active was due to multi-block data structure of my data source. Now my filter order is:

1. `MergeBlocks`
2. `GhostCellGenerator`
3. `CellDatatoPointData` (with _Piece Invariant_ checked)
4. `Contour`
5. `Connectivity`

And it produces good looking surfaces.

Please advise if you think this is still somehow inefficient or may cause issues with accuracy when a number of objects increases substantially. Otherwise, I hope someone may find these notes helpful.

---

_[View the full topic](https://discourse.paraview.org/t/how-to-compute-contours-in-parallel/7046)._