Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 216041

Summary: qtiplot-0.9.4 matrix/3dplot malfunction
Product: Gentoo Linux Reporter: George Deligeorgis <deligeo>
Component: Current packagesAssignee: Gentoo Science Related Packages <sci>
Status: RESOLVED INVALID    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Ascii data causing the malfunction
screenshot of the resulting plots

Description George Deligeorgis 2008-04-03 14:06:19 UTC
Importing a large set of data in qtiplot and trying to plot them in 3dplot
results in corrupted plot. The data in the matrix also appear to be corrupted
I have also filed a bug report in qtiplot main page (bug #13543) although it is not clear whether this is due to some lib not working correctly or the main qtiplot application.
I'll try to add the related files.

Reproducible: Always

Steps to Reproduce:
1.Import the ascii data
2.convert spreadsheet to matrix and delete the first 2 columns ( which contain X data)
3.plot 3d wireframe. the curves are partially corrupted on the low x values side.

Actual Results:  
The 3dplot should be symmetric and it is not. A 2d plot on the spreadsheet is helpfull to see the expected shape

Expected Results:  
The 3dplot should be symmetric

Recompiled everything to make sure this is not a broken dependency issue.
Gentoo amd64 on Intel core 2 duo with:
gsl-1.11
qwt-5.0.2
qwtplot3d-0.2.7
muParser-1.28
liborigin-20080225
scipy-0.6.0-r4
pygsl-0.9.0
Comment 1 George Deligeorgis 2008-04-03 14:07:27 UTC
Created attachment 148261 [details]
Ascii data causing the malfunction

This is the ascii data that are used to replicate the problem
Comment 2 George Deligeorgis 2008-04-03 14:09:13 UTC
Created attachment 148262 [details]
screenshot of the resulting plots

Plot on the left is the wrong 3dplot.
PLot on the right is the 2dplot of the data in spreadsheet.
Comment 3 George Deligeorgis 2008-04-04 07:56:42 UTC
Closing this bug. 
It is the ascii data that have a non-uniform x value set.
The software is working as expected.