Great strategies. Thank you! As Tom O'Brien put it over two decades ago in his book Timing the Trade, "Volume is cause, Price is effect." It's like a compass that points you in the right direction.
Again, another great video which give powerful exploration idea to scanner condition in such a short time which beat all other programming course hand down... 👍👍👍
When you created the options scan and used the study in options hacker, that study is scanning for options or the stocks satisfying conditions within the study? For instance, If i am interested in finding options whose premiums are rising for the last three consecutive periods and the volume is also rising, will it find various option strikes meeting these conditions?
holy s#$^ that was a 50 minute roller coaster ride of information, yes 50 minutes cause I pause numerous times. I love a challenge. I need to join volatility box. argh just have to justify the investment. thanks for the info though.
Hi Wilson - glad you liked the video! I think you're referring to the Fibonacci Retracements (free tool inside of TOS), with colors customized for each extension (right click --> edit properties --> adjust colors).
You would need to change the custom quote's timeframe to be a 1m, instead of D. However, the 1m is more likely to give you false / early signals, esp. with any lag from volatility where the condition may have been true, but is not any longer. I've found larger time frames generally work better.
Glad you liked it, Sam. For a % change from the previous day's close price, you should be able to use logic similar to the scan we built here, and compare the closing price to yesterday's close (ie. close[1]), instead of the 50 SMA. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-2RPzLoHqrwQ.html
hello how you doing great video. question regarding the 3rd scan option scan. when i hit scan weird options pop up. not the underlying. for example /loj22c100
Awesome, awesome video. Much appreciated. When I run the relvolstdev scan it doesn't pick up on a symbol (RIOT) that shows it's above the 4 stdev limit on its chart. I've got the Vol and Bid criteria in place, as well. What am I missing?
Thanks for the kind words. One thing that comes to mind which you may want to double-check is the "Scan in" symbol group at the top of your scan tab. Whatever list is selected there, you'll need to verify that RIOT is a symbol inside of that.
@@TOSIndicators Gone through the video, I've got all my parameters correct and I'm in either All Stocks or All Optionable. I've also scanned several time frames. I know this is getting down to one-on-one here, but if you're cool with it, could you do a search with your scan parameters and see if your scan catches RIOT and/or NAOV (both of which have had several hits above 3 StDev recently)? I'm not getting those on any scan I try.
RIOT shows up on my scans, when looking for a greater than or equal to 3 SD volume, over the past 20 days. plot signal = Sum(RelativeVolumeStDev().relvol >= 3, 20);
@@TOSIndicators That does work for me, as well. I was using "plot signal = Sum(volumeCondition, 10) >=2;", or numeric variations of that, that you showed in the video. On a side note, how do you view the next series of scans (ie, 51-100 of 350) without going to a higher number shown, like 500 for example?
I'm also noticing that "plot signal = Sum(RelativeVolumeStDev().relvol >= 3, 20);" yields a lot more results than "plot signal = Sum(volumeCondition, 20) >=3;". As this is all new to me, are you able to help walk me through why the large difference here ("def volumeCondition = RelativeVolumeStDev(50) .RelVol >=3;" and other search parameters are the same for both searches)?
Hi Derek - I'm not aware of a way to segregate buy vs. sell volume using thinkScript code. I imagine the OnBalanceVolume indicator would be a good place to start, if that fits the bill for what you're looking for.
