AmortizingFixedRateBond question

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

AmortizingFixedRateBond question

Nathan Abbott

Hello,

We've got a question on AmortizingFixedRateBond. We've been looking at this class very carefully and do not quite understand why it can be constructed with both a vector of -amortizing- notionals and a vector of redemptions. Aren't you double counting that way? We assumed the class could either be constructed a) with a vector of amortizing notionals and no redemptions vector (or redemptions only set to the default=100) or b) with a fixed amount and a vector of redemptions from which the actual notionals would be calculated, but not with both a notionals and a redemption vector. Are we missing some peculiar way this class is supposed to be able to behave here?

Thank You.


------------------------------------------------------------------------------

_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users
Reply | Threaded
Open this post in threaded view
|

Re: AmortizingFixedRateBond question

Luigi Ballabio
On Wed, 2009-03-25 at 18:39 -0700, Nathan Abbott wrote:
> We've got a question on AmortizingFixedRateBond. We've been looking at
> this class very carefully and do not quite understand why it can be
> constructed with both a vector of -amortizing- notionals and a vector
> of redemptions. Aren't you double counting that way?

No, it's an extension of a special case---but it's probably not needed.
Sometimes we came across bonds that didn't reimburse the full amount at
the end, but only, say, 99.5.  In the old constructor, that would be
passed in the "redemption" field.  With amortizing bonds, where the
redemption is paid out piecewise, that was extended to a vector (so each
amortization payment could be multiplied by the corresponding number.)
But you're right: it's confusing, and I doubt that this can occur, so
that parameter would better go. In the meantime, just ignore it and
you'll have the expected behavior.

Luigi


--

The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" but "That's funny..."
-- Isaac Asimov



------------------------------------------------------------------------------
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users