VSA for ThinkorSwim - ThinkOrSwim Programming | futures io social day trading
futures io futures trading


VSA for ThinkorSwim
Updated: Views / Replies:169,918 / 429
Created: by cbritton Attachments:131

Welcome to futures io.

(If you already have an account, login at the top of the page)

futures io is the largest futures trading community on the planet, with over 90,000 members. At futures io, our goal has always been and always will be to create a friendly, positive, forward-thinking community where members can openly share and discuss everything the world of trading has to offer. The community is one of the friendliest you will find on any subject, with members going out of their way to help others. Some of the primary differences between futures io and other trading sites revolve around the standards of our community. Those standards include a code of conduct for our members, as well as extremely high standards that govern which partners we do business with, and which products or services we recommend to our members.

At futures io, our focus is on quality education. No hype, gimmicks, or secret sauce. The truth is: trading is hard. To succeed, you need to surround yourself with the right support system, educational content, and trading mentors all of which you can find on futures io, utilizing our social trading environment.

With futures io, you can find honest trading reviews on brokers, trading rooms, indicator packages, trading strategies, and much more. Our trading review process is highly moderated to ensure that only genuine users are allowed, so you dont need to worry about fake reviews.

We are fundamentally different than most other trading sites:
  • We are here to help. Just let us know what you need.
  • We work extremely hard to keep things positive in our community.
  • We do not tolerate rude behavior, trolling, or vendors advertising in posts.
  • We firmly believe in and encourage sharing. The holy grail is within you, we can help you find it.
  • We expect our members to participate and become a part of the community. Help yourself by helping others.

You'll need to register in order to view the content of the threads and start contributing to our community.  It's free and simple.

-- Big Mike, Site Administrator

Reply
 131  
 
Thread Tools Search this Thread
 

VSA for ThinkorSwim

  #51 (permalink)
Elite Member
Atlanta, Georgia
 
Futures Experience: Intermediate
Platform: NT
Broker/Data: DDT
Favorite Futures: ZN, ZB
 
cbritton's Avatar
 
Posts: 224 since Mar 2010
Thanks: 152 given, 237 received


MAXX View Post
IS THERE CODING FOR TOS TO COUNT BARS. LIKE TS HAS. EACH BAR WILL HAVE ITS NUMBER ON THE BOTTOM OF CHART?
THANKS

Not that I'm aware of.

Regards,
-C

Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before defeat. - Sun Tzu
Reply With Quote
The following user says Thank You to cbritton for this post:
 
  #52 (permalink)
Just starting out...
Melbourn, Florida, United States
 
Futures Experience: Advanced
Platform: Thinkorswim
Favorite Futures: rut
 
Posts: 2 since Aug 2010
Thanks: 1 given, 1 received

This counts the bars. Probably better ways but this works.


#BAR_COUNTER
DECLARE LOWER;
REC ONE = (CLOSE / CLOSE);
REC ONEONE = (ONE + ONE[1])/2;
REC TOTALONES = TOTALSUM(ONEONE);
PLOT BAR_NUMBER = TOTALONES;
BAR_NUMBER.SETPAINTINGSTRATEGY(PAINTINGSTRATEGY.HISTOGRAM);
BAR_NUMBER.SETDEFAULTCOLOR(GETCOLOR(7));
BAR_NUMBER.SETLINEWEIGHT(5);

Reply With Quote
The following user says Thank You to joewolf68 for this post:
 
  #53 (permalink)
Trading for Fun
LA, CA
 
Futures Experience: Advanced
Platform: Infinity, IB, TOS
Favorite Futures: currency futures
 
Posts: 93 since Jul 2010
Thanks: 2 given, 24 received

Progress report


I am continuing to watch the upThrust bars and their confirmation bars. I am still uncomfortable with the fact that many of them don't look like the Gravestone Dojis they're supposed to resemble. I've noticed, however, that in almost all cases if I mentally combine an identified upThrust that doesn't look like a Gravestone with 2 to 5 previous bars, a Gravestone Doji would have appeared on a larger time scale. In order to identify true Gravestones I've added the following code identified by a white square:

rec isGraveDojiBar = (spread > avgSpread) && (open == low) && (close == low);

This does indeed find real Gravestones, as few and far between as they might be.

A couple color considerations:

I don't like the fact that there are 3 different conditions identified by a blue square at the top. I have started modifying the colors displayed in order to differentiate these conditions in a way that makes sense. My first change is that pseudoUpthrusts and their confirmation are now identified by an Orange square and triangle instead of blue. This makes it much easier to recognize them when they occur especially because I also changed the color behind their text description to Orange. So far, so good.

I noticed that (152,251,152) is used for a couple of the trend colors. I looked at a web-safe color chart and don't find those numbers there. This is probably not a big deal, but I think the colors should be (153,255,153). 153 is equal to Hex 99 which is a common value in web-safe colors. Btw, I've used (255,102,102) for my Orange.

Reply With Quote
 
  #54 (permalink)
Just starting out...
Melbourn, Florida, United States
 
Futures Experience: Advanced
Platform: Thinkorswim
Favorite Futures: rut
 
Posts: 2 since Aug 2010
Thanks: 1 given, 1 received

On another topic I found a possible bug in the code for noSupplyBar. The code for noDemandBar fits pretty well with the description of No Demand and of a No Demand Up-Bar in the glossary of Williams' first book Master the Markets. The study defines it as an Up bar with narrow spread closing down on volume that has been decreasing over a 2 bar period. Williams' book doesn't define it quite as explicitly but the study's code seems to be a good fit.

def noDemandBar = (isUpBar[0] && isNarrowSpreadBar[0] && isTwoDaysLowVol && isDownCloseBar);

However, in the code for noSupplyBar I think that the last term should be isUpCloseBar not isDownCloseBar. No Supply implies lack of selling pressure which would be more evident if the bar closes up not down.

def noSupplyBar = (isDownBar[0] && isNarrowSpreadBar[0] && isTwoDaysLowVol && isDownCloseBar);


First let me say Thanks for doing all this. You guys are awesome. I agree here that it should be changed to isUpCloseBar.

Reply With Quote
 
  #55 (permalink)
Elite Member
Atlanta, Georgia
 
Futures Experience: Intermediate
Platform: NT
Broker/Data: DDT
Favorite Futures: ZN, ZB
 
cbritton's Avatar
 
Posts: 224 since Mar 2010
Thanks: 152 given, 237 received


snowcloud View Post
I am continuing to watch the upThrust bars and their confirmation bars. I am still uncomfortable with the fact that many of them don't look like the Gravestone Dojis they're supposed to resemble. I've noticed, however, that in almost all cases if I mentally combine an identified upThrust that doesn't look like a Gravestone with 2 to 5 previous bars, a Gravestone Doji would have appeared on a larger time scale. In order to identify true Gravestones I've added the following code identified by a white square:

rec isGraveDojiBar = (spread > avgSpread) && (open == low) && (close == low);

This does indeed find real Gravestones, as few and far between as they might be.

Maybe open = low is too stringent? Where does Williams mention that the up thrust bar must be a gravestone doji?


snowcloud View Post

A couple color considerations:

I don't like the fact that there are 3 different conditions identified by a blue square at the top. I have started modifying the colors displayed in order to differentiate these conditions in a way that makes sense. My first change is that pseudoUpthrusts and their confirmation are now identified by an Orange square and triangle instead of blue. This makes it much easier to recognize them when they occur especially because I also changed the color behind their text description to Orange. So far, so good.

I noticed that (152,251,152) is used for a couple of the trend colors. I looked at a web-safe color chart and don't find those numbers there. This is probably not a big deal, but I think the colors should be (153,255,153). 153 is equal to Hex 99 which is a common value in web-safe colors. Btw, I've used (255,102,102) for my Orange.

The colors were a bit odd in the NT version and I tried to match them as closely as possible. I agree that there are too many similar conditions for the same color, but I did not want to impose those changes since the port was supposed to be as close as possible.

Regards,
-C

Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before defeat. - Sun Tzu
Reply With Quote
 
  #56 (permalink)
Trading for Fun
LA, CA
 
Futures Experience: Advanced
Platform: Infinity, IB, TOS
Favorite Futures: currency futures
 
Posts: 93 since Jul 2010
Thanks: 2 given, 24 received


joewolf68 View Post
On another topic I found a possible bug in the code for noSupplyBar. The code for noDemandBar fits pretty well with the description of No Demand and of a No Demand Up-Bar in the glossary of Williams' first book Master the Markets. The study defines it as an Up bar with narrow spread closing down on volume that has been decreasing over a 2 bar period. Williams' book doesn't define it quite as explicitly but the study's code seems to be a good fit.

def noDemandBar = (isUpBar[0] && isNarrowSpreadBar[0] && isTwoDaysLowVol && isDownCloseBar);

However, in the code for noSupplyBar I think that the last term should be isUpCloseBar not isDownCloseBar. No Supply implies lack of selling pressure which would be more evident if the bar closes up not down.

def noSupplyBar = (isDownBar[0] && isNarrowSpreadBar[0] && isTwoDaysLowVol && isDownCloseBar);


First let me say Thanks for doing all this. You guys are awesome. I agree here that it should be changed to isUpCloseBar.

I made the change to UpCloseBar and it seems to be working fine. Thanks for the thanks!

Reply With Quote
 
  #57 (permalink)
Trading for Fun
LA, CA
 
Futures Experience: Advanced
Platform: Infinity, IB, TOS
Favorite Futures: currency futures
 
Posts: 93 since Jul 2010
Thanks: 2 given, 24 received


cbritton View Post
Maybe open = low is too stringent? Where does Williams mention that the up thrust bar must be a gravestone doji?



The colors were a bit odd in the NT version and I tried to match them as closely as possible. I agree that there are too many similar conditions for the same color, but I did not want to impose those changes since the port was supposed to be as close as possible.

Regards,
-C

Williams doesn't specifically say that an upThrust needs to be a Gravestone Doji, but he does say on p. 111 that it does "...close on the low" which is a characteristic of Gravestones. I agree that open == low is probably too stringent but I wanted to see how this change would manifest in daily use and how it might interact with the upThrust code already in place. Specifically, I want to see if any of the Gravestone Dojis it finds qualify as upThrusts. I put the white square way up above the bar so there will be room for other indicators that might appear above the bar and below the GD white square. Ultimately, it'll probably be best to simply test that the candle's real body is some fraction of the upper wick and that the lower wick is really small if there at all.

I agree that the colors in the NT version are a bit odd, actually more than a bit in my opinion. Little by little, I plan to make changes so that there is an intuitive relationship between the colors and the significance of each VSA label. So far I am really digging my orange pseudo-upThrusts. In one case today a series of them led up to a red upThrust square and triangle confirmation and the EUR/USD price did indeed decline thereafter.


Last edited by snowcloud; August 17th, 2010 at 09:42 PM.
Reply With Quote
 
  #58 (permalink)
Trading for Fun
LA, CA
 
Futures Experience: Advanced
Platform: Infinity, IB, TOS
Favorite Futures: currency futures
 
Posts: 93 since Jul 2010
Thanks: 2 given, 24 received

PseudoUpThrust Hypothesis

I am noticing that when taken in combination with its previous bar a PseudoUpThrustBar can come closer to satisfying Williams' UpThrust criteria than many of the reported UpThrustBars do. Case in point on the EUR/USD at 11:50 AM ET today on two 2min candles. The first: O 2876 H 2882 L 2876 C 2880; The second: O 2880 H 2881 L 2876 C 2876 [add "1." prefix to all values]. The first candle had no identification, the second was identified as a PseudoUpThrust. Together they make a perfect Gravestone Doji of O 2876 H 2882 L 2876 C 2876. The next candle was a PseudoUpThrustConfirmation and the price did decline from there to a low of 2862 six 2min bars later.

I think that the reason for this phenomenon is that the criteria for a PseudoUpThrust requires that the previous bar has to be Up on above average volume which is how many traditional upThrusts in the Williams sense start out. Traditionally they then drop back to the lows of the bar which in this case happens in the next bar identified as a PseudoUpThrust. The code for PseudoUpThrustBars filters out UpThrustBars as defined in the study as well as wideSpreadBars (which is redundant because the criteria for an upThrustBar requires that bar to be a WideSpreadBar therefore !isUpThrustBar[0] filters wideSpreadBars out).

I'll keep watching for confirmation of my hypothesis. (Btw I was away from my computer when these 2 bars occurred so I didn't take this nice little trade. Wish I had)!

rec isPseudoUpThrustBar = (isUpBar[1] && (volume[1] > aboveAvgVolfactor * sAvgVolume[0]) && isDownBar[0] && isDownCloseBar && !isWideSpreadBar[0] && !isUpThrustBar[0]);
# hutcond
def pseudoUpThrustConfirmation = (isPseudoUpThrustBar[1] && isDownBar[0] && isDownCloseBar && !isUpThrustBar[0]);

Reply With Quote
 
  #59 (permalink)
Trading for Profit
Chicago + Illinois/USA
 
Futures Experience: Beginner
Platform: ThinkOrSwim
Favorite Futures: Stock
 
StockJock's Avatar
 
Posts: 256 since Aug 2010
Thanks: 15 given, 148 received

Better Volume Indicator

I just thought I'd let you guys know that someone has translated the Better Volume Indicator which is also a VSA type indicator. See attachments. Would anyone be willing to try to translate one of the Point And Figure indicators that I have attached? Perticularly the XO.txt? They are in MetaTrader 4 language.

Attached Files
Register to download File Type: txt TS_BetterVolume_Indicator.txt (7.0 KB, 119 views)
Register to download File Type: txt FXI_Point&Figure-Adv.txt (39.2 KB, 55 views)
Register to download File Type: txt PnF EasyLanguage code.txt (1.4 KB, 44 views)
Register to download File Type: txt X_O_serg153xo.txt (4.7 KB, 40 views)
Register to download File Type: txt XO.txt (3.9 KB, 40 views)
Register to download File Type: txt Point_and_Figure_Simulator.txt (1.4 KB, 49 views)
Reply With Quote
The following user says Thank You to StockJock for this post:
 
  #60 (permalink)
Elite Member
Atlanta, Georgia
 
Futures Experience: Intermediate
Platform: NT
Broker/Data: DDT
Favorite Futures: ZN, ZB
 
cbritton's Avatar
 
Posts: 224 since Mar 2010
Thanks: 152 given, 237 received



StockJock View Post
I just thought I'd let you guys know that someone has translated the Better Volume Indicator which is also a VSA type indicator. See attachments. Would anyone be willing to try to translate one of the Point And Figure indicators that I have attached? Perticularly the XO.txt? They are in MetaTrader 4 language.


Thanks for the BetterVolume indicator. Can you add this to the ThinkorSwim download section? It would be a nice addition.

I did a quick pass on the easy language version of the point and figure. I will start a new thread for this since it's off topic on this one. Here's the thread: https://futures.io/everything-else-programming/5129-point-figure-tos-thinkorswim-trading-platform.html#post56982

Regards,
-C

Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before defeat. - Sun Tzu
Reply With Quote

Reply



futures io > > > > > VSA for ThinkorSwim

Thread Tools Search this Thread
Search this Thread:

Advanced Search



Upcoming Webinars and Events (4:30PM ET unless noted)

Jigsaw Trading: TBA

Elite only

FuturesTrader71: TBA

Elite only

NinjaTrader: TBA

Jan 18

RandBots: TBA

Jan 23

GFF Brokers & CME Group: Futures & Bitcoin

Elite only

Adam Grimes: TBA

Elite only

Ran Aroussi: TBA

Elite only
     

Similar Threads
Thread Thread Starter Forum Replies Last Post
Volume Spread Analysis (VSA) slumlord Traders Hideout 57 December 6th, 2017 01:19 AM
VSA indicator for MT4 sam1197 MetaTrader 12 December 21st, 2015 08:15 PM
VSA alexav Russian Traders 5 December 17th, 2012 05:03 AM
VSA in MC? TonyB MultiCharts 10 May 28th, 2011 11:37 AM


All times are GMT -4. The time now is 03:46 PM.

Copyright © 2017 by futures io, s.a., Av Ricardo J. Alfaro, Century Tower, Panama, +507 833-9432, info@futures.io
All information is for educational use only and is not investment advice.
There is a substantial risk of loss in trading commodity futures, stocks, options and foreign exchange products. Past performance is not indicative of future results.
no new posts
Page generated 2017-12-17 in 0.15 seconds with 20 queries on phoenix via your IP 107.20.115.174