NexusFi: Find Your Edge


Home Menu

 





VSA for ThinkorSwim


Discussion in ThinkOrSwim

Updated
      Top Posters
    1. looks_one snowcloud with 93 posts (25 thanks)
    2. looks_two StockJock with 91 posts (27 thanks)
    3. looks_3 cbritton with 37 posts (71 thanks)
    4. looks_4 swimtrader with 22 posts (19 thanks)
      Best Posters
    1. looks_one Hornblower with 2.3 thanks per post
    2. looks_two cbritton with 1.9 thanks per post
    3. looks_3 StockJock with 0.3 thanks per post
    4. looks_4 snowcloud with 0.3 thanks per post
    1. trending_up 309,693 views
    2. thumb_up 223 thanks given
    3. group 86 followers
    1. forum 434 posts
    2. attach_file 131 attachments




 
Search this Thread

VSA for ThinkorSwim

  #51 (permalink)
 
cbritton's Avatar
 cbritton 
Atlanta, Georgia
 
Experience: Intermediate
Platform: NT
Broker: DDT
Trading: ZN, ZB
Posts: 230 since Mar 2010
Thanks Given: 152
Thanks Received: 256


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
Started this thread Reply With Quote
Thanked by:

Can you help answer these questions
from other members on NexusFi?
Exit Strategy
NinjaTrader
How to apply profiles
Traders Hideout
NT7 Indicator Script Troubleshooting - Camarilla Pivots
NinjaTrader
Better Renko Gaps
The Elite Circle
PowerLanguage & EasyLanguage. How to get the platfor …
EasyLanguage Programming
 
Best Threads (Most Thanked)
in the last 7 days on NexusFi
Spoo-nalysis ES e-mini futures S&P 500
29 thanks
Just another trading journal: PA, Wyckoff & Trends
25 thanks
Tao te Trade: way of the WLD
24 thanks
Bigger Wins or Fewer Losses?
21 thanks
GFIs1 1 DAX trade per day journal
16 thanks
  #52 (permalink)
joewolf68
Melbourn, Florida, United States
 
Posts: 2 since Aug 2010
Thanks Given: 1
Thanks Received: 1

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
Thanked by:
  #53 (permalink)
snowcloud
LA, CA
 
Posts: 93 since Jul 2010
Thanks Given: 2
Thanks Received: 25


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)
joewolf68
Melbourn, Florida, United States
 
Posts: 2 since Aug 2010
Thanks Given: 1
Thanks Received: 1

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)
 
cbritton's Avatar
 cbritton 
Atlanta, Georgia
 
Experience: Intermediate
Platform: NT
Broker: DDT
Trading: ZN, ZB
Posts: 230 since Mar 2010
Thanks Given: 152
Thanks Received: 256


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
Started this thread Reply With Quote
  #56 (permalink)
snowcloud
LA, CA
 
Posts: 93 since Jul 2010
Thanks Given: 2
Thanks Received: 25


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)
snowcloud
LA, CA
 
Posts: 93 since Jul 2010
Thanks Given: 2
Thanks Received: 25


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.

Reply With Quote
  #58 (permalink)
snowcloud
LA, CA
 
Posts: 93 since Jul 2010
Thanks Given: 2
Thanks Received: 25

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)
StockJock
Chicago + Illinois/USA
 
Posts: 256 since Aug 2010
Thanks Given: 15
Thanks Received: 154

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
Elite Membership required to download: TS_BetterVolume_Indicator.txt
Elite Membership required to download: FXI_Point&Figure-Adv.txt
Elite Membership required to download: PnF EasyLanguage code.txt
Elite Membership required to download: X_O_serg153xo.txt
Elite Membership required to download: XO.txt
Elite Membership required to download: Point_and_Figure_Simulator.txt
Reply With Quote
Thanked by:
  #60 (permalink)
 
cbritton's Avatar
 cbritton 
Atlanta, Georgia
 
Experience: Intermediate
Platform: NT
Broker: DDT
Trading: ZN, ZB
Posts: 230 since Mar 2010
Thanks Given: 152
Thanks Received: 256



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:

Regards,
-C

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




Last Updated on May 21, 2023


© 2024 NexusFi™, s.a., All Rights Reserved.
Av Ricardo J. Alfaro, Century Tower, Panama City, Panama, Ph: +507 833-9432 (Panama and Intl), +1 888-312-3001 (USA and Canada)
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.
About Us - Contact Us - Site Rules, Acceptable Use, and Terms and Conditions - Privacy Policy - Downloads - Top
no new posts