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

pricing a callable floater - valid combinations of swap/swaption classes, ir models, and swaption pricing engines #1979

Closed
eduzea opened this issue May 23, 2024 · 3 comments
Labels

Comments

@eduzea
Copy link

eduzea commented May 23, 2024

Hi,

I'm looking to price a bermudan callable floating rate bond using quantlib. I'm trying to adapt the approach explained in the "Gaussian1D Model" notebook in the ql examples, that is, modeling "a swaption to enter into a one leg swap with notional reimbursement at maturity". I would like to use HullWhite as the model, and an engine such as Bachelier or TreeSwaption engine.

The problem I'm facing is that it seems to use HullWhite I need to use the Swaption class, which in turn needs an underlying VanillaSwap. But I have not found a way to make a VanillaSwap that includes the nomial cashflow at the end. I have been able to create a NonStandard Swap/Swaption with this feature, but then it seems the only engine I can use is the "Gaussian1dNonstandardSwaptionEngine", which in turn requires me to use GSR as the model.

  1. Is it possible to create a VanillaSwap object that includes the nominal payment at maturity? Then I could use this swap with the regular Swaption class and use HullWhite model with the Bachelier or TreeSwaption engine...?

  2. Alternatively, if this can only be done with a NonStandard swap/swaption, is Gaussian1dNonstandardSwaptionEngine the only engine that will be compatible?

Thanks in advance,

Eduardo

Copy link
Contributor

This issue was automatically marked as stale because it has been open 60 days with no activity. Remove stale label or comment, or this will be closed in two weeks.

@github-actions github-actions bot added the stale label Jul 23, 2024
@lballabio lballabio removed the stale label Jul 23, 2024
Copy link
Contributor

This issue was automatically marked as stale because it has been open 60 days with no activity. Remove stale label or comment, or this will be closed in two weeks.

@github-actions github-actions bot added the stale label Sep 22, 2024
Copy link
Contributor

github-actions bot commented Oct 6, 2024

This issue was automatically closed because it has been stalled for two weeks with no further activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants