2
$\begingroup$

I am presently engaged in a project wherein my objective is to construct a volatility surface utilizing either the SVI parameterization or the SABR model, leveraging real market data. Initially, I used mid/mark implied volatility for the purpose of calibration, yielding relatively satisfactory fit. However, my calibration attempts using ask_iv or bid_iv have yielded very bad fits.

I find myself in a state of uncertainty as to the underlying reasons for these subpar calibrations when utilizing ask or bid implied volatility. Logically, it stands to reason that individuals engaged in trading activities would typically reference either ask or bid implied volatility when executing their orders. Consequently, I am curious if there exist specific guidelines or best practices that one should adhere to when fitting the volatility surface with ask/bid_iv data. Furthermore, I am interested in understanding how market participants make trading decisions based on a volatility surface calibrated using mid/mark_iv. It's pertinent to mention that the options I am dealing with are relatively illiquid.

I would greatly appreciate any references to books, research papers, blogs, or any resources that delve into this subject matter, as they would prove invaluable to my project.

$\endgroup$
2
  • $\begingroup$ Gatheral, J., Jacquier, A. Arbitrage-free SVI volatility surfaces. Quantitative Finance, 14(1):59–71, 2014. $\endgroup$
    – Nick
    Sep 10 at 16:41
  • $\begingroup$ Could you please clarify what is "very bad fit"? There are multiple problems that might contribute to the bad fit (for example, absence of syncronization between options price time and underlying price time). There is nothing wrong with using mid point for fitting the surface, some industry standard vendors are doing it (e.g. Optionmetrics) $\endgroup$
    – Eli
    Oct 2 at 13:03

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.