-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Support the Canadian Overnight Repo Rate Average (CORRA) #1685
Comments
Methodology for calculating the Canadian Overnight Repo Rate Average (CORRA) says:
So i think settlementDays is 0, as for other repo indexes.
That sounds like normal bank holidays to me, which is what i believe the Canada(Settlement) calendar represents. There's no explicit mention of a day count convention there. The convention will be whatever is used in the repo market. However, the CORRA Compounded Index is defined in terms of CORRA using a 365-day year, which suggests that CORRA is actual/365. How-to Guide: SFTR repo day-count conventions, a piece by some hardcore repo transaction reporting geek, gets into some glorious detail about repo day count conventions, and says:
So dayCounter is Actual365Fixed(). |
You might be interested to look in the OpenSourceRisk project. They have CORRA implemented: https://github.com/OpenSourceRisk/Engine/blob/master/QuantExt/qle/indexes/ibor/corra.hpp It may be possible to move this code into QuantLib itself. |
Is anyone working on this? I am a new contributor - I think this is a new contributor friendly issue. Can I work on this? |
- remove idle "//"
Sure, go ahead! |
PR here: #1705 |
- add corra.cpp/.hpp to build files
I only just noticed we don't have an index class for this. It's a popular interest rate index in Canada, and after 28 June 2024, it will be the only interest rate index in Canada.
https://www.bankofcanada.ca/rates/interest-rates/corra/
It's an overnight index, so adding it should be extremely straightforward, in the mould of ESTR and SOFR. We need to know:
Family name and currency are obvious. We should be able to find out the others by reading the index documentation. Hopefully it doesn't use some wacky calendar we don't currently have (like SOFR :) ).
There's a strong chance i will have to do this locally soon, and i will push it back up if so.
The text was updated successfully, but these errors were encountered: