# Raytracing in batch mode - progressive passes are ignored

**URL:** https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139
**Category:** ParaView Support
**Created:** [May 23, 2023, 8:43am UTC](https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139 "2023-05-23T08:43:07Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![flotus1](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/7ea924/32.png) [@flotus1](https://discourse.paraview.org/u/flotus1)
#### Post date: [May 23, 2023, 8:43am UTC](https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139/1 "2023-05-23T08:43:07Z")

</div>

I am getting inconsistent results between exporting screenshots from the GUI, and exporting them in batch mode. Specifically when using “progressive passes” in order to keep interactivity up, while still getting high quality visualization.

This is the image I get when exporting a screenshot from the GUI. 1 sample per pixel, 32 progressive passes:

 ![test1_progressive32_gui](https://discourse.paraview.org/uploads/default/original/2X/7/79075c059cd9f9160ceefd1cbf6de7482d72c142.jpeg)

Same settings, but exported the image in batch mode via python script. Note how the quality is basically what I get in the GUI without progressive passes

 ![test1_progressive32_batch](https://discourse.paraview.org/uploads/default/original/2X/e/ebffebf0907f991cb0516b98d6bfb2ad6a8163e2.png)

And lastly, the same image from batch mode, but with 32 samples per pixel, and no progressive passes. This is the quality I expected.

 ![test1_samplesperpixel32_batch](https://discourse.paraview.org/uploads/default/original/2X/3/39c48f7e03764bfa0c824b8737fc8aec2dc53058.jpeg)

Should I just avoid the progressive passes feature with batch processing in mind?

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 23, 2023, 8:47am UTC](https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139/2 "2023-05-23T08:47:48Z")

</div>

> [@flotus1](#):
>
> Should I just avoid the progressive passes feature with batch processing in mind?

Definitely. Progressive passes do not make much sense in batch mode and I suspect only one pass is done in that case.

@Dave_DeMarle

---

<div class="post-metadata">

### Author: ![flotus1](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/7ea924/32.png) [@flotus1](https://discourse.paraview.org/u/flotus1)
#### Post date: [May 23, 2023, 9:06am UTC](https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139/3 "2023-05-23T09:06:01Z")

</div>

I see, thanks.  
Though that is a bit of a bummer. The user experience while trying to compose the scene is very different between “high number of progressive passes” and “high number of samples per pixel”

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 23, 2023, 9:06am UTC](https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139/4 "2023-05-23T09:06:55Z")

</div>

Wdym ? There is no user interactivity at all in batch mode. Just turn progressive pass off in your script.

---

<div class="post-metadata">

### Author: ![flotus1](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/7ea924/32.png) [@flotus1](https://discourse.paraview.org/u/flotus1)
#### Post date: [May 23, 2023, 9:08am UTC](https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139/5 "2023-05-23T09:08:17Z")

</div>

Of course. But at some point before that, I have to use the graphical user interface in order to set up the scene I want to export as an image.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 23, 2023, 9:09am UTC](https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139/6 "2023-05-23T09:09:36Z")

</div>

Yes, use progressive pass interactively and edit your script before running in batch mode.

---

<div class="post-metadata">

### Author: ![flotus1](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/f/7ea924/32.png) [@flotus1](https://discourse.paraview.org/u/flotus1)
#### Post date: [May 23, 2023, 9:12am UTC](https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139/7 "2023-05-23T09:12:15Z")

</div>

Yep, that’s just one more step along the way. I was not sure if this was really necessary.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [May 23, 2023, 9:13am UTC](https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139/8 "2023-05-23T09:13:32Z")

</div>

Looks like it is. You can open an issue in ParaView to improve the rendering in that case:

[https://gitlab.kitware.com/paraview/paraview/-/issues](https://gitlab.kitware.com/paraview/paraview/-/issues)

---

<div class="post-metadata">

### Author: ![aerogt3](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/a/3bc359/32.png) [@aerogt3](https://discourse.paraview.org/u/aerogt3)
#### Post date: [March 12, 2024, 9:37am UTC](https://discourse.paraview.org/t/raytracing-in-batch-mode-progressive-passes-are-ignored/12139/9 "2024-03-12T09:37:43Z")

</div>

What makes this confusing, is that pvbatch seems to respect the ProgressivePasses when using SaveAnimation, but NOT when using SaveScreenshot.

Is there a reason for that?
