VTK issueshttps://gitlab.kitware.com/vtk/vtk/-/issues2016-08-12T06:47:01-04:00https://gitlab.kitware.com/vtk/vtk/-/issues/5478Wrong derivatives computation in vtkQuadraticHexahedron2016-08-12T06:47:01-04:00Kitware RobotWrong derivatives computation in vtkQuadraticHexahedron**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5478). Further discussion may take place here.**
---
The derivatives are computed in [-1; 1] but need to be converted in [0; 1]
coor...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5478). Further discussion may take place here.**
---
The derivatives are computed in [-1; 1] but need to be converted in [0; 1]
coordinates.https://gitlab.kitware.com/vtk/vtk/-/issues/5480EvaluatePosition segfaults in vtkQuadraticLinearQuad2016-08-12T06:47:02-04:00Kitware RobotEvaluatePosition segfaults in vtkQuadraticLinearQuad**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5480). Further discussion may take place here.**
---
EvaluatePosition segfaults in vtkQuadraticLinearQuad
if closestPoint is NULL. ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5480). Further discussion may take place here.**
---
EvaluatePosition segfaults in vtkQuadraticLinearQuad
if closestPoint is NULL. This is fixed in the attached patch.https://gitlab.kitware.com/vtk/vtk/-/issues/5481Wrong derivatives computation in vtkQuadraticLinearWedge2016-08-12T06:47:02-04:00Kitware RobotWrong derivatives computation in vtkQuadraticLinearWedge**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5481). Further discussion may take place here.**
---
The derivatives are computed in [-1; 1] but need to be converted in [0; 1]
coor...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5481). Further discussion may take place here.**
---
The derivatives are computed in [-1; 1] but need to be converted in [0; 1]
coordinates.
The attached patch contains also the fixes of bug 3691.
https://gitlab.kitware.com/vtk/vtk/-/issues/5482Wrong derivatives computation in vtkQuadraticPyramid2016-08-12T06:47:02-04:00Kitware RobotWrong derivatives computation in vtkQuadraticPyramid**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5482). Further discussion may take place here.**
---
The derivatives are computed in [-1; 1] but need to be converted in [0; 1]
coor...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5482). Further discussion may take place here.**
---
The derivatives are computed in [-1; 1] but need to be converted in [0; 1]
coordinates.https://gitlab.kitware.com/vtk/vtk/-/issues/5483Wrong derivatives computation in vtkTriQuadraticHexahedron2016-08-12T06:47:03-04:00Kitware RobotWrong derivatives computation in vtkTriQuadraticHexahedron**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5483). Further discussion may take place here.**
---
The numbering of the derivatives is wrong.
The derivatives are computed in [-1;...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5483). Further discussion may take place here.**
---
The numbering of the derivatives is wrong.
The derivatives are computed in [-1; 1] but need to be converted in [0; 1]
coordinates.
The attached patch fixes this issue, update the
documentation to the correct numbering and fixes
some typos.
The attached patch contains also the fixes of bug 3691.https://gitlab.kitware.com/vtk/vtk/-/issues/5484Test cell consistency and evaluation for new quadratic cells2016-08-12T06:47:03-04:00Kitware RobotTest cell consistency and evaluation for new quadratic cells**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5484). Further discussion may take place here.**
---
Filtering/Testing/Cxx/quadraticEvaluation.cxx and
Filtering/Testing/Cxx/quadCel...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5484). Further discussion may take place here.**
---
Filtering/Testing/Cxx/quadraticEvaluation.cxx and
Filtering/Testing/Cxx/quadCellConsistency.cxx should test
the new quadratic cells.
A patch is attached.https://gitlab.kitware.com/vtk/vtk/-/issues/5485Implement cubic cells and improve the InterpolationDerives test2016-08-12T06:47:04-04:00Kitware RobotImplement cubic cells and improve the InterpolationDerives test**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5485). Further discussion may take place here.**
---
This is a major feature request for the implementation
of cubic cells in VTK. ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5485). Further discussion may take place here.**
---
This is a major feature request for the implementation
of cubic cells in VTK. The sources of the new cubic cells and a
patch to integrate them into VTK are attached.
Additionally TestInterpolationDerivs
has been improved to find incorrect derivatives computation
by using numerical differentiation.
If something is missing please let me know.https://gitlab.kitware.com/vtk/vtk/-/issues/5499Bug in vtkThinPlateSplineTransform::InternalUpdate()2016-08-12T06:47:08-04:00Kitware RobotBug in vtkThinPlateSplineTransform::InternalUpdate()**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5499). Further discussion may take place here.**
---
The following code leads to crash: division by zero!
int nSize = 2;
vtkPoint...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5499). Further discussion may take place here.**
---
The following code leads to crash: division by zero!
int nSize = 2;
vtkPoints* pScr = vtkPoints::New();
pScr->SetNumberOfPoints(nSize);
pScr->SetPoint(0, 0.0, 0.0, 0.0);
pScr->SetPoint(1, 5.0, 6.0, 0.0);
vtkPoints* pTrg = vtkPoints::New();
pTrg->SetNumberOfPoints(nSize);
pTrg->SetPoint(0, 0.0, 0.0, 0.0);
pTrg->SetPoint(1, 0.0, 0.0, 0.0);
vtkThinPlateSplineTransform* pT = vtkThinPlateSplineTransform::New();
pT->Modified();
pT->SetSourceLandmarks(pScr);
pT->SetTargetLandmarks(pTrg);
pT->Update();
pT->Delete();
https://gitlab.kitware.com/vtk/vtk/-/issues/5500vtkAbstractTransform and Co. - internal state2016-08-12T06:47:08-04:00Kitware RobotvtkAbstractTransform and Co. - internal state**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5500). Further discussion may take place here.**
---
This is a major feature request for the implementation of vtkAbstractTransform a...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5500). Further discussion may take place here.**
---
This is a major feature request for the implementation of vtkAbstractTransform and Co.. In some cases it is very helpful to know if the TemplateTransformPoint() or TemplateTransformInverse() was successful. Currently I see no possibility to get this information. So my proposal is to add some internal state flag in vtkAbstractTransform.
Example:
You are using vtkThinPlateSplineTransform with some very scattered points. Then you call TemplateTransformInverse() so the Newton method well be executed, but it fails to converge. At the moment you get an annoying warrning. It would be more usable to get the error state at the runtime, so you can react to this error inside you code.
Greets... https://gitlab.kitware.com/vtk/vtk/-/issues/5535add a few constants in vtkConstants.py2016-08-12T06:47:19-04:00Kitware Robotadd a few constants in vtkConstants.py**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5535). Further discussion may take place here.**
---
I have added a few useful constants about cells description in vtkConstants.py,
...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5535). Further discussion may take place here.**
---
I have added a few useful constants about cells description in vtkConstants.py,
copied from vtkCellType.h
BTW, the last cell types ("higher order") seem to do not exist for
python wrapping.https://gitlab.kitware.com/vtk/vtk/-/issues/5621Printing destroys the View in the VTK MFC examples.2016-08-12T06:47:47-04:00Kitware RobotPrinting destroys the View in the VTK MFC examples.**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5621). Further discussion may take place here.**
---
This applies to the examples VTKMDI.exe and VTKSDI.exe. If print previes os call...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5621). Further discussion may take place here.**
---
This applies to the examples VTKMDI.exe and VTKSDI.exe. If print previes os called it works Ok and displays the pages Ok. However upon closing print preview the view is not restored. In other words the displayed object is lost. I suspect it is some problem in either SetupMenoryRendering() or ResumeScreenRendering()https://gitlab.kitware.com/vtk/vtk/-/issues/5641I can not build vtk.sln on visual c++ 20052016-08-12T06:47:53-04:00Kitware RobotI can not build vtk.sln on visual c++ 2005**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5641). Further discussion may take place here.**
---
when i build vtk.sln, i get the next errors:
1>------ Build started: Project:...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5641). Further discussion may take place here.**
---
when i build vtk.sln, i get the next errors:
1>------ Build started: Project: vtkRendering, Configuration: Debug Win32 ------
1>Compiling...
1>vtkWin32OpenGLRenderWindow.cxx
1>..\..\vtk-5.0.3\Rendering\vtkWin32OpenGLRenderWindow.cxx(34) : fatal error C1083: Cannot open include file: 'GL/glaux.h': No such file or directory
1>Build log was saved at "file://c:\VTK_BINARY_DIR\Rendering\vtkRendering.dir\Debug\BuildLog.htm"
1>vtkRendering - 1 error(s), 0 warning(s)
2>------ Build started: Project: vtkHybrid, Configuration: Debug Win32 ------
3>------ Build started: Project: vtkVolumeRendering, Configuration: Debug Win32 ------
3>Linking...
2>Linking...
3>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
2>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
3>Build log was saved at "file://c:\VTK_BINARY_DIR\VolumeRendering\vtkVolumeRendering.dir\Debug\BuildLog.htm"
3>vtkVolumeRendering - 1 error(s), 0 warning(s)
2>Build log was saved at "file://c:\VTK_BINARY_DIR\Hybrid\vtkHybrid.dir\Debug\BuildLog.htm"
2>vtkHybrid - 1 error(s), 0 warning(s)
4>------ Build started: Project: GenericFilteringCxxTests, Configuration: Debug Win32 ------
5>------ Build started: Project: vtkWidgets, Configuration: Debug Win32 ------
4>Linking...
4>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
5>Linking...
5>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
4>Build log was saved at "file://c:\VTK_BINARY_DIR\GenericFiltering\Testing\Cxx\GenericFilteringCxxTests.dir\Debug\BuildLog.htm"
4>GenericFilteringCxxTests - 1 error(s), 0 warning(s)
5>Build log was saved at "file://c:\VTK_BINARY_DIR\Widgets\vtkWidgets.dir\Debug\BuildLog.htm"
5>vtkWidgets - 1 error(s), 0 warning(s)
6>------ Build started: Project: GraphicsCxxTests, Configuration: Debug Win32 ------
7>------ Build started: Project: VTKExamplesTarget, Configuration: Debug Win32 ------
7>Generating ../VTKExamples
6>Linking...
6>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
6>Build log was saved at "file://c:\VTK_BINARY_DIR\Graphics\Testing\Cxx\GraphicsCxxTests.dir\Debug\BuildLog.htm"
6>GraphicsCxxTests - 1 error(s), 0 warning(s)
8>------ Build started: Project: WidgetsCxxTests, Configuration: Debug Win32 ------
8>Linking...
8>LINK : fatal error LNK1104: cannot open file 'vtkWidgets.lib'
8>Build log was saved at "file://c:\VTK_BINARY_DIR\Widgets\Testing\Cxx\WidgetsCxxTests.dir\Debug\BuildLog.htm"
8>WidgetsCxxTests - 1 error(s), 0 warning(s)
9>------ Build started: Project: VTKBenchMark, Configuration: Debug Win32 ------
9>Linking...
9>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
9>Build log was saved at "file://c:\VTK_BINARY_DIR\Rendering\Testing\Cxx\VTKBenchMark.dir\Debug\BuildLog.htm"
9>VTKBenchMark - 1 error(s), 0 warning(s)
10>------ Build started: Project: VolumeRenderingCxxTests, Configuration: Debug Win32 ------
10>Linking...
10>LINK : fatal error LNK1104: cannot open file 'vtkVolumeRendering.lib'
10>Build log was saved at "file://c:\VTK_BINARY_DIR\VolumeRendering\Testing\Cxx\VolumeRenderingCxxTests.dir\Debug\BuildLog.htm"
10>VolumeRenderingCxxTests - 1 error(s), 0 warning(s)
11>------ Build started: Project: ImagingCxxTests, Configuration: Debug Win32 ------
11>Linking...
11>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
11>Build log was saved at "file://c:\VTK_BINARY_DIR\Imaging\Testing\Cxx\ImagingCxxTests.dir\Debug\BuildLog.htm"
11>ImagingCxxTests - 1 error(s), 0 warning(s)
12>------ Build started: Project: RenderingCxxTests, Configuration: Debug Win32 ------
12>Linking...
12>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
12>Build log was saved at "file://c:\VTK_BINARY_DIR\Rendering\Testing\Cxx\RenderingCxxTests.dir\Debug\BuildLog.htm"
12>RenderingCxxTests - 1 error(s), 0 warning(s)
7>Internal cmake changing into directory: C:/VTK_BINARY_DIR/Examples/All
7>======== CMake output ======
7>Warning: CMake is forcing CMAKE_BUILD_TYPE to "" to match that imported from VTK. This is required because projects must use the same compiler settings. If this message appears for more than one imported project, you have conflicting compiler settings and will have to re-build one of those projects.
7>Warning: CMake is forcing CMAKE_BUILD_TYPE to "" to match that imported from VTK. This is required because projects must use the same compiler settings. If this message appears for more than one imported project, you have conflicting compiler settings and will have to re-build one of those projects.
7>======== End CMake output ======
7>Microsoft (R) Visual C++ Express Edition Version 8.0.50727.867.
7>Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
7>1>------ Build started: Project: Cone5, Configuration: Debug Win32 ------
7>2>------ Build started: Project: Cone4, Configuration: Debug Win32 ------
7>2>Linking...
7>1>Linking...
7>2>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>2>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Tutorial\Step4\Cxx\Cone4.dir\Debug\BuildLog.htm"
7>2>Cone4 - 1 error(s), 0 warning(s)
7>1>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>1>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Tutorial\Step5\Cxx\Cone5.dir\Debug\BuildLog.htm"
7>1>Cone5 - 1 error(s), 0 warning(s)
7>3>------ Build started: Project: Cone3, Configuration: Debug Win32 ------
7>3>Linking...
7>3>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>3>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Tutorial\Step3\Cxx\Cone3.dir\Debug\BuildLog.htm"
7>3>Cone3 - 1 error(s), 0 warning(s)
7>4>------ Build started: Project: Cone2, Configuration: Debug Win32 ------
7>4>Linking...
7>4>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>4>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Tutorial\Step2\Cxx\Cone2.dir\Debug\BuildLog.htm"
7>4>Cone2 - 1 error(s), 0 warning(s)
7>5>------ Build started: Project: Cone, Configuration: Debug Win32 ------
7>5>Linking...
7>5>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>5>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Tutorial\Step1\Cxx\Cone.dir\Debug\BuildLog.htm"
7>5>Cone - 1 error(s), 0 warning(s)
7>6>------ Build started: Project: SpecularSpheres, Configuration: Debug Win32 ------
7>6>Linking...
7>6>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>6>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Rendering\Cxx\SpecularSpheres.dir\Debug\BuildLog.htm"
7>6>SpecularSpheres - 1 error(s), 0 warning(s)
7>7>------ Build started: Project: DiffuseSpheres, Configuration: Debug Win32 ------
7>7>Linking...
7>7>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>7>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Rendering\Cxx\DiffuseSpheres.dir\Debug\BuildLog.htm"
7>7>DiffuseSpheres - 1 error(s), 0 warning(s)
7>8>------ Build started: Project: Cylinder, Configuration: Debug Win32 ------
7>8>Linking...
7>8>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>8>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Rendering\Cxx\Cylinder.dir\Debug\BuildLog.htm"
7>8>Cylinder - 1 error(s), 0 warning(s)
7>9>------ Build started: Project: AmbientSpheres, Configuration: Debug Win32 ------
7>9>Linking...
7>10>------ Build started: Project: finance, Configuration: Debug Win32 ------
7>9>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>9>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Rendering\Cxx\AmbientSpheres.dir\Debug\BuildLog.htm"
7>9>AmbientSpheres - 1 error(s), 0 warning(s)
7>10>Linking...
7>10>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>10>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Modelling\Cxx\finance.dir\Debug\BuildLog.htm"
7>10>finance - 1 error(s), 0 warning(s)
7>11>------ Build started: Project: Medical3, Configuration: Debug Win32 ------
7>11>Linking...
7>11>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>11>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Medical\Cxx\Medical3.dir\Debug\BuildLog.htm"
7>11>Medical3 - 1 error(s), 0 warning(s)
7>12>------ Build started: Project: Medical2, Configuration: Debug Win32 ------
7>12>Linking...
7>12>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>12>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Medical\Cxx\Medical2.dir\Debug\BuildLog.htm"
7>12>Medical2 - 1 error(s), 0 warning(s)
7>13>------ Build started: Project: Medical1, Configuration: Debug Win32 ------
7>13>Linking...
7>13>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>13>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Medical\Cxx\Medical1.dir\Debug\BuildLog.htm"
7>13>Medical1 - 1 error(s), 0 warning(s)
7>14>------ Build started: Project: SGrid, Configuration: Debug Win32 ------
7>14>Linking...
7>15>------ Build started: Project: RGrid, Configuration: Debug Win32 ------
7>14>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>14>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\DataManipulation\Cxx\SGrid.dir\Debug\BuildLog.htm"
7>14>SGrid - 1 error(s), 0 warning(s)
7>15>Linking...
7>15>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>15>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\DataManipulation\Cxx\RGrid.dir\Debug\BuildLog.htm"
7>15>RGrid - 1 error(s), 0 warning(s)
7>16>------ Build started: Project: Cube, Configuration: Debug Win32 ------
7>16>Linking...
7>16>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>16>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\DataManipulation\Cxx\Cube.dir\Debug\BuildLog.htm"
7>16>Cube - 1 error(s), 0 warning(s)
7>17>------ Build started: Project: Arrays, Configuration: Debug Win32 ------
7>17>Linking...
7>17>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>17>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\DataManipulation\Cxx\Arrays.dir\Debug\BuildLog.htm"
7>17>Arrays - 1 error(s), 0 warning(s)
7>18>------ Build started: Project: MultiBlock, Configuration: Debug Win32 ------
7>18>Linking...
7>18>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>18>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\MultiBlock\Cxx\MultiBlock.dir\Debug\BuildLog.htm"
7>18>MultiBlock - 1 error(s), 0 warning(s)
7>19>------ Build started: Project: HierarchicalBoxPipeline, Configuration: Debug Win32 ------
7>19>Linking...
7>19>LINK : fatal error LNK1104: cannot open file 'vtkRendering.lib'
7>19>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\AMR\Cxx\HierarchicalBoxPipeline.dir\Debug\BuildLog.htm"
7>19>HierarchicalBoxPipeline - 1 error(s), 0 warning(s)
7>20>------ Build started: Project: Cone6, Configuration: Debug Win32 ------
7>20>Linking...
7>20>LINK : fatal error LNK1104: cannot open file 'vtkWidgets.lib'
7>20>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\Tutorial\Step6\Cxx\Cone6.dir\Debug\BuildLog.htm"
7>20>Cone6 - 1 error(s), 0 warning(s)
7>21>------ Build started: Project: ALL_BUILD, Configuration: Debug Win32 ------
7>21>"Build all projects"
7>21>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\All\ALL_BUILD.dir\Debug\BuildLog.htm"
7>21>ALL_BUILD - 0 error(s), 0 warning(s)
7>========== Build: 1 succeeded, 20 failed, 1 up-to-date, 0 skipped ==========
7>Project : error PRJ0019: A tool returned an error code from "Generating ../VTKExamples"
7>Build log was saved at "file://c:\VTK_BINARY_DIR\Examples\VTKExamplesTarget.dir\Debug\BuildLog.htm"
7>VTKExamplesTarget - 21 error(s), 0 warning(s)
13>------ Build started: Project: ALL_BUILD, Configuration: Debug Win32 ------
13>"Build all projects"
13>Build log was saved at "file://c:\VTK_BINARY_DIR\ALL_BUILD.dir\Debug\BuildLog.htm"
13>ALL_BUILD - 0 error(s), 0 warning(s)
========== Build: 1 succeeded, 12 failed, 27 up-to-date, 0 skipped ==========
On CMake I set:
BUILD_EXAMPLES: "ON"
BUILD_SHARED_LIBS: "ON"
VTK_USE_RENDERING: "ON"
My system is:
Microsoft Windows Vista Home Premium (32-bit)
Visual C++ 2005
SDK update for Windows Vista
CMake 2.4
VTK 5.0.3https://gitlab.kitware.com/vtk/vtk/-/issues/5676crash when writing pvtu file in binary mode2016-08-12T06:48:03-04:00Kitware Robotcrash when writing pvtu file in binary mode**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5676). Further discussion may take place here.**
---
i am trying to write a non ascii vtu file in parallel
i construct a vtkUnstruct...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5676). Further discussion may take place here.**
---
i am trying to write a non ascii vtu file in parallel
i construct a vtkUnstructuredGrid pass it to the vtkXMLPUnstructuredGridWriter
pwriter->SetInput(ug);
pwriter->SetFileName( filename );
if (*myid == 0)
{
pwriter->SetNumberOfPieces(*NumberOfPieces);
pwriter->Write();
}
else
{
pwriter->SetNumberOfPieces(1);
pwriter->SetStartPiece(*myid);
pwriter->SetEndPiece(*myid);
pwriter->Write();
}
in ascii mode this works fine and i get a pvtu file containing
<?xml version="1.0"?>
<VTKFile type="PUnstructuredGrid" version="0.1"
byte_order="LittleEndian" compressor="vtkZLibDataCompressor">
<PUnstructuredGrid GhostLevel="0">
<PPointData Scalars="Scalars_">
<PDataArray type="Float32" Name="Scalars_"/>
</PPointData>
<PPoints>
<PDataArray type="Float32" NumberOfComponents="3"/>
</PPoints>
<Piece Source="test_xml_0.vtu"/>
<Piece Source="test_xml_1.vtu"/>
</PUnstructuredGrid>
</VTKFile>
and two vtu files.
however when i remove pwriter->SetDataModeToAscii(); i get an error message
vtkOffsetsManagerArray.h:140: OffsetsManagerGroup&
OffsetsManagerArray::GetPiece(unsigned int): Assertion `index <
this->Internals.size()' failed.
forrtl: error (76): IOT trap signal
https://gitlab.kitware.com/vtk/vtk/-/issues/5728bug in vtkTriangle::PointInTriangle2016-08-12T06:48:19-04:00Kitware Robotbug in vtkTriangle::PointInTriangle**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5728). Further discussion may take place here.**
---
Consider the case where x lies along one of the edges, say v21, but outside the ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5728). Further discussion may take place here.**
---
Consider the case where x lies along one of the edges, say v21, but outside the edge. Then the vectors x1, x2 and v21 are all pointing in the same direction. Then n2 becomes (0, 0, 0) as the result of the cross product, and both dot products on line 992 evaluate to zero. So the function returns 1, even though the point is not on the triangle (or on the edge). Right?https://gitlab.kitware.com/vtk/vtk/-/issues/5736Exodus reader should support attributes2016-08-12T06:48:21-04:00Kitware RobotExodus reader should support attributes**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5736). Further discussion may take place here.**
---
The vtkExodusIIReader currently supports results variables defined over objects ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5736). Further discussion may take place here.**
---
The vtkExodusIIReader currently supports results variables defined over objects but does not support time-invariant attributes. These should be supported as additional block arrays. They are currently only defined over blocks (not sets or maps).https://gitlab.kitware.com/vtk/vtk/-/issues/5738Exodus reader should provide access to properties2016-08-12T06:48:22-04:00Kitware RobotExodus reader should provide access to properties**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5738). Further discussion may take place here.**
---
The new Exodus library (as of late 2006), supports properties defined over objec...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5738). Further discussion may take place here.**
---
The new Exodus library (as of late 2006), supports properties defined over objects of any type (blocks, sets, and maps). A property has a name (a character string) and a single integer value defined for each object of a given type. There are some standard properties (such as "ID", used to define block/set ID numbers) but these may now be arbitrarily extended.
A list of properties and their values should be accessible through the reader. Also, it may be desirable to coordinate properties in an Exodus file with DART metadata files since both may contain the same information.https://gitlab.kitware.com/vtk/vtk/-/issues/5740Exodus reader needs a convention for indicating global IDs2016-08-12T06:48:23-04:00Kitware RobotExodus reader needs a convention for indicating global IDs**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5740). Further discussion may take place here.**
---
Nodes, elements, faces, and edges may all have multiple maps associated with the...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5740). Further discussion may take place here.**
---
Nodes, elements, faces, and edges may all have multiple maps associated with them in the new Exodus file format. To my knowledge, there is not currently any way to know which map represents a global ordering across multiple files. Each map may be assigned a name, but I am unaware of a convention for specifying the purpose of a map in its name.https://gitlab.kitware.com/vtk/vtk/-/issues/4946vtkExodusIIReader doesn't provide model metadata2016-08-12T06:48:23-04:00Kitware RobotvtkExodusIIReader doesn't provide model metadata**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4946). Further discussion may take place here.**
---
The new vtkExodusIIReader doesn't yet create model a metadata object containing ...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=4946). Further discussion may take place here.**
---
The new vtkExodusIIReader doesn't yet create model a metadata object containing QA records, etc. from the Exodus file.
This is a feature request to replace the original bug (#4923) that caused crashes.https://gitlab.kitware.com/vtk/vtk/-/issues/5741Exodus metadata should be available from Python (and other wrapped languages)2016-08-12T06:48:23-04:00Kitware RobotExodus metadata should be available from Python (and other wrapped languages)**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5741). Further discussion may take place here.**
---
Issue #4946 requests metadata be added to the vtkExodusIIReader. This issue furt...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5741). Further discussion may take place here.**
---
Issue #4946 requests metadata be added to the vtkExodusIIReader. This issue further requests the metadata to be accessible via wrapped member functions so that python scripts can process the metadata.https://gitlab.kitware.com/vtk/vtk/-/issues/5754Black spots on surface rendered model when switching from one window to another2016-08-12T06:48:28-04:00Kitware RobotBlack spots on surface rendered model when switching from one window to another**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5754). Further discussion may take place here.**
---
I’m using the latest ‘unstable’ release of VTK (5.1.0) in order to develop a too...**This issue was created automatically from an original [Mantis Issue](http://vtk.org/Bug/view.php?id=5754). Further discussion may take place here.**
---
I’m using the latest ‘unstable’ release of VTK (5.1.0) in order to develop a tool able to generate 3d models from dicom images and to view them in stereo mode.
The problem: when I have two windows opened (one is the 2d viewer, the other is the 3d viewer) in the 3d viewer I correctly visualize a surface rendered model in stereo mode (CrystalEyes, active stereo mode converted to the passive one by using a nVidia Quadro FX3500 graphics card), but if I switch on the other window (keeping the 3d viewer window opened in background) and then I return on the 3d viewer window the model becomes partially black!
If on the 3d viewer I switch to the anaglyph stereo mode, and then again to the CrystalEyes ones, the 3d model is probably recomputed and the black spots disappear.
This problem doesn’t happen if I use the last stable version of VTK (5.0.3), but I need to use the new one.