Download it now!
Bug 47787 - B Spline interpolation is broken
Summary: B Spline interpolation is broken
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
(earliest affected)
Master old -3.6
Hardware: Other All
: medium normal
Assignee: Not Assigned
: 57234 (view as bug list)
Depends on:
Blocks: Chart
  Show dependency treegraph
Reported: 2012-03-23 18:03 UTC by Markus Mohrhard
Modified: 2020-09-17 04:07 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

File for experiments (21.93 KB, application/vnd.oasis.opendocument.spreadsheet)
2012-03-31 11:28 UTC, Regina Henschel

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Mohrhard 2012-03-23 18:03:21 UTC
B Spline interpolation is broken for some documents.

Open the test document attached to Bug 47632 and switch to edit mode. Somewhere in Splines.cxx must be an error implementing the algorithm mentioned in ODF 1.2.
Comment 1 Markus Mohrhard 2012-03-24 13:20:00 UTC
Algorithm is implemented in chart2/source/view/charttypes/Splines.cxx
Comment 2 Markus Mohrhard 2012-03-30 19:51:59 UTC
This one is getting really nasty. I have more or less implemented the algorithm totally new and added unit tests but the algorithm results in memory corruption.

Have to spend some time on other calc bugs.
Comment 3 Regina Henschel 2012-03-31 11:28:30 UTC
Created attachment 59314 [details]
File for experiments

Hi Markus. I think, that the problem is caused by identical y-values. When you increase the x- or y-values step by step, you can notice, that the amplitude of the curves increases too. I tend to think, that this cannot be avoided, because B-Spline interpolation curves are parametric. I guess, that it is a property of this kind of interpolation.
When you agree to that and not find an error in the algorithm, I suggest, that we implement some functional interpolation. For those of cause the x-values have to be sorted as it has been in older versions of OOo. Perhaps we can discuss this on the Hackfest?
Comment 4 Markus Mohrhard 2012-03-31 21:34:16 UTC
Hey Regina,

I don't think that the B-Spline algorithm itself has a problem with identical y values. I fear more that one of our assumptions in the implementation is wrong.

I think I remember from my Numerical Math 2 lecture that there is no such limitation for B splines but I would need to check with my script.

I have now to fix some more calc bugs before I can come back to this problem but I will finally try to run this data through MATLAB and compare the result of each individual step with the MATLAB result.

I already did that for the creation of t and u with my reworked implementation and they were the same in matlab and in my implementation. I will try to get the splitted up implementation into master before the hackfest and hopefully the test data ready until then.

Sadly we are not free to implement another algorithm because ODF1.2 explicitly mentions this algorithm. Nevertheless if there is really a problem with the ODF algorithm we may talk to Kohei/Thorsten how to proceed.
Comment 5 Markus Mohrhard 2013-02-14 16:40:02 UTC
*** Bug 57234 has been marked as a duplicate of this bug. ***
Comment 6 Thomas Lendo 2017-06-17 12:32:23 UTC
Is there any development in working on this bug or should it be unassigned? Last comment is from 2012.
Comment 7 Xisco Faulí 2017-09-16 13:48:00 UTC
Dear developer,
This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW.
Please assigned it back to yourself if you're still working on this.
Comment 8 QA Administrators 2018-09-17 02:46:41 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2020-09-17 04:07:30 UTC
Dear Markus Mohrhard,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat:

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team