Skip to content
This repository has been archived by the owner on Oct 14, 2019. It is now read-only.

Inputs are drop-downs instead of a text-box with data validation. #58

Closed
ZircXes opened this issue Jan 14, 2018 · 4 comments
Closed

Inputs are drop-downs instead of a text-box with data validation. #58

ZircXes opened this issue Jan 14, 2018 · 4 comments

Comments

@ZircXes
Copy link
Contributor

ZircXes commented Jan 14, 2018

Inputs are drop-downs instead of a text-box with data validation.

@danielhstahl
Copy link
Owner

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.

@ZircXes
Copy link
Contributor Author

ZircXes commented Jan 14, 2018

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.

@danielhstahl
Copy link
Owner

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.

@ZircXes
Copy link
Contributor Author

ZircXes commented Jan 14, 2018

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.

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

No branches or pull requests

2 participants