We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Numpy-financial functions:
fv(rate, nper, pmt, pv[, when])
ipmt(rate, per, nper, pv[, fv, when])
irr(values)
mirr(values, finance_rate, reinvest_rate)
nper(rate, pmt, pv[, fv, when])
npv(rate, values)
pmt(rate, nper, pv[, fv, when])
ppmt(rate, per, nper, pv[, fv, when])
pv(rate, nper, pmt[, fv, when])
rate(nper, pmt, pv, fv[, when, guess, tol, …])
Not sure that we actually want to have all of these. ActuaryUtilities provides a more flexible interface, I think?
E.g. for present value, the above definition restricts you:
npv
pv
In contrast, with ActuaryUtilities present_value(rate,cfs,times) or pv:
present_value(rate,cfs,times)
rate
cfs
times
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Numpy-financial functions:
fv(rate, nper, pmt, pv[, when])
| Compute the future value.ipmt(rate, per, nper, pv[, fv, when])
| Compute the interest portion of a payment.irr(values)
| Return the Internal Rate of Return (IRR).mirr(values, finance_rate, reinvest_rate)
| Modified internal rate of return.nper(rate, pmt, pv[, fv, when])
| Compute the number of periodic payments.npv(rate, values)
| Returns the NPV (Net Present Value) of a cash flow series.pmt(rate, nper, pv[, fv, when])
| Compute the payment against loan principal plus interest.ppmt(rate, per, nper, pv[, fv, when])
| Compute the payment against loan principal.pv(rate, nper, pmt[, fv, when])
| Compute the present value.rate(nper, pmt, pv, fv[, when, guess, tol, …])
| Compute the rate of interest per period.Not sure that we actually want to have all of these. ActuaryUtilities provides a more flexible interface, I think?
E.g. for present value, the above definition restricts you:
npv
you can have a vector of rates, but not specify the timepoints. And the rate needs to be constantpv
is the old calculator bond formula. Great for doing a super simple bond calc, but for everything else...?In contrast, with ActuaryUtilities
present_value(rate,cfs,times)
orpv
:rate
can be a constant or a curvecfs
can varytimes
lets you specify when cashflows occur and they can be of varying magnitude and at uneven timesThe text was updated successfully, but these errors were encountered: