Dear all, I am currently looking at the capstripper in QL test-suite. Regarding
the tests performed on the capstripper I would like to know if there is a
particular reason why the matrix the capstripper is tested on does not include
ATM strikes. Furthermore the capstripper header includes two more test cases.
Will these test cases be included in the future? At last, please allow me to
remark that it would also be very helpful to include a test case of pricing a
cap using the capstripper. Many thanks in advance. Best regards, Laurent
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ QuantLib-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-users |
Hi Laurent,
We do not include the ATM values in the volatility matrix because we haven’t found a sensible to way to use it. The algorithm we have implemented can be sketched as follow: For each strike we start by assuming that the first stripped volatility is equal to the first implied volatility. Then we price the following cap using this value for the caplets which correspond to the first part. We deduce the price of the rest of the cap and we compute the corresponding implied volatility. Here is an example of the values you can expect:
Ex: 1Y cap 12% -> iv = 12% 2Y cap 14% -> iv = 14.5% 3Y cap 13% -> iv = 11%
In more complex settings we use volatilities given by futures options as starting point. ( in this case the CapStripper is used with an HybridCapletVolatilityStructure). As for the unimplemented functions declared in the header file I have just removed them and put a comment instead. (One of them was redundant with other tests and the other should be implemented later on). We are actually pricing caps during tests (in the highPrecisionTest for example) though I agree that it is not the most simple use case we can imagine. Maybe a good way to get used to these stuffs is to use the Object Wizard in QuantLibLXL (which I have just rewritten by the way ;-) Regards, François
-----Original
Message-----
Dear all,
I am currently looking at the capstripper in QL test-suite. Regarding the tests performed on the capstripper I would like to know if there is a particular reason why the matrix the capstripper is tested on does not include ATM strikes. Furthermore the capstripper header includes two more test cases. Will these test cases be included in the future? At last, please allow me to remark that it would also be very helpful to include a test case of pricing a cap using the capstripper.
Many thanks in advance. Best regards,
Laurent
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ QuantLib-users mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-users |
Free forum by Nabble | Edit this page |