Optimizing TTM Squeeze Strategy
Author: lanatmwan
Creation Date: 12/21/2017 6:24 PM
profile picture

lanatmwan

#1
I am new to wealthscript and the TTM squeeze (by John Carter) but I'm interested in learning both. In wealth lab I downloaded a strategy called "double-band squeeze system" which I believe is the TTM squeeze strategy. In the community extensions there is a strategy that definitely bills itself as the TTM strategy: http://www2.wealth-lab.com/WL5WIKI/Squeeze.ashx

In both there are a number of hard coded values that I think could be made into StrategyParameter in order to support optimization. I have made the changes but I want to know what the process is for uploading them for code review and release to the community?
profile picture

Eugene

#2
Thank you for your helping hand.

QUOTE:
In wealth lab I downloaded a strategy called "double-band squeeze system" which I believe is the TTM squeeze strategy.

1. It might be a usability improvement. However, I think that there has to be a bigger reason for uploading a strategy revision than just adding Straps (strategy parameters). As a rule we do it when discovering a code bug or making substantial (i.e. not cosmetic) improvement to the logic.

QUOTE:
In the community extensions there is a strategy that definitely bills itself as the TTM strategy: http://www2.wealth-lab.com/WL5WIKI/Squeeze.ashx

2. The Wiki example code lacks Straps just to stay terse i.e. for the purpose of illustrating the indicator's syntax.

P.S. Let me add for anybody interested in supporting optimization in a strategy that doesn't do it: it's described in a tutorial in the WealthScript Programming Guide > Programming Trading Strategies > Strategy Parameters.

Thanks again.
profile picture

lanatmwan

#3
I can see your point on terseness. However, I would disagree with the notion that Straps are cosmetic. Its a few lines of code that automatically connects a script to a huge selling point of the platform. Do you have a rough estimate of how many people actively use/dev wealthscripts? I'm curious whether there would be enough of a development community to warrant a github repository where it was easy for people to branch off/contribute changes as needed?
profile picture

Eugene

#4
QUOTE:
However, I would disagree with the notion that Straps are cosmetic. Its a few lines of code that automatically connects a script to a huge selling point of the platform.

There are three hundred strategies to which every trader might offer an improvement. If so, we technicians would be swamped in reviewing and approving those minor revisions (like the addition of Straps that you're proposing). We're interested in the first place in publishing new Strategies (not just strategy variations), and in changes that fix bugs in existing Strategy code. For now, please consider this as a DIY excercise - a minor effort for anyone interested.

QUOTE:
I'm curious whether there would be enough of a development community to warrant a github repository where it was easy for people to branch off/contribute changes as needed?

Though an interesting feature but a GitHub repository will not happen for many reasons: tiny user base, considerable development effort, hard to couple with the application's built-in Strategy download feature, security concerns etc. And the usability of Github is not the "Wealth-Lab way" (read: tiny user base).

Amazing but nothing new under the sun. 10 years ago, the first generation of wealth-lab.com was hosting ChartScript code to be run on the website. There you could see a horde of variations to the original script which frequently was just a change to its parameters. Been there, done that, and definitely not where we're going again.
profile picture

superticker

#5
QUOTE:
2. The Wiki example code lacks Straps just to stay terse
I like the idea of the wiki example http://www2.wealth-lab.com/WL5WIKI/Squeeze.ashx staying terse. But the example needs to have "closure" so everything mentioned in its discussion is also reflected in its code example (or some external link). The wiki mentions a smoothed momentum histogram (with green, lime, red, and magenta bars), but the wiki code example excludes this. Can we make the two consistent by including the code for the discussed histogram?

Also, the link cited in the wiki is broken.

I just watched John Carter's YouTube presentation about TTM Squeeze with great interest. https://www.youtube.com/watch?v=lbmUfauTGkU
profile picture

Eugene

#6
QUOTE:
Also, the link cited in the wiki is broken.

It happens all the time since the link points to an external resource. Thanks for the link, added it.

QUOTE:
But the example needs to have "closure" so everything mentioned in its discussion is also reflected in its code example (or some external link)

Good point. I've deleted the discussion and left only the key points about the indicator's idea. Everyone interested is welcome to do their own search for external resources.