ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-01-03T13:04:52-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/14118VisItBridge compilation error2019-01-03T13:04:52-05:00Kitware RobotVisItBridge compilation error**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14118). Further discussion may take place here.**
---
I have enabled PARAVIEW_USE_VISITBRIDGE using ParaView commit 3f4918784cb8...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14118). Further discussion may take place here.**
---
I have enabled PARAVIEW_USE_VISITBRIDGE using ParaView commit 3f4918784cb8aa2662d27ccdcad9b49eff2e8490 on Mac OS X. Compilation fails with
[ 94%] Building CXX object Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/vtkVisItVsReader.cxx.o
/Users/quammen/dev/build/MADAIWorkbench-Installer/bin/ParaView-build/Utilities/VisItBridge/databases/vtkVisItVsReader.cxx: In member function ‘virtual bool vtkVisItVsReader::InitializeAVTReader(const int&)’:
/Users/quammen/dev/build/MADAIWorkbench-Installer/bin/ParaView-build/Utilities/VisItBridge/databases/vtkVisItVsReader.cxx:102: error: cannot allocate an object of abstract type ‘avtVsFileFormat’
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/databases/Vs/avtVsFileFormat.h:41: note: because the following virtual functions are pure within ‘avtVsFileFormat’:
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtFileFormat.h:150: note: virtual const char* avtFileFormat::GetType()
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtSTMDFileFormat.h:129: note: virtual vtkDataSet* avtSTMDFileFormat::GetMesh(int, const char*)
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtSTMDFileFormat.h:130: note: virtual vtkDataArray* avtSTMDFileFormat::GetVar(int, const char*)
/Users/quammen/dev/build/MADAIWorkbench-Installer/src/ParaView/Utilities/VisItBridge/Library/VisItLib/avt/Database/Formats/avtSTMDFileFormat.h:140: note: virtual void avtSTMDFileFormat::PopulateDatabaseMetaData(avtDatabaseMetaData*)
make[3]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/vtkVisItVsReader.cxx.o] Error 1
make[2]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/all] Error 2
make[1]: *** [Utilities/VisItBridge/databases/CMakeFiles/vtkIOVisItBridge.dir/rule] Error 2
make: *** [vtkIOVisItBridge] Error 2
https://gitlab.kitware.com/paraview/paraview/-/issues/14117nektar plugin doesn't build on mac2018-08-08T22:26:31-04:00Kitware Robotnektar plugin doesn't build on mac**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14117). Further discussion may take place here.**
---
There's a "#define max" that is interfering with std::max. **This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14117). Further discussion may take place here.**
---
There's a "#define max" that is interfering with std::max. https://gitlab.kitware.com/paraview/paraview/-/issues/14116paraview won't read ensight gold case files properly.2021-04-22T21:50:38-04:00Kitware Robotparaview won't read ensight gold case files properly.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14116). Further discussion may take place here.**
---
The ensight readers will read a case file that looks like
...
TIME
time s...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14116). Further discussion may take place here.**
---
The ensight readers will read a case file that looks like
...
TIME
time set: 1
number of steps: 5
filename numbers: 10005 10010 10015 10020 10025
time values: 0.0 0.1 0.2 0.3 0.4
but not in the new gold format:
TIME
time set: 1
number of steps: 187
filename numbers file: cyl_desFlow.numbers
time values file: cyl_desFlow.time
Where the two files have the iteration numbers and time numbers.https://gitlab.kitware.com/paraview/paraview/-/issues/14115Text not being shown correctly in pvbatch with split views2018-08-08T22:26:31-04:00Kitware RobotText not being shown correctly in pvbatch with split views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14115). Further discussion may take place here.**
---
Run the attached script in pvbatch. It renders 2 views, one after another ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14115). Further discussion may take place here.**
---
Run the attached script in pvbatch. It renders 2 views, one after another (you have to type a key and press enter to look at the results). Each view has just 1 text label, however the text label from the first view leaks into the second!!https://gitlab.kitware.com/paraview/paraview/-/issues/14113fix server side only reader plugins so that file extension hints are supported2020-05-06T05:07:40-04:00Kitware Robotfix server side only reader plugins so that file extension hints are supported**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14113). Further discussion may take place here.**
---
For a server side only reader plugin (i.e. no GUI_RESOURCE_FILES set) the ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14113). Further discussion may take place here.**
---
For a server side only reader plugin (i.e. no GUI_RESOURCE_FILES set) the user should only have to load the plugin on the server (currently there's a warning triangle if this happens).
If I load the plugin on both the client and the server then when I try to read the file in it doesn't recognize the file extension. The attached file (nektarfiles.tgz) can be used to demonstrate the problem for the nektar reader plugin.https://gitlab.kitware.com/paraview/paraview/-/issues/14112Surface Selection in parallel segfaulting when there are more than 0xffffff I...2018-08-08T22:26:31-04:00Kitware RobotSurface Selection in parallel segfaulting when there are more than 0xffffff IDs to render**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14112). Further discussion may take place here.**
---
Load a large dataset with more than 0xffffff cells (or points) per node in...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14112). Further discussion may take place here.**
---
Load a large dataset with more than 0xffffff cells (or points) per node in parallel. Now, when remote-rendering enabled, select surface cells (or points) in client-server mode. Note that remote-rendering needs to be enabled even before the first render. This will segfault.
https://gitlab.kitware.com/paraview/paraview/-/issues/14111VisIt MFiX Reader needs updating2018-08-08T22:26:31-04:00Kitware RobotVisIt MFiX Reader needs updating**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14111). Further discussion may take place here.**
---
The VisItBridge MFiX Reader needs to be updated to the newest version and ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14111). Further discussion may take place here.**
---
The VisItBridge MFiX Reader needs to be updated to the newest version and enabled by default.https://gitlab.kitware.com/paraview/paraview/-/issues/14110allow for floats as Duration in Real Time mode2023-05-16T16:21:03-04:00Kitware Robotallow for floats as Duration in Real Time mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14110). Further discussion may take place here.**
---
Right now, when visualizing a time-dependent data set, one can set the dur...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14110). Further discussion may take place here.**
---
Right now, when visualizing a time-dependent data set, one can set the duration of the animation to a fixed integer. Restricting this value to int appears unnecessary. Allowing for a float value here would allow for a more accurate presentation of results, also when exporting the data an animation (avi, ogv,...).https://gitlab.kitware.com/paraview/paraview/-/issues/14108make install doesn't work due to missing www directory in build directory2018-08-08T22:26:31-04:00Kitware Robotmake install doesn't work due to missing www directory in build directory**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14108). Further discussion may take place here.**
---
In the main PV CMakeLists.txt source file there is a custom command to cre...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14108). Further discussion may take place here.**
---
In the main PV CMakeLists.txt source file there is a custom command to create the ${PARAVIEW_WWW_DIR} directory (i.e. by default the www subdirectory in the build tree) but there is nothing that depends on the www.stamp output of the custom command so this directory never gets created. This is a problem when trying to install as it tries to install this missing directory. I think the CMakeLists.txt should be changed to something like:
if(BUILD_DOCUMENTATION)
add_custom_target(ParaViewDoc ALL
DEPENDS ${CMAKE_CURRENT_BINARY_DIR}/www.stamp)
add_custom_command(
OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/www.stamp
COMMAND ${CMAKE_COMMAND} -E make_directory "${PARAVIEW_WWW_DIR}")
install(DIRECTORY "${PARAVIEW_WWW_DIR}"
DESTINATION ${VTK_INSTALL_LIBRARY_DIR}
COMPONENT Runtime)
endif()
https://gitlab.kitware.com/paraview/paraview/-/issues/14107crash when picking with 'p' for stream tracer : Tag mismatch: got 1, expectin...2017-04-20T16:16:41-04:00Kitware Robotcrash when picking with 'p' for stream tracer : Tag mismatch: got 1, expecting 22222**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14107). Further discussion may take place here.**
---
With git master (first noticed a few days ago, rebased this am) I'm hittin...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14107). Further discussion may take place here.**
---
With git master (first noticed a few days ago, rebased this am) I'm hitting crash when attempting to use the stream tracer interactive picking a seed.
1) load the data,
2) change to surface rep,
3) add stream tracer filter
4) hit the 'p' key to select a seed -> crash.
I've only been able to reproduce with a real dataset (1024^3 image mesh). the small data I've tried from ParaViewData doesn't lead to the crash, However, there's plenty of ram (first encountered using 32 ranks 4 ranks per node 48g per node on longhorn reduced to 4 ranks 24g on my workstation for debugging). I can share this dataset if it helps to debug, or you may have to use a large dataset to trigger.
here's cerr output and a stack
3437 ERROR: In /scratch/01237/bloring/ParaView/next/ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 877
3438 vtkSocketCommunicator (0x2efd2d0): Tag mismatch: got 1, expecting 22222.
3439
3440 pvserver: /scratch/01237/bloring/ParaView/next/ParaView/VTK/Parallel/Core/vtkMultiProcessStream.cxx:637: vtkMultiProcessStream &vtkMultiProcessStream::operator>>(unsigned int &): Assertion `this->Internals->Data.front() == vtkInter nals::uint32_value' failed.
#0 0x00000033aea30215 in raise () from /lib64/libc.so.6
#1 0x00000033aea31cc0 in abort () from /lib64/libc.so.6
#2 0x00000033aea29696 in __assert_fail () from /lib64/libc.so.6
#3 0x00002b6ae159c3ed in vtkMultiProcessStream::operator>> (this=0x7fffea94ed68, value=@0x7fffea94ed1c)
at /scratch/01237/bloring/ParaView/next/ParaView/VTK/Parallel/Core/vtkMultiProcessStream.cxx:637
#4 0x00002b6aef371cdd in vtkPVSynchronizedRenderWindows::LoadWindowAndLayout (this=0x2835d50, window=0x26e9650, stream=@0x7fffea94ed68)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVSynchronizedRenderWindows.cxx:998
#5 0x00002b6aef37155b in vtkPVSynchronizedRenderWindows::RootStartRender (this=0x2835d50, renWin=0x26e9650)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVSynchronizedRenderWindows.cxx:901
#6 0x00002b6aef3711aa in vtkPVSynchronizedRenderWindows::HandleStartRender (this=0x2835d50, renWin=0x26e9650)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVSynchronizedRenderWindows.cxx:814
#7 0x00002b6aef36dc5a in vtkPVSynchronizedRenderWindows::vtkObserver::Execute (this=0x282f660, ocaller=0x26e9650, eventId=3)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVSynchronizedRenderWindows.cxx:219
#8 0x00002b6ae374c9ff in vtkSubjectHelper::InvokeEvent (this=0x282e970, event=3, callData=0x0, self=0x26e9650) at /scratch/01237/bloring/ParaView/next/ParaView/VTK/Common/Core/vtkObject.cxx:620
#9 0x00002b6ae374d028 in vtkObject::InvokeEvent (this=0x26e9650, event=3, callData=0x0) at /scratch/01237/bloring/ParaView/next/ParaView/VTK/Common/Core/vtkObject.cxx:789
#10 0x00002b6adc9ee77a in vtkRenderWindow::Render (this=0x26e9650) at /scratch/01237/bloring/ParaView/next/ParaView/VTK/Rendering/Core/vtkRenderWindow.cxx:313
#11 0x00002b6af42443f7 in vtkXOpenGLRenderWindow::Render (this=0x26e9650) at /scratch/01237/bloring/ParaView/next/ParaView/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx:1826
#12 0x00002b6adc9183d6 in vtkHardwareSelector::CaptureBuffers (this=0x26e9460) at /scratch/01237/bloring/ParaView/next/ParaView/VTK/Rendering/Core/vtkHardwareSelector.cxx:288
#13 0x00002b6af05119ef in vtkPVHardwareSelector::PrepareSelect (this=0x26e9460) at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/VTKExtensions/Rendering/vtkPVHardwareSelector.cxx:62
#14 0x00002b6af0511a54 in vtkPVHardwareSelector::Select (this=0x26e9460, region=0x7fffea94f750)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/VTKExtensions/Rendering/vtkPVHardwareSelector.cxx:75
#15 0x00002b6aef353e31 in vtkPVRenderView::Select (this=0x2833ce0, fieldAssociation=1, region=0x7fffea94f750)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:597
#16 0x00002b6aef353a19 in vtkPVRenderView::SelectCells (this=0x2833ce0, region=0x7fffea94f750)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.cxx:556
#17 0x00002b6ada8b1064 in vtkPVRenderView::SelectCells (this=0x2833ce0, region0=218, region1=142, region2=218, region3=142)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerCore/Rendering/vtkPVRenderView.h:246
#18 0x00002b6ada8ab300 in vtkPVRenderViewCommand (arlu=0x227b4f0, ob=0x2833ce0, method=0x3dfbd19 "SelectCells", msg=@0x7fffea951538, resultStream=@0x227bdf0)
at /scratch/01237/bloring/ParaView/next/PV/Wrapping/ClientServer/vtkPVRenderViewClientServer.cxx:545
#19 0x00002b6ae04b896e in vtkClientServerInterpreter::ProcessCommandInvoke (this=0x227b4f0, css=@0x7fffea951b90, midx=0)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:379
#20 0x00002b6ae04b7d5b in vtkClientServerInterpreter::ProcessOneMessage (this=0x227b4f0, css=@0x7fffea951b90, message=0)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:214
#21 0x00002b6ae04b7c0e in vtkClientServerInterpreter::ProcessStream (this=0x227b4f0, css=@0x7fffea951b90)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerStream/vtkClientServerInterpreter.cxx:183
#22 0x00002b6adba173cd in vtkPVSessionCore::ExecuteStreamInternal (this=0x227b990, stream=@0x7fffea951b90, ignore_errors=false)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:665
#23 0x00002b6adba1711e in vtkPVSessionCore::ExecuteStream (this=0x227b990, location=21, stream=@0x7fffea951b90, ignore_errors=false)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx:635
---Type <return> to continue, or q <return> to quit---
#24 0x00002b6adba11dde in vtkPVSessionBase::ExecuteStream (this=0x1a6ae50, location=21, stream=@0x7fffea951b90, ignore_errors=false)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionBase.cxx:173
#25 0x00002b6adba284b4 in vtkPVSessionServer::OnClientServerMessageRMI (this=0x1a6ae50, message=0x3cd3d00, message_length=16)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionServer.cxx:510
#26 0x00002b6adba25d2e in (anonymous namespace)::RMICallback (localArg=0x1a6ae50, remoteArg=0x3cd3d00, remoteArgLength=16)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ServerImplementation/Core/vtkPVSessionServer.cxx:56
#27 0x00002b6ae158abcc in vtkMultiProcessController::ProcessRMI (this=0x2efd1a0, remoteProcessId=1, arg=0x3cd3d00, argLength=16, rmiTag=55625)
at /scratch/01237/bloring/ParaView/next/ParaView/VTK/Parallel/Core/vtkMultiProcessController.cxx:650
#28 0x00002b6ae158a48f in vtkMultiProcessController::ProcessRMIs (this=0x2efd1a0, reportErrors=0, dont_loop=1)
at /scratch/01237/bloring/ParaView/next/ParaView/VTK/Parallel/Core/vtkMultiProcessController.cxx:596
#29 0x00002b6adbec2d07 in vtkTCPNetworkAccessManager::ProcessEventsInternal (this=0x174f090, timeout_msecs=0, do_processing=true)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx:268
#30 0x00002b6adbec25d0 in vtkTCPNetworkAccessManager::ProcessEvents (this=0x174f090, timeout_msecs=0)
at /scratch/01237/bloring/ParaView/next/ParaView/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx:165
#31 0x00000000004035e0 in RealMain (argc=5, argv=0x7fffea953418, type=vtkProcessModule::PROCESS_SERVER) at /scratch/01237/bloring/ParaView/next/ParaView/CommandLineExecutables/pvserver_common.h:90
#32 0x000000000040305d in main (argc=5, argv=0x7fffea953418) at /scratch/01237/bloring/ParaView/next/ParaView/CommandLineExecutables/pvserver.cxx:21https://gitlab.kitware.com/paraview/paraview/-/issues/14106add ghost cells to netkar reader plugin2021-04-29T19:11:35-04:00Kitware Robotadd ghost cells to netkar reader plugin**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14106). Further discussion may take place here.**
---
We should add in ghost cells to the nektar reader plugin so that we don't ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14106). Further discussion may take place here.**
---
We should add in ghost cells to the nektar reader plugin so that we don't get rendering issues in parallel.https://gitlab.kitware.com/paraview/paraview/-/issues/14105nektar reader plugin has points that should be merged but aren't2021-04-29T19:13:19-04:00Kitware Robotnektar reader plugin has points that should be merged but aren't**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14105). Further discussion may take place here.**
---
The nektar reader plugin cell connectivity file format lists coordinates f...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14105). Further discussion may take place here.**
---
The nektar reader plugin cell connectivity file format lists coordinates for each cell. Later on this points need to be merged because they'll be added in multiple times. vtkCleanUnstructuredGrid takes care of most of them but some of the coincident points aren't merged because they don't have the exact same value. This needs to be changed because otherwise there will be issues like the one in the uploaded file.https://gitlab.kitware.com/paraview/paraview/-/issues/14102CGNS reader problems with vars in different solutions2018-08-08T22:26:31-04:00Kitware RobotCGNS reader problems with vars in different solutions**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14102). Further discussion may take place here.**
---
Bug with CGNS Reader: http://visitbugs.ornl.gov/issues/57**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14102). Further discussion may take place here.**
---
Bug with CGNS Reader: http://visitbugs.ornl.gov/issues/57https://gitlab.kitware.com/paraview/paraview/-/issues/14101coprocessing.py is bad2018-08-08T22:26:31-04:00Kitware Robotcoprocessing.py is bad**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14101). Further discussion may take place here.**
---
Some of the methods need to import the proper parts of paraview's python i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14101). Further discussion may take place here.**
---
Some of the methods need to import the proper parts of paraview's python interface to work as well as set the time for UpdatePipeline() to avoid warnings.https://gitlab.kitware.com/paraview/paraview/-/issues/14100update the nektar reader2018-08-08T22:26:31-04:00Kitware Robotupdate the nektar reader**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14100). Further discussion may take place here.**
---
Changes from Joe Insley for the Nektar reader plugin. It also needs to be ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14100). Further discussion may take place here.**
---
Changes from Joe Insley for the Nektar reader plugin. It also needs to be added to the superbuild.https://gitlab.kitware.com/paraview/paraview/-/issues/14099Spreadsheet view doesn't select cells correctly from composite datasets.2018-08-08T22:26:31-04:00Kitware RobotSpreadsheet view doesn't select cells correctly from composite datasets.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14099). Further discussion may take place here.**
---
+ open can.ex2, all variables apply
+ split view and create spreadsheet v...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14099). Further discussion may take place here.**
---
+ open can.ex2, all variables apply
+ split view and create spreadsheet view
+ change attribute type to "Cell Data" to view cells in the spreadsheet view.
+ click on cell - it gets selected and then deselected again!
Doesn't happen for non-composite datasets, works fine in that case!https://gitlab.kitware.com/paraview/paraview/-/issues/14098Plot over line shows non-existant 0 values2018-08-08T22:26:31-04:00Kitware RobotPlot over line shows non-existant 0 values**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14098). Further discussion may take place here.**
---
+ Open can.ex2, all variable, hit apply
+ Create plot-over-line, default ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14098). Further discussion may take place here.**
---
+ Open can.ex2, all variable, hit apply
+ Create plot-over-line, default properites, apply
You get the attached plot for GlobalNodeId. While, EQPS and other variable correctly show no-line for missing values, why does GlobalNodeId go to 0? Looks like a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/14097Plot selection over time broken2018-08-08T22:26:31-04:00Kitware RobotPlot selection over time broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14097). Further discussion may take place here.**
---
Git version: v4.0.0-RC2
* Open can.ex2 and load all variables - hit app...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14097). Further discussion may take place here.**
---
Git version: v4.0.0-RC2
* Open can.ex2 and load all variables - hit apply
* Select a cell on the "block" that crushes the can and then create "Plot Selection Over Time" filter - hit apply.
* The plot is incorrect. If you look at the results from PlotSelectionOverTime filter in spreadsheet view, you'll see the reason: EQPS is 0 for all times.https://gitlab.kitware.com/paraview/paraview/-/issues/14096non-printable characters sent or received with vtkErrorMacro2023-06-15T08:19:28-04:00Kitware Robotnon-printable characters sent or received with vtkErrorMacro**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14096). Further discussion may take place here.**
---
in client server mode when server errors are reported in the terminal a nu...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14096). Further discussion may take place here.**
---
in client server mode when server errors are reported in the terminal a number of non-printable chars are streamed out. This is usually an indication of reading uninitialized memory. To reproduce you need to generate a server side error, one way to do it is to trump up a "text.bov" file, the visit bridge will choke on it and report an error.
pasting below (hope the non-printable chars come along for the ride):
�t��
ERROR: In /scratch/01237/bloring/ParaView/next/ParaView/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 751
vtkPVCompositeDataPipeline (0x240ae70): Algorithm vtkVisItBOVReader(0x23f8e70) returned failure for request: vtkInformation (0x242ab30)
Debug: Off
Modified Time: 152125
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0https://gitlab.kitware.com/paraview/paraview/-/issues/14095vtkScalarBarActor::RebuildLayout() is getting called on each render2018-08-08T22:26:31-04:00Kitware RobotvtkScalarBarActor::RebuildLayout() is getting called on each render**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14095). Further discussion may take place here.**
---
Git Version: v4.0.0-RC2
vtkScalarBarActor::RebuildLayout() is getting c...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14095). Further discussion may take place here.**
---
Git Version: v4.0.0-RC2
vtkScalarBarActor::RebuildLayout() is getting called on every render in ParaView. Although it's generally fast, I was able to get ParaView in a state (with Mathplotlib enabled) where the vtkScalarBarActor::LayoutAnnotations() was taking a really long time. Unfortunately, I cannot seem to reproduce that state anymore. In any case, the fact that vtkScalarBarActor::RebuildLayout() is getting called on every render seems like a bug.