# how coprocess render the image for distributed cases

**URL:** https://discourse.paraview.org/t/how-coprocess-render-the-image-for-distributed-cases/4702
**Category:** In Situ Support
**Created:** [June 28, 2020, 3:57am UTC](https://discourse.paraview.org/t/how-coprocess-render-the-image-for-distributed-cases/4702 "2020-06-28T03:57:48Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![Kenneth\_Moreland](https://discourse.paraview.org/user_avatar/discourse.paraview.org/kenneth_moreland/32/15033_2.png) [@Kenneth\_Moreland](https://discourse.paraview.org/u/Kenneth_Moreland)
#### Post date: [June 29, 2020, 12:51pm UTC](https://discourse.paraview.org/t/how-coprocess-render-the-image-for-distributed-cases/4702/8 "2020-06-29T12:51:56Z")

</div>

It _is_ possible to replace the IceT communicator to use something other than MPI. IceT has its own abstraction for a communicator, and you can write one that does not use MPI.

The reason why the one in ParaView/Catalyst uses MPI directly rather than `vtkCommunicator` is that IceT requires asynchronous sends and receives (i.e. `ISend` and `IRecv`) and `vtkCommunicator` does not support these.

If `MochiCommunicator` supports asynchronous sends/receives, it should be possible to have the IceT library use it.

---

_[View the full topic](https://discourse.paraview.org/t/how-coprocess-render-the-image-for-distributed-cases/4702)._