VTK issueshttps://gitlab.kitware.com/vtk/vtk/-/issues2021-02-03T03:57:48-05:00https://gitlab.kitware.com/vtk/vtk/-/issues/18106VTK does not build on Windows with variable `UNICODE`2021-02-03T03:57:48-05:00Michael MiglioreVTK does not build on Windows with variable `UNICODE`I tried to build VTK with Unicode version of Win32 APIs that are used in some places in Windows specialized classes.
There are a lot of build errors related to the use of 8-bytes strings instead of 16-bytes strings.
To reproduce, conf...I tried to build VTK with Unicode version of Win32 APIs that are used in some places in Windows specialized classes.
There are a lot of build errors related to the use of 8-bytes strings instead of 16-bytes strings.
To reproduce, configure VTK with `/DUNICODE` in `CMAKE_CXX_FLAGS`.
cc @mwestphalhttps://gitlab.kitware.com/vtk/vtk/-/issues/18102VTK_NO_PYTHON_THREADS and VTK_PYTHON_FULL_THREADSAFE should be exposed in cmake2023-07-03T05:16:06-04:00Mathieu Westphal (Kitware)VTK_NO_PYTHON_THREADS and VTK_PYTHON_FULL_THREADSAFE should be exposed in cmakeVTK_NO_PYTHON_THREADS and VTK_PYTHON_FULL_THREADSAFE are two variables that can be set manually but are not declared as CMake options, making them hidden.
They should be declared as cmake options.VTK_NO_PYTHON_THREADS and VTK_PYTHON_FULL_THREADSAFE are two variables that can be set manually but are not declared as CMake options, making them hidden.
They should be declared as cmake options.https://gitlab.kitware.com/vtk/vtk/-/issues/18101TestIOADIOS2VTX_VTU3D and TestIOADIOS2VTX_VTI3D fundamentally broken2021-02-01T09:05:48-05:00Cory Quammencory.quammen@kitware.comTestIOADIOS2VTX_VTU3D and TestIOADIOS2VTX_VTI3D fundamentally brokenThere are a few issues with these tests:
* The pipeline won't execute the `TesterVTU3D`/`TesterVTI3D` filters because they produce 0 outputs
* If an output is specified, the `int FillOutputPortInformation(int port, vtkInformation* info)...There are a few issues with these tests:
* The pipeline won't execute the `TesterVTU3D`/`TesterVTI3D` filters because they produce 0 outputs
* If an output is specified, the `int FillOutputPortInformation(int port, vtkInformation* info)` member function must be overridden.
* Even if the above two items are done, the `DoCheckData(vtkMultiBlockDataSet*)` functions fail because the dataset passed into those functions are not `vtkMultiBlockDataSets`.
/cc @caitlin.ross @chuck.atkins @williamfgchttps://gitlab.kitware.com/vtk/vtk/-/issues/18100CI build configuration tracking2024-03-25T06:51:51-04:00Ben BoeckelCI build configuration trackingAdd Linux builds for the following:
- [ ] asan (!7575; reverted)
- [ ] ubsan (!7575; reverted)
- [ ] tsan
- [x] clang-tidy (!7598)
- [x] osmesa (!7855)
- [ ] 32bit ids
- [ ] egl
- [ ] cuda (!7876)
- [x] Doxygen nightly...Add Linux builds for the following:
- [ ] asan (!7575; reverted)
- [ ] ubsan (!7575; reverted)
- [ ] tsan
- [x] clang-tidy (!7598)
- [x] osmesa (!7855)
- [ ] 32bit ids
- [ ] egl
- [ ] cuda (!7876)
- [x] Doxygen nightly upload job
- [ ] icc + mpi (removed here because of SHM issues: https://gitlab.kitware.com/vtk/vtk/-/merge_requests/9747)
- [ ] coverage
- [ ] cross compiled android
- [ ] Debug
- [ ] cppcheck: https://gitlab.kitware.com/vtk/vtk/-/issues/18142
Additional dependencies (see `.gitlab/ci/configure_fedora_common.cmake`; these will need added to ParaView as well):
- [x] adios (@chuck.atkins, @caitlin.ross) (!7855)
- [x] openturns (@mwestphal) (!7855)
- [x] openvr (@ken-martin) (!7855)
- [ ] ospray (@utkarsh.ayachit)
- [ ] optix(?) (@ken-martin)
- [ ] visrtx (@ken-martin)
- [ ] open cascade (@spiros.tsalikis )
macOS builds (other than "all features"):
- [ ] nopython/python3
- [ ] aarch64 universal compilation (with tests on aarch64 and x86_64 hardware)
Most dependencies need downloaded here.
Windows builds (other than "all features"):
- [ ] nopython/python3
- [ ] mpi/nompi
- [ ] kits/nokits
- [ ] cuda
Most dependencies need downloaded here too.
Linux builds (other than "all features"):
- [ ] `VTK_PYTHON_FULL_THREADSAFE`
Python wheels (`master` only; MRs can unmask to test specifically):
- [x] manylinux2014/3.6 (!7898)
- [x] manylinux2014/3.7 (!7898)
- [x] manylinux2014/3.8 (!7898)
- [x] manylinux2014/3.9 (!7898)
- [x] macos/3.6 (!7898)
- [x] macos/3.7 (!7898)
- [x] macos/3.8 (!7898)
- [x] macos/3.9 (!7898)
- [x] win64/3.6 (!7898)
- [x] win64/3.7 (!7898)
- [x] win64/3.8 (!7898)
- [x] win64/3.9 (!7898)https://gitlab.kitware.com/vtk/vtk/-/issues/18098VTK Linux CI exclusions2022-07-08T04:36:07-04:00Ben BoeckelVTK Linux CI exclusionsThere are currently a host of tests being excluded on the "main" Linux build job due to some rendering quirks. It is unknown what the cause(s) of these problems are, but this issue is to track information about it. See `.gitlab/ci/ctest_...There are currently a host of tests being excluded on the "main" Linux build job due to some rendering quirks. It is unknown what the cause(s) of these problems are, but this issue is to track information about it. See `.gitlab/ci/ctest_test.cmake` (!7486) for the exclusion list.
Cc: @ken-martin @utkarsh.ayachit @sankheshhttps://gitlab.kitware.com/vtk/vtk/-/issues/18095Sometime isnan is a macro2021-02-16T14:01:20-05:00Alain MiniussiSometime isnan is a macroWhen building 4.9.0 with Intel 2020 update2 on top of Gcc 8.3 (library support) on CentOS7, I get the following error:
```
[337/20298] Generating the wrap hierarchy for VTK::CommonCore
FAILED: lib64/vtk/hierarchy/ParaView/vtkCommonCore-h...When building 4.9.0 with Intel 2020 update2 on top of Gcc 8.3 (library support) on CentOS7, I get the following error:
```
[337/20298] Generating the wrap hierarchy for VTK::CommonCore
FAILED: lib64/vtk/hierarchy/ParaView/vtkCommonCore-hierarchy.txt
cd /beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/VTK/Common/Core && /beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/bin/vtkWrapHierarchy-pv5.9 @/beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/VTK/Common/Core/CMakeFiles/vtkCommonCore-hierarchy.Release.args -o /beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/lib64/vtk/hierarchy/ParaView/vtkCommonCore-hierarchy.txt /beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/VTK/Common/Core/CMakeFiles/vtkCommonCore-hierarchy.data @/beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/paraview_build/VTK/Common/Core/CMakeFiles/vtkCommonCore-hierarchy.depends.args
vtkWrapHierarchy-pv5.9: In /beegfs/home/alainm/view/ocamodules/install/paraview/5.9.0/ParaView-v5.9.0/VTK/Common/Core/vtkGenericDataArrayLookupHelper.h:39: syntax error.
[378/20298] Building C object VTK/ThirdParty/glew/vtkglew/CMakeFiles/glew.dir/src/glew.c.o
ninja: build stopped: subcommand failed.
```
The error disappear if I insert:
```
#ifdef isnan
#undef isnan
#endif
```
before line 39
Thankshttps://gitlab.kitware.com/vtk/vtk/-/issues/18093vtkLight::ShallowClone() doesn't copy ShadowAttenuation2021-01-26T23:37:18-05:00Andras DeakvtkLight::ShallowClone() doesn't copy ShadowAttenuationI noticed this in the Python package:
```py
>>> import vtk
... light = vtk.vtkLight()
... light.SetShadowAttenuation(0.5)
... light.ShallowClone().GetShadowAttenuation() # expected: 0.5
1.0
```
And sure enough I don't seem to find `Sha...I noticed this in the Python package:
```py
>>> import vtk
... light = vtk.vtkLight()
... light.SetShadowAttenuation(0.5)
... light.ShallowClone().GetShadowAttenuation() # expected: 0.5
1.0
```
And sure enough I don't seem to find `ShadowAttenuation` being set at https://gitlab.kitware.com/vtk/vtk/-/blob/master/Rendering/Core/vtkLight.cxx#L91-115.
I would expect `ShallowClone()` to copy the `ShadowAttenuation` as well.https://gitlab.kitware.com/vtk/vtk/-/issues/18092vtkFlyingEdges3D not producing valid result while vtkContourFilter does on ve...2021-01-30T11:14:54-05:00Sebastien JourdainvtkFlyingEdges3D not producing valid result while vtkContourFilter does on very thin slabContouring the attached file for a scalar=1 don't produce the same result.
The vtkFlyingEdges3D seems to be connecting all the points to a virtual point in the origin of the image data.
Such connectivity is wrong and does not appear whe...Contouring the attached file for a scalar=1 don't produce the same result.
The vtkFlyingEdges3D seems to be connecting all the points to a virtual point in the origin of the image data.
Such connectivity is wrong and does not appear when the filtering is done with vtkContourFilter.
[thin-slab.vti](/uploads/f09e47f08d3cb69fc3c453620a837dea/thin-slab.vti)
![Screen_Shot_2021-01-26_at_15.14.58](/uploads/b0bb1d2e10bb51ae2496082326bd3875/Screen_Shot_2021-01-26_at_15.14.58.png)
![Screen_Shot_2021-01-26_at_15.15.05](/uploads/fb74f74766e676209231d70707c49a29/Screen_Shot_2021-01-26_at_15.15.05.png)Will SchroederWill Schroederhttps://gitlab.kitware.com/vtk/vtk/-/issues/18090Handling a corner case in diy based ghost cells generator2021-01-22T17:58:22-05:00Yohann Bearzi (Kitware)Handling a corner case in diy based ghost cells generatorThis follows !7548. Currently, ghosts are computed with only one rank communication pass: ranks adjacent to each other exchange ghosts. This works well if your input is not "sliced". Let's say you want to generate ghost cells between 3D ...This follows !7548. Currently, ghosts are computed with only one rank communication pass: ranks adjacent to each other exchange ghosts. This works well if your input is not "sliced". Let's say you want to generate ghost cells between 3D `vtkImageData` such that they are all stacked to each other in one dimension with image datas of thickness 1 voxel in this stacking dimension. The ghost cell generator will fail to exchange more than 1 layer of ghosts.
In order to be able to exchange more layer of ghosts, iterative communication between ranks needs to be added. Let's take an example. Block `A` communicates with block `B`. `B` is very thin and can send one layer of ghosts. However we want to generate 3 of them. `A` and `B` exchange their respective geometry, `A` notices that `B` didn't provide enough for 3 layers. In the meanwhile, `B` might have gather information from another block `C` which provides one additional layer of ghosts to `B`. In an additional communication between `A` and `B`, `A` can be aware of this additional geometry. If `A` doesn't have all its layers still (one is missing, in our example), the process can be looped over until no additional new geometry can be shared between blocks lacking ghost layers, or until every block has the wanted amount of ghost layers.
A similar mechanism will need to be done when exchanging ghost data (point data, cell data for instance). Ideally, this convoluted process should be done generically so new data types can be added without too much extra work.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/vtk/vtk/-/issues/18088Leak in jsoncpp2021-01-22T11:55:03-05:00Thomas CaissardLeak in jsoncppThere is a leak in the `jsoncpp` library. Line `3400` of `jsoncpp/vtkjsoncpp/jsoncpp.cpp` allocates a `const char*` but never free it.
This should be patched (just launching paraview results in a 2.3mb leak).There is a leak in the `jsoncpp` library. Line `3400` of `jsoncpp/vtkjsoncpp/jsoncpp.cpp` allocates a `const char*` but never free it.
This should be patched (just launching paraview results in a 2.3mb leak).https://gitlab.kitware.com/vtk/vtk/-/issues/18087Installed python binding lacks .egg-info: pip fails to recognize it and mayav...2022-10-17T12:38:31-04:00yurivictInstalled python binding lacks .egg-info: pip fails to recognize it and mayavi fails to find itI installed ```vtk9-9.0.1``` on FreeBSD in basically the same way as Arch Linux does it: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=vtk9
The resulting installation works (through ```import vtk```), but Mayavi fails to find i...I installed ```vtk9-9.0.1``` on FreeBSD in basically the same way as Arch Linux does it: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=vtk9
The resulting installation works (through ```import vtk```), but Mayavi fails to find it: DistributionNotFound: The 'vtk' distribution was not found and is required by the application (see https://github.com/enthought/mayavi/issues/1005).
What is wrong, why doesn't vtk install ```.egg-info```?https://gitlab.kitware.com/vtk/vtk/-/issues/18086VTK9.0.1+pyqt5 on TX2 cannot initialize2021-01-23T00:30:52-05:00Daizheng-zVTK9.0.1+pyqt5 on TX2 cannot initializeI can run my code correctly on the pc(ubuntu18.04+i5+gtx1060), but it cannot be displayed when deployed on tx2. The error message is “ERR| vtkXOpenGLRenderWindow (0x198ce420): GLEW could not be initialized: Missing GL version”
vtk is in...I can run my code correctly on the pc(ubuntu18.04+i5+gtx1060), but it cannot be displayed when deployed on tx2. The error message is “ERR| vtkXOpenGLRenderWindow (0x198ce420): GLEW could not be initialized: Missing GL version”
vtk is installed by compilation (VTK_PYTHON_VERSION = 3, VTK_WRAP_PYTHON = ON)
the code is:
```
from PyQt5.QtWidgets import QApplication, QMainWindow
import sys
import vtk
from PyQt5 import QtCore, QtGui, QtWidgets
from vtk.qt.QVTKRenderWindowInteractor import QVTKRenderWindowInteractor
class myMainWindow(QtWidgets.QMainWindow):
def __init__(self, parent=None):
QtWidgets.QMainWindow.__init__(self, parent)
self.frame = QtWidgets.QFrame()
self.vl = QtWidgets.QVBoxLayout()
self.vtkWidget = QVTKRenderWindowInteractor(self.frame)
self.vl.addWidget(self.vtkWidget)
self.ren = vtk.vtkRenderer()
self.vtkWidget.GetRenderWindow().AddRenderer(self.ren)
self.iren = self.vtkWidget.GetRenderWindow().GetInteractor()
# Create source
source = vtk.vtkConeSource()
source.SetCenter(0, 0, 0)
source.SetRadius(0.1)
source1 = vtk.vtkSphereSource()
source1.SetCenter(0, 0, 0)
source1.SetRadius(0.3)
# Create a mapper
mapper = vtk.vtkPolyDataMapper()
mapper.SetInputConnection(source.GetOutputPort())
mapper1 = vtk.vtkPolyDataMapper()
mapper1.SetInputConnection(source1.GetOutputPort())
# Create an actor
actor = vtk.vtkActor()
actor.SetMapper(mapper)
actor1 = vtk.vtkActor()
actor1.SetMapper(mapper1)
self.ren.AddActor(actor)
self.ren.AddActor(actor1)
self.ren.ResetCamera()
self.frame.setLayout(self.vl)
self.setCentralWidget(self.frame)
self.show()
self.iren.Initialize()
if __name__ == "__main__":
app = QApplication(sys.argv)
window = myMainWindow()
sys.exit(app.exec_())
```
the full error message is :
```
$ python3 test.py
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00]vtkOpenGLRenderWindow.c:569 ERR| vtkXOpenGLRenderWindow (0x2588420): GLEW could not be initialized: Missing GL version
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:63 WARN| Error in cache state for GL_DEPTH_WRITEMASK
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:72 WARN| Error in cache state for GL_COLOR_WRITEMASK
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:79 WARN| Error in cache state for GL_BLEND
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:86 WARN| Error in cache state for GL_DEPTH_TEST
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:109 WARN| Error in cache state for GL_SCISSOR_TEST
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:132 WARN| Error in cache state for GL_VIEWPORT
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:140 WARN| Error in cache state for GL_SCISSOR_BOX
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:147 WARN| Error in cache state for GL_CULL_FACE_MODE
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:154 WARN| Error in cache state for GL_ACTIVE_TEXTURE
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:161 WARN| Error in cache state for GL_DEPTH_FUNC
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:168 WARN| Error in cache state for GL_BLEND_SRC_RGB
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:175 WARN| Error in cache state for GL_BLEND_SRC_ALPHA
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:182 WARN| Error in cache state for GL_BLEND_DST_RGB
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:189 WARN| Error in cache state for GL_BLEND_DST_ALPHA
2021-01-20 20:20:47.692 ( 0.988s) [ A4946E00] vtkOpenGLState.cxx:196 WARN| Error in cache state for GL_DRAW_FRAMEBUFFER_BINDING
2021-01-20 20:20:47.692 ( 0.989s) [ A4946E00] vtkOpenGLState.cxx:203 WARN| Error in cache state for GL_READ_FRAMEBUFFER_BINDING
2021-01-20 20:20:47.692 ( 0.989s) [ A4946E00] vtkOpenGLState.cxx:222 WARN| Error in cache state for GL_DRAW_BUFFER got -148227696 expected1026
2021-01-20 20:20:47.692 ( 0.989s) [ A4946E00] vtkOpenGLState.cxx:240 WARN| Error in cache state for GL_READ_BUFFER
2021-01-20 20:20:47.692 ( 0.989s) [ A4946E00] vtkOpenGLState.cxx:257 WARN| Error in cache state for GL_COLOR_CLEAR_VALUE
2021-01-20 20:20:47.695 ( 0.991s) [ A4946E00] vtkOpenGLState.cxx:265 WARN| at stack loc
0x7f9e4753e0 : ??? [(???) ???:-1]
0x7f9e46ff54 : vtksys::SystemInformation::GetProgramStack[abi:cxx11](int, int) [(libvtksys-9.0.so.1) ???:-1]
0x7f9759e178 : vtkOpenGLState::CheckState() [(libvtkRenderingOpenGL2-9.0.so.1) ???:-1]
0x7f975a1ebc : vtkOpenGLState::vtkglGetIntegerv(unsigned int, int*) [(libvtkRenderingOpenGL2-9.0.so.1) ???:-1]
0x7f97579ddc : vtkOpenGLRenderWindow::CreateOffScreenFramebuffer(int, int) [(libvtkRenderingOpenGL2-9.0.so.1) ???:-1]
0x7f9757750c : vtkOpenGLRenderWindow::Start() [(libvtkRenderingOpenGL2-9.0.so.1) ???:-1]
0x7f976581c0 : vtkXOpenGLRenderWindow::Start() [(libvtkRenderingOpenGL2-9.0.so.1) ???:-1]
0x7f9bcf1554 : vtkRenderWindow::Render() [(libvtkRenderingCore-9.0.so.1) ???:-1]
0x7f9757ab7c : vtkOpenGLRenderWindow::Render() [(libvtkRenderingOpenGL2-9.0.so.1) ???:-1]
0x7f9765ab28 : vtkXOpenGLRenderWindow::Render() [(libvtkRenderingOpenGL2-9.0.so.1) ???:-1]
0x7f9bcfacfc : vtkRenderWindowInteractor::Render() [(libvtkRenderingCore-9.0.so.1) ???:-1]
0x7f9bcfdbc8 : vtkRenderWindowInteractor::Initialize() [(libvtkRenderingCore-9.0.so.1) ???:-1]
0x7f9c035a70 : ??? [(???) ???:-1]
0x5bbd4c : _PyCFunction_FastCallDict [(python3) ???:-1]
0x52ba70 : ??? [(???) ???:-1]
0x5306c0 : _PyEval_EvalFrameDefault [(python3) ???:-1]
0x52b108 : ??? [(???) ???:-1]
0x52b42c : _PyFunction_FastCallDict [(python3) ???:-1]
0x607a20 : _PyObject_FastCallDict [(python3) ???:-1]
0x5f4d34 : ??? [(???) ???:-1]
0x608da8 : PyObject_Call [(python3) ???:-1]
0x597e30 : ??? [(???) ???:-1]
0x5a740c : ??? [(???) ???:-1]
0x607948 : _PyObject_FastCallDict [(python3) ???:-1]
0x52b850 : ??? [(???) ???:-1]
0x5306c0 : _PyEval_EvalFrameDefault [(python3) ???:-1]
0x52b108 : ??? [(???) ???:-1]
0x631598 : PyRun_FileExFlags [(python3) ???:-1]
0x636c2c : PyRun_SimpleFileExFlags [(python3) ???:-1]
0x621428 : Py_Main [(python3) ???:-1]
0x420d3c : main [(python3) ???:-1]
0x7fa46156e0 : __libc_start_main [(libc.so.6) ???:-1]
0x420e94 : ??? [(???) ???:-1]
Segmentation fault (core dumped)
```https://gitlab.kitware.com/vtk/vtk/-/issues/18084vtkOpenGLCellToVTKCellMap CellCellMap Invalid2021-01-18T08:31:07-05:00Stephen HogarthvtkOpenGLCellToVTKCellMap CellCellMap InvalidIn Rendering/OpenGL2/vtkOpenGLCellToVTKCellMap.cpp, if the MapBuildState is updated and the CellCellMap cleared, mappers will not hardware probe accurately. This may be as a result of some other part of the application calling `BuildPrim...In Rendering/OpenGL2/vtkOpenGLCellToVTKCellMap.cpp, if the MapBuildState is updated and the CellCellMap cleared, mappers will not hardware probe accurately. This may be as a result of some other part of the application calling `BuildPrimitiveOffsetsIfNeeded` before calling `Update`, without the source data being updated in between the two calls. Then the CellCellMap will not be built during the update call and remain empty despite `CellMapSizes` indicating it should have content.
I have seen this for some time as a very transient bug, but am now seeing it happen very routinely in my application. I assume that it is also the cause for the changes in !7137, as those changes would be some of the defensive programming needed to error handle this situation. It can be avoided if the if statement in `Update` on line 287 changes from `if (this->MapBuildState != this->TempState)` to `if (this->MapBuildState != this->TempState || this->CellCellMap.empty())`, though that doesn't seem to be the proper fix for this bug. Would you have a better idea for how this could be fixed?https://gitlab.kitware.com/vtk/vtk/-/issues/18079Some VTK Dependency not checked at configuration time2021-01-11T09:00:49-05:00Mathieu Westphal (Kitware)Some VTK Dependency not checked at configuration timeThe following package were needed by VTK but not checked at configuration time
* linux-headers for `linux/fs.h`
* libexecinfo-dev for `execinfo.h`
FYI @ben.boeckelThe following package were needed by VTK but not checked at configuration time
* linux-headers for `linux/fs.h`
* libexecinfo-dev for `execinfo.h`
FYI @ben.boeckelhttps://gitlab.kitware.com/vtk/vtk/-/issues/18073vtkAngleRepresentation3D does not compute angle if x-coords of points are the...2021-01-06T05:09:58-05:00Philipp WeissenbachervtkAngleRepresentation3D does not compute angle if x-coords of points are the sameToday I recognized a strange behaviour of the `vtkAngleWidget`. (version 9.0 commit 1762d09ccdddcba85586b67475a2abd89918f590)
When initializing the widget programmatically with three points (all laying on the YZ-plane) the widget does no...Today I recognized a strange behaviour of the `vtkAngleWidget`. (version 9.0 commit 1762d09ccdddcba85586b67475a2abd89918f590)
When initializing the widget programmatically with three points (all laying on the YZ-plane) the widget does not compute the angle.
The problematic section of code is in `vtkAngleRepresentation3D` line 293.
// Compute the angle (only if necessary since we don't want
// fluctuations in angle value as the camera moves, etc.)
if (p1[0] - c[0] == 0.0 || p2[0] - c[0] == 0.0)
{
return;
}
Here, the `BuildRepresentation()` method returns if the x-coordinates of the points are the same (why is it that way?). Is that a bug, or an intended behaviour?
In my use case (CT Viewer) I cannot measure 3D angle if the picked world coordinates originate from the sagittal plane (x-coordinates of all three points are the same). For an example image of the imcomplete angle measurement of the `vtkAngleWidget` see attached image file.
![IncompleteAngleMeasurement](/uploads/4c4dc135393b52971c46f205cde37470/IncompleteAngleMeasurement.png)https://gitlab.kitware.com/vtk/vtk/-/issues/18070vtkFLUENTReader - Cell Array Selection doesn't work2021-01-03T15:06:18-05:00Arthur P.vtkFLUENTReader - Cell Array Selection doesn't workWhen reading Fluent files (.cas) in Paraview, the Cell Array Selection menu (see picture) offers the possibility to add/remove the variables needed before reading the file (when "apply" is pressed).
If I check the variable that I need, P...When reading Fluent files (.cas) in Paraview, the Cell Array Selection menu (see picture) offers the possibility to add/remove the variables needed before reading the file (when "apply" is pressed).
If I check the variable that I need, Paraview will not open the desired variable but all the variables.
The Cell Array selection menu is useless.
The function "this->CellDataArraySelection->AddArray" in the "RequestInformation" function of "IO/Geometry/vtkFLUENTReader.cxx" seems to load the name for Paraview but this is not used afterwards.
![Capture_d_écran_2021-01-03_à_20.20.08](/uploads/8b709a6e6ee68d5ebe7a92457bcf3818/Capture_d_écran_2021-01-03_à_20.20.08.png)https://gitlab.kitware.com/vtk/vtk/-/issues/18069STLWriter error checking needs investigation2021-12-20T17:52:54-05:00Ben BoeckelSTLWriter error checking needs investigationThe `vtkSTLWriter` class tries to detect "out of space" errors, but does so poorly. It checks only `fflush` for an error (any error) and assumes it means `ENOSPC` (rather than checking for `EIO` or other plausible errors). The thing is t...The `vtkSTLWriter` class tries to detect "out of space" errors, but does so poorly. It checks only `fflush` for an error (any error) and assumes it means `ENOSPC` (rather than checking for `EIO` or other plausible errors). The thing is that `fwrite`/`fprintf` could *also* have triggered the `ENOSPC` leaving nothing in the buffer to flush and therefore no error.
I've disabled the testing of the "out of space" error for now because the code just isn't handling the detection well enough for our CI.https://gitlab.kitware.com/vtk/vtk/-/issues/18068SEG-Y 3D Reader is Broken2021-11-03T13:42:53-04:00Bane SullivanSEG-Y 3D Reader is BrokenThe SEG-Y (geophysical seismic format) reader is broken. To reproduce, run the [`TestSegY3DReader` test](https://gitlab.kitware.com/vtk/vtk/-/blob/master/IO/SegY/Testing/Cxx/TestSegY3DReader.cxx)
The output image resolution is so small ...The SEG-Y (geophysical seismic format) reader is broken. To reproduce, run the [`TestSegY3DReader` test](https://gitlab.kitware.com/vtk/vtk/-/blob/master/IO/SegY/Testing/Cxx/TestSegY3DReader.cxx)
The output image resolution is so small that the image comparison test does not detect the fact that it is producing a bad output.
| Expected ([the image on DKC](https://data.kitware.com/api/v1/file/hashsum/sha512/50ac5d767f0cd4c0a2ebf98d64a8cf990ba7aad98c68b6c9fbb6c641c3043c2c2baf2e9a5f20b247ce722054fb9cbff40181f98b794a29339f854786e686cca2/download)) | Actual Ouput |
|---|---|
|![TestSegY3DReader](/uploads/37424f426ebcaef2423f58b4e258d0fb/TestSegY3DReader.png) | ![segy](/uploads/11ad1e56da092af1b03b7e45fba765ee/segy.png) |
The testing data is available [here](https://data.kitware.com/api/v1/file/hashsum/sha512/63a2285ef9dc633ec3696bcdd9af43137d6c519a7a653d45faec549b3f81fbd8ef79120aed6f7b86b62ed0d50e727ea8599aca57d2e3ed8e15a90c4b91c5c1b5/download)
This also affects ParaView. Note that I think using the Force 2D option yields okay results
cc @danlipsahttps://gitlab.kitware.com/vtk/vtk/-/issues/18067Quadratic Quad Cell as Face2020-12-17T03:27:23-05:00MetinQuadratic Quad Cell as FaceThis is an issue related to vtkUnstructuredGridGeometryFilter.
The faces of a 3D quadratic cells are represented by 2D quadratic elements.
### Problem
The inserted/generated faces are not the best representations of a 3D quadratic cel...This is an issue related to vtkUnstructuredGridGeometryFilter.
The faces of a 3D quadratic cells are represented by 2D quadratic elements.
### Problem
The inserted/generated faces are not the best representations of a 3D quadratic cell. See the picture below.
Obviously, the face orientation is wrong but that's not all is it?
The test case is here:
[paraview_testcase_quad.tar](/uploads/4bd48fa47d041c8dd5a5bc43c4e40fae/paraview_testcase_quad.tar)
![testcase_quad](/uploads/2d8372f8ba6ca2420cf4e43cdaa0a756/testcase_quad.png)
### Face Issue
![image](/uploads/31ef255ecc100cd4a86ae71183aef8d4/image.png)
Maybe the cell type VTK_QUADRATIC_QUAD is not the best choice?https://gitlab.kitware.com/vtk/vtk/-/issues/18065const qualifier InsertNextLinkedPoint2020-12-17T12:27:48-05:00Ronaldconst qualifier InsertNextLinkedPointThe point in https://gitlab.kitware.com/vtk/vtk/-/blob/master/Common/DataModel/vtkPolyData.h#L472 should be `const`.The point in https://gitlab.kitware.com/vtk/vtk/-/blob/master/Common/DataModel/vtkPolyData.h#L472 should be `const`.