June 20th, 2011, 2:12 pm
My objective in seeking a fit is not to determine a theoretical volatility (I use a kernel-based smoother for that) but rather to generate an estimate of skew (dsigma/dK), which for technical reasons my kernel-based smoother does not generate efficiently. Skew is needed to plug into the "swimming delta" formula, i.e. the adjustment to make to hedging deltas under the assumption of an ATM skew that stays constant w.r.t. underlier price move.Therefore, my definition of "robust" is a polynomial of nth degree that i) minimizes error over the interval of low strike to high strike, and ii) has a slope who's avg. error is no worse at the interval edge than anywhere else in the interval (i.e. doesn't become unstable at the interval edge).I'm not a math genius, but using a polynomial with a degree that's too high will introduce this type of instability as described at the wiki page I linked below. Piecewise polynomials are also a possibility. However, one problem we always encounter is the possibility that one or more strikes is poorly quoted, or quoted wide (i.e. a worth option which is 0 bid @ $5). If that option happens to sit on the boundary between two polynomials you can get a really rotten skew.Just curious if anyone has seen this particular problem and what they did about it.