ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-08-08T22:25:46-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/14856"Edit color legend properties" unavailable2018-08-08T22:25:46-04:00Kitware Robot"Edit color legend properties" unavailable**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14856). Further discussion may take place here.**
---
1) Load a file in PARAVIS and do "Color by"...
2) Display the scalar bar ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14856). Further discussion may take place here.**
---
1) Load a file in PARAVIS and do "Color by"...
2) Display the scalar bar by clicking in the tool bar "Toggle color legend visibility".
3) Do "Edit color map"
=> In the result a "Color Map Editor" dockable windows is displayed, but there are two problems:
P1: "Edit color legend properties" button is unavailable
P2 "Show/hide color legend" button is not pushed, but the color legend is visible
See ColorMapDlg.jpeg imagehttps://gitlab.kitware.com/paraview/paraview/-/issues/14854Bug with the shifted selection of the nodes2020-05-06T05:05:17-04:00Kitware RobotBug with the shifted selection of the nodes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14854). Further discussion may take place here.**
---
When selecting points on a mesh, the displayed selection does not
corresp...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14854). Further discussion may take place here.**
---
When selecting points on a mesh, the displayed selection does not
correspond exactly to the position of the node of the mesh. The attached
image illustrates this situation where the pink points are shifted from
the nodes.https://gitlab.kitware.com/paraview/paraview/-/issues/14821Long compilation of ParaView with early versions of gcc 4.42018-08-08T22:25:48-04:00Kitware RobotLong compilation of ParaView with early versions of gcc 4.4**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14821). Further discussion may take place here.**
---
The compilation of ParaView takes very long time on some Linux distributio...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14821). Further discussion may take place here.**
---
The compilation of ParaView takes very long time on some Linux distributions.
The analysis has shown that this problem takes place with some versions of gcc compiler. For example, this problem is reproduced on:
- Mandriva 2010.0 64bits: gcc version 4.4.1.
- CentOS 5.5 64bits: gcc version 4.4.0.
The 'make' process freezes at compilation of ParaViewCore/ServerManager/SMApplication/vtkInitializationHelper.cxx file.
The compilation, if not stopped, might take more than a week!!! :)
In the end, the compilation of this file is successfully finished and rest of build procedure is done as usual.
During the compilation of this file, CPU shows ~100% of loading (on multi-core systems only one core is loaded).
The analysis has shown that the problem is caused by ParaView_build/ParaViewCore/ServerManager/SMApplication/vtkSMGeneratedModules.h file that is generated by kwProcessXML tool. Namely, this (very big) file operates with huge hard-coded string variables, e.g.
...
// From file /data/mnt/vsr/tmp/ParaView-4.1.0_SRC/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml
static const char* const vtkSMDefaultModulesfiltersInterface0 =
"<ServerManagerConfiguration>\n"
" <ProxyGroup name=\"internal_filters\">\n"
...
This problem can be fixed by patching of the Utilities/ProcessXML/ProcessXML.cxx file, in "void PrintHeader(const char* title, const char* file)" function, by replacing (in line 53)
<< "static const char* " << this->Prefix.c_str() << title << this->Suffix.c_str() << this->Count
with
<< "static const char* const " << this->Prefix.c_str() << title << this->Suffix.c_str() << this->Count
With this patch, the compilation of mentioned file takes just a second. No any negative side effect has been found after applying of this patch.
https://gitlab.kitware.com/paraview/paraview/-/issues/14764Second attempt to load Paraview plug-in from python leads to a crash of the a...2018-08-08T22:25:51-04:00Kitware RobotSecond attempt to load Paraview plug-in from python leads to a crash of the application**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14764). Further discussion may take place here.**
---
- Start Paraview
- Menu "Tools" = > "Python Shell"
- Type LoadPlugin("li...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14764). Further discussion may take place here.**
---
- Start Paraview
- Menu "Tools" = > "Python Shell"
- Type LoadPlugin("libForceTime.so", ns=globals())
=> If Force Time plug-in was already loaded, then application crashes, otherwise after second call of the LoadPlugin("libForceTime.so", ns=globals())application crashes.
An attached patch clientServerInterp.patch solves a problem.
Could you please integrate it the next version of the Paraview?https://gitlab.kitware.com/paraview/paraview/-/issues/14763Use platform dependant separator for the PV_PLUGIN_PATH environment variable2018-08-08T22:25:51-04:00Kitware RobotUse platform dependant separator for the PV_PLUGIN_PATH environment variable**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14763). Further discussion may take place here.**
---
The problem is that by some reason Paraview 4.1 only supports semicolon ("...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14763). Further discussion may take place here.**
---
The problem is that by some reason Paraview 4.1 only supports semicolon (";") as a separator of the directories for the PV_PLUGIN_PATH variable, though this is natural that separator is platform-dependant (";" on Windows and ":" on Linux). On the other hand ";" is used as a separator of the CMake list items and we encountered with the following problem:
We have a CMake macro which accumulates an environment needed for the correct tests execution:
GENERATE_TESTS_ENVIRONMENT(tests_env)
ADD_TEST(TestName TestExecutable)
SET_TESTS_PROPERTIES(TestName PROPERTIES ENVIRONMENT "${tests_env}")
The variable tests_env is CMake list which contains a environment variables needed for the test execution:
tests_env is "PATH=path1:path2:path3:...:pathn;LD_LIBRARY_PATH=ldpath1:ldpath2:ldpath3:...:ldpathn;PV_PLUGIN_PATH=pvpath1;pvpath2;pvpath3:...;pvpathn"
The problem is that then CMake parses this list it takes for the PV_PLUGIN_PATH only fist path pvpath1 so far as ";" is a separator for the list items in CMake. Thus some tests fail because Paraview plug-ins located in the pvpath2, pvpath3,...,pvpathn can’t be found.
Attached patch contains a small fix which allows use both ":" and ";" separators on Linux (to avoid possible regressions) and ";" separator on Windows for the PV_PLUGIN_PATH environment variable.
Could you please analyze a patch and if possible integrate it the next version of the Paraview?https://gitlab.kitware.com/paraview/paraview/-/issues/14738Crash in the vtkPVGeometryFilter on the simple case2018-08-08T22:25:53-04:00Kitware RobotCrash in the vtkPVGeometryFilter on the simple case**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14738). Further discussion may take place here.**
---
An attached file "carre.vtu" contains 4 quadrangles.
Applying of the vtkP...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14738). Further discussion may take place here.**
---
An attached file "carre.vtu" contains 4 quadrangles.
Applying of the vtkPVGeometryFilter to this data set leads to the crash of the application.
Run attached python script carre.py, in the result application crashes, in the console displayed the following log:
paraview version 4.1.0
ERROR: In /dn47/SALOME/PRODUCTS/7x/opt/CentOS.6.3.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 389
vtkPVSessionCore (0x2b35510): Object type: vtkPVGeometryFilter, could not find requested method: "SetMakeOutlineOfInput"
or the method was called with incorrect arguments.
while processing
Message 0 = Invoke
Argument 0 = vtk_object_pointer {vtkPVGeometryFilter (0x61711c0)}
Argument 1 = string_value {SetMakeOutlineOfInput}
Argument 2 = int32_value {0}
ERROR: In /dn47/SALOME/PRODUCTS/7x/opt/CentOS.6.3.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 390
vtkPVSessionCore (0x2b35510): Aborting execution for debugging purposes.
############ ABORT #############
ERROR: In /dn47/SALOME/PRODUCTS/7x/opt/CentOS.6.3.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 486
vtkSISourceProxy (0x6170ff0): Could not parse property: MakeOutlineOfInput
ERROR: In /dn47/SALOME/PRODUCTS/7x/opt/CentOS.6.3.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/ClientServerCore/Core/vtkPVAlgorithmPortsInformation.cxx, line 56
vtkPVAlgorithmPortsInformation (0x613c650): Could not downcast vtkAlgorithm.
ERROR: In /dn47/SALOME/PRODUCTS/7x/opt/CentOS.6.3.64/7.4.0/tmp/ParaView-4.1.0_SRC/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 267
vtkSISourceProxy (0x6170ff0): Incorrect message received. Missing xml_group and xml_name information.
global_id: 4840
location: 1
[paraview_protobuf.ProxyState.property] {
name: "Input"
value {
type: INPUT
proxy_global_id: 4829
port_number: 0
}
}
Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0.https://gitlab.kitware.com/paraview/paraview/-/issues/14733Bad computation of the min and max values of a field when the color gradient ...2018-08-08T22:25:53-04:00Kitware RobotBad computation of the min and max values of a field when the color gradient has been changed by the user**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14733). Further discussion may take place here.**
---
Click on Source > Cone. Apply.
Color by field "cellNormals" and component...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14733). Further discussion may take place here.**
---
Click on Source > Cone. Apply.
Color by field "cellNormals" and component "Z".
Display the Color Map.
Click on Edit Color map > Choose Preset > Blue to Red Rainbow. Close
Click on Save as Default. Close.
Click on Source > Sphere. Apply.
Create filter "Mesh Quality". Apply.
Display the Color Map.
The Color Map ranges from -0.918 to 0.918 and should go from 1.06 to 1.64.
Clicking on "Rescale to data range" does not solve the problem.https://gitlab.kitware.com/paraview/paraview/-/issues/14731After relaunching a python script, the last scalar bar stays displayed when h...2020-05-06T05:16:49-04:00Kitware RobotAfter relaunching a python script, the last scalar bar stays displayed when hiding the representation**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14731). Further discussion may take place here.**
---
Launch the script playing_with_scalar_bar_paraview.py (attached).
In the ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14731). Further discussion may take place here.**
---
Launch the script playing_with_scalar_bar_paraview.py (attached).
In the Pipeline Browser, click on the eye left of MeshQuality1.
=> The representation and the scalar bar are hidden.
Re-launch the script.
Click on the eye left of MeshQuality2.
=> The representation is hidden, but the scalar is still displayed.https://gitlab.kitware.com/paraview/paraview/-/issues/14730vtkPVGeometryFilter produces a strange dataset from the bi-quadratic quadrangles2018-08-08T22:25:53-04:00Kitware RobotvtkPVGeometryFilter produces a strange dataset from the bi-quadratic quadrangles**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14730). Further discussion may take place here.**
---
Run the geom_filter.py script in the paraview python console from the atta...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14730). Further discussion may take place here.**
---
Run the geom_filter.py script in the paraview python console from the attached archive PVGeometryFilter.zip.
An InputData.vtk file contains a dataset with the bi-quadratic quadrangles. In the result applying 'vtkPVGeometryFilter' filter to this dataset it produces a strange dataset.
Please see attached pictures:
1) input_data.png - input data for the 'vtkPVGeometryFilter' filter.
2) output_data.png - output data of the 'vtkPVGeometryFilter' filter.https://gitlab.kitware.com/paraview/paraview/-/issues/14729It is impossible use Unicode symbols in the "Text" source2018-06-26T06:15:29-04:00Kitware RobotIt is impossible use Unicode symbols in the "Text" source**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14729). Further discussion may take place here.**
---
It is impossible use Unicode symbols in the "Text" source from the python ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14729). Further discussion may take place here.**
---
It is impossible use Unicode symbols in the "Text" source from the python or directly from the GUI:
Example 1:
Text1 = Text()
Text1.Text = 'Diff\xe9rence'
RenderView1 = GetRenderView()
DataRepresentation1 = Show()
Render()
Example 2:
Menu Source -> Text,
Insert the "Différence" string in the 'Text' area
Click on Apply
In the result appears "Output Message" window with the following log:
Generic Warning: In /misc/dn20/salome/rnv/PRODUCTS_BUILD/ParaView-4.1.0_SRC/VTK/Common/Core/vtkUnicodeString.cxx, line 183
vtkUnicodeString::from_utf8(): not a valid UTF-8 string.
Generic Warning: In /misc/dn20/salome/rnv/PRODUCTS_BUILD/ParaView-4.1.0_SRC/VTK/Common/Core/vtkUnicodeString.cxx, line 183
vtkUnicodeString::from_utf8(): not a valid UTF-8 string.
Generic Warning: In /misc/dn20/salome/rnv/PRODUCTS_BUILD/ParaView-4.1.0_SRC/VTK/Common/Core/vtkUnicodeString.cxx, line 183
vtkUnicodeString::from_utf8(): not a valid UTF-8 string.
Generic Warning: In /misc/dn20/salome/rnv/PRODUCTS_BUILD/ParaView-4.1.0_SRC/VTK/Common/Core/vtkUnicodeString.cxx, line 183
vtkUnicodeString::from_utf8(): not a valid UTF-8 string.
ERROR: In /misc/dn20/salome/rnv/PRODUCTS_BUILD/ParaView-4.1.0_SRC/VTK/Rendering/FreeType/vtkTextActor.cxx, line 803
vtkTextActor (0x36e3d80): Cannot compute bounding box.
Generic Warning: In /misc/dn20/salome/rnv/PRODUCTS_BUILD/ParaView-4.1.0_SRC/VTK/Common/Core/vtkUnicodeString.cxx, line 183
vtkUnicodeString::from_utf8(): not a valid UTF-8 string.https://gitlab.kitware.com/paraview/paraview/-/issues/14363Building with MPI-enabled external HDF5 causes build issues2018-08-08T22:26:16-04:00Kitware RobotBuilding with MPI-enabled external HDF5 causes build issues**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14363). Further discussion may take place here.**
---
Building with MPI-enabled external HDF5 causes build issues. The solution ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14363). Further discussion may take place here.**
---
Building with MPI-enabled external HDF5 causes build issues. The solution is to fix the HDF5 include dirs and libs to include the MPI ones too. This should be handled automatically.https://gitlab.kitware.com/paraview/paraview/-/issues/14322client/server communication makes kernel's TCP buffer overflow2018-08-08T22:26:18-04:00Kitware Robotclient/server communication makes kernel's TCP buffer overflow**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14322). Further discussion may take place here.**
---
Steps to reproduce:
1. Launch pvserver in mutli-client mode
2. Launch pa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14322). Further discussion may take place here.**
---
Steps to reproduce:
1. Launch pvserver in mutli-client mode
2. Launch paraview client to connect to the above
paraview -url=cs://localhost:11111
3. Launch the attached script (shrink-sphere.py), either with "pvpython" (in which case the Ctrl-C is not caught
properly) or with python (and the correct PYTHONPATH) directly.
4. Inspecting the network status with:
netstat --inet -np
shows that the Python client script has its TCP buffer growing and growing (column "Recv-Q"). This ultimately crashes.
It seems that the client is not trying to read everything the server sends.
This is not a timing issue: increasing the "sleep" delay in the script to 1 sec shows the same behavior.
This is only with scripting: the configuration with only pvserver and paraview-client doesn't exhibit the behavior.
The behavior is seen with both the binary version (Linux 64 bits) and with a self-recompiled version (Linux 64 bits) of
ParaView 4.0.1.
-------- THE SCRIPT:
# Supposing the pvserver is already started on 'localhost'
from paraview import simple as spl
from time import sleep
# Connect to the pvserver
spl.Connect('localhost')
# Create a sphere and apply the Shrink filter to it:
ss = spl.Sphere(Radius=2, ThetaResolution=32)
shr = spl.Shrink(Input=ss)
spl.Show(shr)
spl.SetDisplayProperties(Representation = "Wireframe")
#shr.SetPropertyWithName("ShrinkFactor", 0.9)
# Loop on the shrink factor up and down for a while:
shr.ShrinkFactor = 0.5
step = 0.1
try:
while True:
if shr.ShrinkFactor >= 1.0:
step = -0.1
if shr.ShrinkFactor <= 0.0:
step = +0.1
shr.ShrinkFactor += step
sleep(0.1)
pass
except KeyboardInterrupt:
print "Ctrl-C received"
try:
while True:
pass
except KeyboardInterrupt:
print "Ctrl-C again! This time bye bye."
spl.Disconnect()
https://gitlab.kitware.com/paraview/paraview/-/issues/14308Invalid surface and "Surface With Edges" rendering of nonconvex VTK_POLYGON2018-08-08T22:26:18-04:00Kitware RobotInvalid surface and "Surface With Edges" rendering of nonconvex VTK_POLYGON**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14308). Further discussion may take place here.**
---
0- Open merge.vtu file in attachment
1- Activate Surface or Surface With ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14308). Further discussion may take place here.**
---
0- Open merge.vtu file in attachment
1- Activate Surface or Surface With Edges renderning
-> The rendering of nonconvex polygon cell #0 is invalid (see black part
between convex hull of cell # 0 and real cell in
SurfaceRenderOfNonConvexPolygon.png)
However on page 127 of 4th edition of VTK book in Cell Types section, it
is written that : "The polygon may be nonconvex,...".
Regards,
Alejandro.
https://gitlab.kitware.com/paraview/paraview/-/issues/14267behavior of views when displaying vector fields2018-08-08T22:26:22-04:00Kitware Robotbehavior of views when displaying vector fields**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14267). Further discussion may take place here.**
---
Hello,
Some of my users complain about a behavior of the views when dis...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14267). Further discussion may take place here.**
---
Hello,
Some of my users complain about a behavior of the views when displaying vector fields. I am trying to explain this behavior by a simple example :
1) Create a PacMan using the menu "Sources"
2) Open a second "3D View" and display also the PacMan inside
3) In the first view chose to visualize the field "Normals" and its component "X"
4) Go to the second view and display also "Normals" but choosing "Y" as a component
5) If you now click in the first view this view changes its selection to the "Y" component !
I would like to know if this is just a bug or the behavior is there to respect some visualization philosophy.
Cheers,
Alejandro.https://gitlab.kitware.com/paraview/paraview/-/issues/14188Bug on clipping vtkUnstructuredGrid containing Polyhedrons2018-08-08T22:26:27-04:00Kitware RobotBug on clipping vtkUnstructuredGrid containing Polyhedrons**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14188). Further discussion may take place here.**
---
In attached file a VTU file containing 36 cells (30 hexa8+6 polyhedrons)
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14188). Further discussion may take place here.**
---
In attached file a VTU file containing 36 cells (30 hexa8+6 polyhedrons)
with a scalar field on cells called "AFieldOnCells".
When clip filter is applied in PV4.0.1 (and 3.98) either a SIGSEGV
occurs or no cells appear (depending on the plane chosen for the clip).https://gitlab.kitware.com/paraview/paraview/-/issues/14187Information on data arrays not update when changing time steps2018-08-08T22:26:27-04:00Kitware RobotInformation on data arrays not update when changing time steps**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14187). Further discussion may take place here.**
---
Load a file with time steps for instance can1.ex or FileSeries/blow*
fro...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14187). Further discussion may take place here.**
---
Load a file with time steps for instance can1.ex or FileSeries/blow*
from ParaviewData. Apply.
In "Information" panel, we focus on data arrays values.
Click many times on icon "Next frame" in order to go next time steps.
=> Values are well updated for "DISPL".
Click many times on icon "Previous frame" in order to go previous time
steps.
=> Values are not updated.
Click again on "Next frame".
=> Values are not updated anymore.
https://gitlab.kitware.com/paraview/paraview/-/issues/14186Points sprites do not appear with a radius and opacity proportional to the a...2018-08-08T22:26:27-04:00Kitware RobotPoints sprites do not appear with a radius and opacity proportional to the already selected field**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14186). Further discussion may take place here.**
---
- Open contraintes_gauss_0_0.vtp.
- Apply.
- In Display, as representati...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14186). Further discussion may take place here.**
---
- Open contraintes_gauss_0_0.vtp.
- Apply.
- In Display, as representation type, chose "Point sprite".
- Display CHAM1D field instead of "Solid color", with the EFFX component
instead of Magnitude.
=> All spheres are displayed with the same radius.
- Click on "Edit Radius Transfer Function", put 0.01 as min and 0.1 as max.
=> nothing changes.
- In Display, Scale by, chose "CHAM1D_Vector".
=> spheres radius is proportional to the EFFX value.
- Put Scale by back to CHAM1D.
=> The sphere radius is now proportional to EFFX value.
- Click on "Edit Radius Transfer Function", put 0.05 as max.
=> The sphere radius is well updated.https://gitlab.kitware.com/paraview/paraview/-/issues/14185Wrong component shown in the legend2018-08-08T22:26:27-04:00Kitware RobotWrong component shown in the legend**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14185). Further discussion may take place here.**
---
- Open the file deplacements_0_0.vtu
- Apply
- Color by DEP1
- Click th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14185). Further discussion may take place here.**
---
- Open the file deplacements_0_0.vtu
- Apply
- Color by DEP1
- Click the icon 'Toggle Color Legend Visibility'
=> the name displayed is 'DEP1 DX' instead of 'DEP1 magnitude'https://gitlab.kitware.com/paraview/paraview/-/issues/14184CSV reader producing invalid Python trace2018-08-08T22:26:27-04:00Kitware RobotCSV reader producing invalid Python trace**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14184). Further discussion may take place here.**
---
Attachments:
------------
sinus.csv - a simple CSV file containing 4 lin...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14184). Further discussion may take place here.**
---
Attachments:
------------
sinus.csv - a simple CSV file containing 4 lines of two values (comma
separated)
trace_adr.py - ParaView generated Python trace
Description:
-------------
The Python trace generated by ParaView when importing the CSV file given
in attachment can not be re-executed.
Error trace:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File
"/export/home/adrien/my_salome/prereq/ParaView-4.0.1_INSTALL_Debug/lib/paraview-4.0/site-packages/paraview/simple.py",
line 300, in Show
raise RuntimeError, "Could not create a representation object for
proxy %s" % proxy.GetXMLLabel()
RuntimeError: Could not create a representation object for proxy CSV
Reader
Steps to reproduce
------------------
- open ParaView
- start Trace
- open the CVS file sinus.csv
- click Apply
- stop trace
- Run pvpython
- execute the lines of code given in the trace
https://gitlab.kitware.com/paraview/paraview/-/issues/13942"FitAll" function in python scripting2018-08-08T22:26:41-04:00Kitware Robot"FitAll" function in python scripting**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13942). Further discussion may take place here.**
---
Hello,
I have a request concerning the function that set the viewing po...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13942). Further discussion may take place here.**
---
Hello,
I have a request concerning the function that set the viewing position so that all visible datasets in the selected 3D view are within the viewing frustum. This function is the first icon in the Camera Control Toolbar. I would like to use this function when scripting in python. Can you expose this function via a "FitAll" method or something similar? I know there exists a ResetCamera function but it seems that does not correspond to what I want.
Exemple:
_RenderView = GetRenderView()
_RenderView.CenterAxesVisibility = 0
_RenderView.CenterOfRotation = [2.05, 2.05, 2.13]
_RenderView.CameraViewUp = [-0.1462842057166934, -0.63184311527201897, -0.76116700456679443] _RenderView.CameraPosition = [4.3574016706599696, 7.6016996854983274, -3.0256734058706636] _RenderView.CameraClippingRange = [2.9513133656308672, 13.226048282992661]
_RenderView.CameraFocalPoint = [2.9930930754568661, 1.7779227807543228, 2.0708298819357598]
The last 4 commands of this code are necessary to do the "FitAll" BUT they are dependent on the mesh and then not adapted to a pure scripting environment.
Thanks in advance,
Alejandro.