Created attachment 144524 [details] spreadsheet showing bug Using the YIELD function, with basis argument 3 ("Exact number of days in month, year has 365 days"), for the different settlement and maturity dates but with the same number of days inbetween those dates, results in different yield numbers. They are also different from the output in MS Excel while the two programs agree when the default basis of 0 is used (360 days in the year, 30 days in the month). Maybe something is going wrong with the dates math.
On Win7 with LO 6.0.6.2, I confirm the behavior. 0,055482928352414 in column A 0,055402701880945 in column D In comparison with Excel 2013, I got 0,055362676 for both columns.
Zdenek: noticing https://cgit.freedesktop.org/libreoffice/core/commit/?id=1b52171752d5e4f9fc101a8bc15f6feb6599aaa2, thought you might be interested in this one.
I get different results compared to comment 1: 0,055482928352414 in column A 0,055402701880945 in column D in Version: 6.2.0.0.alpha0+ Build ID: 3bd8316718fdfed454c01a9c4ae6af6beb34437d CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: threaded and Versión: 6.1.0.3 Id. de compilación: efb621ed25068d70781dc026f7e9c5187a4decd1 Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group threaded as well as in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 In Excel 2010 I get: 0,055362676 in Column A 0,055363 in Column D
Created attachment 144548 [details] File created with Excel 2010 However, the problem is not reproduced with a file created in MSO Excel 2010. In Version: 6.2.0.0.alpha0+ Build ID: 3bd8316718fdfed454c01a9c4ae6af6beb34437d CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: threaded I get 0,055362675668767 in Column A 0,05536 in Column D
@Eike, @Winfried, I thought you could be interested in this issue...
By the way, using basis 1 (Exact number of days in months, exact number of days in year) displays different numbers as well for the same number of days in the period, but the difference is much smaller than that for basis 3.
I looked into this and I have a problem... with Excel's answers. The calculations in column A and D both have a frequency value of 2, meaning that twice a year the interest is applied: at the 30 June - 1 July crossing and the 31 December - 1 January crossing. As the settlement date differs between column A and D, the time from settlement to first coupon date differs too. Consequently, the interest accrued differs and therefore the yield. As I am not a financial expert, I am not 100% certain of my conclusion, but currently I have confidence in Calc's results of YIELD.
Dear Stan, 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 https://www.libreoffice.org/download/ 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Stan, 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 https://www.libreoffice.org/download/ 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 https://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Stan, 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 https://www.libreoffice.org/download/ 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 https://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug