-
Notifications
You must be signed in to change notification settings - Fork 769
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong computation of functionality. #256
base: trunk
Are you sure you want to change the base?
Conversation
I got to know that Npv is giving a wrong value . |
@Bhanu17Sharma02 can you provide an example that we can use to verify this? For instance, some numbers and what the function should return so that we can verify this change? |
@pjfanning |
my excel returns 328.92 for npv(0.08, -1000, 500, 300, 800) - so I won't be merging this PR as is |
@pjfanning ok , but take a look in your excel . I think you are applying this term "-1000/(1+0.08)^1" also in computation but-1000 should not be divide by (1+0.08)^1.So it is a computational mistake. |
the existing code works with the examples in https://support.microsoft.com/en-us/office/npv-function-8672cb67-2576-4d07-b67b-ac28acf2a568 I think you have a bug in your logic We will not be changing the POI code unless you can provide an excel file where the result of the npv calc does not match what POI calculates. |
Thanks for sharing a Microsoft reference, I went through it, |
Just to add to this @pjfanning , I've been using a python library called numpy-financial that offers the same functions and has the same function signature, the results we get from POI and numpy-financial do not match. |
I'm not sure if you are not misusing the POI npv call - in your excel, you have If you use POI is a Java port of Excel and we have to match Excel, we do not want to match numpy - our users expect us to match Excel |
No description provided.