View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0012733ParaView(No Category)public2011-11-16 11:292016-08-12 09:59
ReporterStephane P 
Assigned ToPat Marion 
PriorityhighSeverityminorReproducibilityhave not tried
PlatformOSOS Version
Product Version3.10 
Target VersionFixed in Version 
Summary0012733: pvbatch rendering is different than interactive rendering
DescriptionThe user starts ParaView, starts tracing as soon as possible. He then does some post-processing, dumps an image and stops tracing.
when executing the created dump with pvbatch, the image created is different than then one created interactively.

attached is a simple test script.
TagsNo tags attached.
Topic Name
Typeincorrect functionality
Attached Fileszip file icon [^] (143,230 bytes) 2011-11-16 11:29
? file icon [^] (1,370 bytes) 2011-11-23 10:14
png file icon test.png [^] (16,360 bytes) 2011-11-29 02:52


Pat Marion (reporter)
2011-11-21 17:06

Hi Stephane,

I believe what you are observing is the expected behavior. Python trace captures actions (object creation and property modifications) as they happen. Since the 3D Render View exists before python trace is enabled, the generated python script does not contain any lines of code that assign the render view properties: view size, background color.

The result is that the script, when executed under pvbatch, writes the image using a render view with default properties. In pvbatch, the default properties of a render view are not the same as the defaults in the paraview GUI, which depend on the user settings.

You can generate an image in pvbatch that matches the GUI exactly if you do the following:

close all views in paraview gui
start trace
create a new 3d view
do your usual work
stop trace

Let me know if you have any questions. Also, let me know if there are changes we could make to the behavior of python trace so that it works better for you. For example, we could make it so that python trace always records the view's background color and size before rendering, even if those properties were not changed by the user while trace was enabled.
Stephane P (reporter)
2011-11-23 10:13

After some tests, the parameter view.ViewSize is missing from the trace when we start tracing when no 3D view is opened, even if the view is resized from the GUI.
And when we add this parameter in the script, it is not respected in the created image.

Attached is a script that should create a 100*100 image, but it creates a 100*115 image.
Pat Marion (reporter)
2011-11-28 21:34

You're right, ViewSize is not set by the trace generator, my mistake. I'll talk with some folks and come up with a solution for that.

I tried the script you attached using paraview 3.12 and 3.10.1, and I get an image with the correct dimensions, 100x100. Could you let me know your exact version of paraview and OS so that I can try reproducing the 100x115 bug?
Stephane P (reporter)
2011-11-29 02:53

I used winXP 32 bits, with the binary installation of pv 3.12 to reproduce it. Attached is the image I get (115*100, not 100*155)
Kitware Robot (administrator)
2016-08-12 09:59

Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.

 Issue History
Date Modified Username Field Change
2011-11-16 11:29 Stephane P New Issue
2011-11-16 11:29 Stephane P File Added:
2011-11-18 13:03 Utkarsh Ayachit Assigned To => Pat Marion
2011-11-21 17:06 Pat Marion Note Added: 0027727
2011-11-23 10:13 Stephane P Note Added: 0027730
2011-11-23 10:14 Stephane P File Added:
2011-11-28 21:34 Pat Marion Note Added: 0027740
2011-11-29 02:52 Stephane P File Added: test.png
2011-11-29 02:53 Stephane P Note Added: 0027741
2016-08-12 09:59 Kitware Robot Note Added: 0038100
2016-08-12 09:59 Kitware Robot Status backlog => closed
2016-08-12 09:59 Kitware Robot Resolution open => moved

Copyright © 2000 - 2018 MantisBT Team