MantisBT - ParaView
View Issue Details
0011697ParaViewBugpublic2011-01-14 10:302012-02-08 17:24
Paul Edwards 
Kyle Lutz 
normalmajoralways
closedfixed 
Development 
3.123.12 
TBD
11697-fix-d3-data-type
incorrect functionality
0011697: All points are converted to floating point when run through D3
The points datatype is always float regardless of the datatype going in.
Run attached script. Output:


8<-----------------------------------------------------------------
paul@localhost:~/d3test$ pvpython d3-bug-double-precision-points-lost.py
Listen on port: 11111
Waiting for client...
Client connected.
vtkSphereSource : [ ...........]
vtkSphereSource(1) : [ ...........]
vtkSphereSource : [ ...........]
Process id: 0 >> Datatype is 11
Process id: 1 >> Datatype is 11
vtkPythonProgrammableFilter(1) : [ ...........]
vtkDistributedDataFilter(1) : [ ...........]
Clean up and finish : [ ...........]
vtkPythonProgrammableFilter(1) : [ ...........]
Process id: 0 >> Datatype is 10
Process id: 1 >> Datatype is 10
paul@localhost:~/d3test$
----------------------------------------------------------------->8
Additional point data will stay the same type - it is only for the coordinates.
No tags attached.
? d3-bug-double-precision-points-lost.py (1,158) 2011-09-05 05:54
https://www.vtk.org/Bug/file/9016/d3-bug-double-precision-points-lost.py
patch d3-bug-double-precision-points-lost.patch (571) 2011-09-05 05:55
https://www.vtk.org/Bug/file/9017/d3-bug-double-precision-points-lost.patch
Issue History
2011-01-14 10:30Paul EdwardsNew Issue
2011-01-20 09:39Utkarsh AyachitAssigned To => Utkarsh Ayachit
2011-01-20 09:39Utkarsh AyachitStatusbacklog => tabled
2011-09-05 05:54Paul EdwardsFile Added: d3-bug-double-precision-points-lost.py
2011-09-05 05:55Paul EdwardsFile Added: d3-bug-double-precision-points-lost.patch
2011-09-05 05:56Paul EdwardsNote Added: 0027453
2011-09-05 10:16Kyle LutzAssigned ToUtkarsh Ayachit => Kyle Lutz
2011-09-05 10:16Kyle LutzStatusbacklog => todo
2011-09-05 10:16Kyle LutzStatustodo => active development
2011-09-05 10:23Kyle LutzTopic Name => 11697-fix-d3-data-type
2011-09-05 10:23Kyle LutzNote Added: 0027454
2011-09-05 10:23Kyle LutzStatusactive development => gatekeeper review
2011-09-05 10:23Kyle LutzResolutionopen => fixed
2011-09-05 10:24Kyle LutzNote Added: 0027455
2011-09-06 09:07Utkarsh AyachitProject => TBD
2011-09-06 09:07Utkarsh AyachitType => incorrect functionality
2011-09-06 09:07Utkarsh AyachitTarget Version => 3.12
2011-09-09 14:13Utkarsh AyachitFixed in Version => git-master
2011-09-09 14:14Utkarsh AyachitStatusgatekeeper review => customer review
2011-09-09 14:14Utkarsh AyachitNote Added: 0027467
2011-11-11 17:03Utkarsh AyachitFixed in Versiongit-master => 3.12
2012-02-08 17:24Utkarsh AyachitStatuscustomer review => closed
2012-02-08 17:24Utkarsh AyachitNote Added: 0028143

Notes
(0027453)
Paul Edwards   
2011-09-05 05:56   
I just realised I didn't add the python test. I have also added a patch to fix the issue.
(0027454)
Kyle Lutz   
2011-09-05 10:23   
Merge topic '11697-fix-d3-data-type' into pv-next

9aa84ed Perserve original data type in D3 filter


Merge topic '11697-fix-d3-data-type' into next

f54995e Update VTK to bring in '11697-fix-d3-data-type'
(0027455)
Kyle Lutz   
2011-09-05 10:24   
Test output with patch applied:

$ ./pvpython /home/kyle/Downloads/d3-bug-double-precision-points-lost.py
Waiting for client
Connection URL: cs://localhost:11111
Client connected.
Datatype is 11
Datatype is 11
Datatype is 11
Datatype is 11
Exiting...
Exiting...
(0027467)
Utkarsh Ayachit   
2011-09-09 14:14   
merged into git-master.
(0028143)
Utkarsh Ayachit   
2012-02-08 17:24   
Closing bugs sitting in "customer review" for a long time.