Skip to content
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

CMS accrual range swap #195

Open
EazyDS opened this issue Nov 19, 2023 · 2 comments
Open

CMS accrual range swap #195

EazyDS opened this issue Nov 19, 2023 · 2 comments

Comments

@EazyDS
Copy link

EazyDS commented Nov 19, 2023

Hi,
Is there a way to represent cms spread accrual range swap with ORE ? I am excited about playing with scripted trades feature but can't find a way to make it for this product either with scripted trades or directly with xml or others. (it can be seen as a strip of digital cms - one for each day during accumulation period). Are there any helpful example for cms range somewhere with callability (to make it general).
Regards.

@rolandlichters
Copy link
Contributor

Hi,
apologies for the late reply - indeed, you should be able to represent that payoff as a scripted trade, but we haven't got an out-of-the box example there. Would you like to have a go and contribute an example? The ST will also be able to handle callability. But note that we are currently using a single factor Gaussian IR model under the ST, which does not seem appropriate for CMS Spreads. We really need to build this out to multi-factor models for such cases, stochastic volatility etc - there is still a lot to do in ORE.
You could also have a look at the "formula leg", to be released in v12. This can handle CMS Spreads with Caps/Floors using a multi-factor lognormal model, but it does not cover callability, nor the range accrual feature.
Best wishes,
Roland

@EazyDS
Copy link
Author

EazyDS commented May 16, 2024

Hi, thanks for your reply. I am happy to contribute an example but as you mentioned there is a current limitation to single factor gaussian IR model which is indeed not suitable for spreads.
Regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants