[Kst] [Bug 110734] Ability to mask datapoints for fits and other operations etc.

Nicolas Brisset nicolas.brisset at eurocopter.com
Tue Aug 23 10:15:17 CEST 2005

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From nicolas.brisset eurocopter com  2005-08-23 10:15 -------
I like this idea... and Andrew's suggestions. They don't seem to be too difficult to implement or use, the biggest issue here probably being performance. 

I don't think it is necessary to be able to edit data points in a spreadsheet interface for that feature (Barth, can you give a use case where suggestions 1) e.g. with Del+LMB or 2) above would not be handy enough ?). Just keeping an optional array of invalid points for each vector sould be enough. There should not be too many of them in normal cases... Invalid points should be drawn with a different color or point style, and possibly excluded when drawing lines.

Thinking a bit more about this, I do see potential difficulties from a user interaction perspective wrt Andrew's suggestion number 1: as curves are made up of 2 vectors (or more in some cases), how can the user specify which point is invalid ? Can we assume that the Y value is wrong or should we bring up a dialog for the user to indicate whether he wants to invalidate the X or Y value (would be my prefered solution) ? And how about curves involving vectors with different lengths where some points are actually interpolated: invalidate closest point or disable the feature ? 

I believe this feature is important and I hope it will be implemented in spite of these difficulties :-) 
As for the "fit to visible points only" feature, it should be possible to exclude whole ranges and not just isolated points. We just need to find the best solution to store isolated points as well as ranges in the "invalid points" container(s). Invalid data could then be excluded from all computations (fits, filters, etc...), which would require kst to pass "arranged" vectors to plugins.

More information about the Kst mailing list