Closed ZircXes closed 6 years ago
The more I think about this...the more I think this is necessary. Especially keeping everything in sync once calibration is added.
However, it wont be trivial to add text boxes with validation.
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.