View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0001590 | VTK | (No Category) | public | 2005-02-10 01:27 | 2016-08-12 09:54 | ||||
Reporter | Frank | ||||||||
Assigned To | Dave DeMarle | ||||||||
Priority | high | Severity | major | Reproducibility | always | ||||
Status | closed | Resolution | moved | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0001590: Copying input instead of source point data in vtkGlyph3D | ||||||||
Description | 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); | ||||||||
Tags | No tags attached. | ||||||||
Project | |||||||||
Type | |||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0002082) Mathieu Malaterre (developer) 2005-02-18 16:24 |
Seems to interfere with other bug: Bug #455 - Glyph does not pass all point data. |
(0002083) Mathieu Malaterre (developer) 2005-02-18 16:27 |
Closing bug. Preferer behavior was to copy from source. |
(0002117) Mathieu Malaterre (developer) 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 (manager) 2013-06-05 16:43 |
Does the problem still occur with VTK 5.10 ? VTK 6 ? |
(0031204) Dave DeMarle (administrator) 2013-07-22 18:59 |
If this is still an issue in VTK6, please reopen. |
(0034293) Andreas Buykx (reporter) 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 (administrator) 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. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2008-11-30 09:27 | Mathieu Malaterre | Status | backlog => tabled |
2008-11-30 09:27 | Mathieu Malaterre | Assigned To | Mathieu Malaterre => David Cole |
2011-01-19 10:20 | David Cole | Assigned To | David Cole => |
2011-06-16 13:11 | Zack Galbreath | Category | => (No Category) |
2013-06-05 16:43 | Jean-Christophe Fillion-Robin | Note Added: 0030925 | |
2013-07-22 18:59 | Dave DeMarle | Note Added: 0031204 | |
2013-07-22 18:59 | Dave DeMarle | Status | backlog => expired |
2013-07-22 18:59 | Dave DeMarle | Resolution | reopened => open |
2013-07-22 18:59 | Dave DeMarle | Assigned To | => Dave DeMarle |
2015-03-05 04:36 | Andreas Buykx | Note Added: 0034293 | |
2016-08-12 09:54 | Kitware Robot | Note Added: 0036766 | |
2016-08-12 09:54 | Kitware Robot | Status | expired => closed |
2016-08-12 09:54 | Kitware Robot | Resolution | open => moved |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |