Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I've been discussing with other TOS users in the TOS forum and even Think or Swim can't seem to answer this. That number in parenthesis to the right of the implied volatility on an option chain is suppose to be a one standard deviation move according to Don Kaufman and other people in the TOS forum. The problem comes when you go to the analyze tab or look at the deltas and add or subtract that EXPECTED move number it doesn't hit a minus 16 or plus 16 delta all the time but the analyze tab doesn't come close to the numbers. This isn't a discussion about skew right now.
With 2 days to go the SPY Friday expiry closed at 244.56 today so adding and subtracting that 1.744 expected move gets you to
246.3 on the upside and 242.8 on the downside yet the Analyze tab show 241.50 and 247.12.......these difference get bigger when you go further out in time....what gives ? What should we use for a one standard deviation move ? I've watched tasty trade videos and theotrade but nothing seems to come together. Here is a screen shot of the analyze . Try this same thing going out to September 20th for example and the numbers are way off
any help out here ? Thanks
Volt
Can you help answer these questions from other members on NexusFi?
For SD calculations on underlyings like the S&P 500 - which isn't a performance index but a simple
free-float cap-weighted price index - and its derivatives (like the SPY) you can choose between the
devil and the deep blue sea:
In the absence of payout research, the naive method is deriving the SD from past prices.
The error is obvious and raises with differences in earnings. Since most S&P constituents show
seasonalities, that method is second-rate (at best).
The theoretically "correct" method is estimating (or knowing) the payouts until the relevant date and
adjusting the SDs accordingly. Here the major problems arise from the necessary overhead and earnings
surprises, i.e. differences between the estimates and the actual values.
In September the SPY has an expected (e) consensus payout of $1.17e, in December $1.37e.
Past paypouts were e.g. $1.0821 in 9/2016 and $1.3289 in 12/2016.
These amounts don't fall into your lap at the pay dates but accrue over time and also must be
reflected in projected ETF and options prices.
yeah, I'm not so sure he understood the question or maybe doesn't use the TOS platform..... it's certainly possible that his mind thinks way behind the ordinary so I'm certainly not complaining but it just doesn't answer the question in a way I can understand it....anyone else want to take a crack at this one ?
I do remind myself, that don (theotrade) once said on this topic, that for index products use the option chain ex move, for equities use the analyze tab.
Something to do with different calculations on volatility in the analyze tab
To OP, have you looked at the calculation for how expected move is calculated? I think that should answer most of your question.
"Free markets work because they allow people to be lucky, thanks to aggressive trial and error, not by giving rewards or incentives for skill. The strategy is, then, to tinker as much as possible and try to collect as many Black Swan opportunities as you can"
I think there is a Jacob video in the TT archive that discusses the difference between 1SD and expected move. It depends on how the model was jiggered in the platform.
In short, expected move should be somewhat smaller than 1SD is the gist of it.
If even ToS cannot answer your question in form and content, a logical answer is pretty obvious, isn't it?
Normally vendors are using a combination of self-calculated data and data that they buy on addition.
Since noone (not even a retail customer) needs any help for the naive method 1, but the research for
method 2 is expensive, it is common in the industry to buy these data. And only by chance the results
of method 2 would match the naive results of method 1 ...
P.S.: You can get the same effect if you compare e.g. 2 naive methods like SD and ATR/ADR for the same period.
Both of them tell you something about the "expected" move / range, but only by chance they are matching.
