Quote from uncleTom:
Ok. SO what you're saying is that I could use the 365 although my volatility and therefore theoretical option prices would be different?
Just pick whether you want greeks computed per trading day or per calendar day. In other words, if you compute the volatility and time remaining per 365 days, you'll get theta per calendar day, for example. Option pricing won't make much of a difference no matter which you use, although you'll get some quantum jumps on Fridays and Mondays if you use calendar pricing.
Did you see that I was lost on the volatility days? Isn't really the length of the close array, closeData.length?
See page #3 of these posts--it's a constant representing the number of lookback days to compute the volatility over. 20 trading days is a frequently used number.
the method call dfc.getCloseData()? Is that the way you open the file with closing prices?
The method returns an array of closing prices.
Ok. SO what you're saying is that I could use the 365 although my volatility and therefore theoretical option prices would be different?
Just pick whether you want greeks computed per trading day or per calendar day. In other words, if you compute the volatility and time remaining per 365 days, you'll get theta per calendar day, for example. Option pricing won't make much of a difference no matter which you use, although you'll get some quantum jumps on Fridays and Mondays if you use calendar pricing.
Did you see that I was lost on the volatility days? Isn't really the length of the close array, closeData.length?
See page #3 of these posts--it's a constant representing the number of lookback days to compute the volatility over. 20 trading days is a frequently used number.
the method call dfc.getCloseData()? Is that the way you open the file with closing prices?
The method returns an array of closing prices.
