You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 14, 2019. It is now read-only.
Yeah, in order to calibrate, we would need to have specific daycounts, and the user would select the volatility based on the daycount convention.
Example: I can use a BSM calculator online, but I had to use an analytical tool offline to test the model because the calculator was using a 365 day level which cannot be cleanly divided given the inputs.
If we want to get into day count conventions we are going to get into some interesting territory. The open source Quantlib spends what appears to be the majority of its code on timing issues.
I think we can avoid daycount conversions by allowing an input for T and volatility; however, for calibration purposes, the user has to consistently apply T and volatility.
Inputs are drop-downs instead of a text-box with data validation.
The text was updated successfully, but these errors were encountered: