MantisBT - VTK
View Issue Details
0001590VTK(No Category)public2005-02-10 01:272016-08-12 09:54
Frank 
Dave DeMarle 
highmajoralways
closedmoved 
 
 
0001590: Copying input instead of source point data in vtkGlyph3D
As far as I understand, for vtkGlyph3D, the point data copied to the output must come from the SOURCE and not the INPUT. This was correct in VTK < 4.5.

In vtkGlyph3D.cxx, line 268 is currently:
    pd = input->GetPointData();
This should be:
    pd = source->GetPointData();

And then on line 576:
        outputPD->CopyData(pd,inPtId,ptIncr+i);
Should be:
        outputPD->CopyData(pd,i,ptIncr+i);
No tags attached.
Issue History
2008-11-30 09:27Mathieu MalaterreStatusbacklog => tabled
2008-11-30 09:27Mathieu MalaterreAssigned ToMathieu Malaterre => David Cole
2011-01-19 10:20David ColeAssigned ToDavid Cole =>
2011-06-16 13:11Zack GalbreathCategory => (No Category)
2013-06-05 16:43Jean-Christophe Fillion-RobinNote Added: 0030925
2013-07-22 18:59Dave DeMarleNote Added: 0031204
2013-07-22 18:59Dave DeMarleStatusbacklog => expired
2013-07-22 18:59Dave DeMarleResolutionreopened => open
2013-07-22 18:59Dave DeMarleAssigned To => Dave DeMarle
2015-03-05 04:36Andreas BuykxNote Added: 0034293
2016-08-12 09:54Kitware RobotNote Added: 0036766
2016-08-12 09:54Kitware RobotStatusexpired => closed
2016-08-12 09:54Kitware RobotResolutionopen => moved

Notes
(0002082)
Mathieu Malaterre   
2005-02-18 16:24   
Seems to interfere with other bug:
Bug #455 - Glyph does not pass all point data.
(0002083)
Mathieu Malaterre   
2005-02-18 16:27   
Closing bug. Preferer behavior was to copy from source.
(0002117)
Mathieu Malaterre   
2005-02-25 10:29   
Reopening bug. Frank reported that:

[What happens at the moment is that the ENTIRE data set(s) of the INPUT points are copied IN FULL to every glyph.

This means that if I have say a 1000 input points, each with say 10 scalar values, then all this data (1000x10) gets copied for each of the 1000 glyphs! VERY slow and memory intensive, which was what first alerted me that something was wrong.]
(0030925)
Jean-Christophe Fillion-Robin   
2013-06-05 16:43   
Does the problem still occur with VTK 5.10 ? VTK 6 ?
(0031204)
Dave DeMarle   
2013-07-22 18:59   
If this is still an issue in VTK6, please reopen.
(0034293)
Andreas Buykx   
2015-03-05 04:36   
I noticed that copying point-data depends on whether indexing is used or not.
When not using indexing, input point-data are copied, when indexing is used, source-point-data is copied.
(0036766)
Kitware Robot   
2016-08-12 09:54   
Resolving issue as `moved`.

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