here another "How-to-search-on-futures.io (formerly BMT)-Workshop" :
what you did was searching in the downloads. a very good idea ! but only the first out of 2 possible ways.
the second search-possiblity would be to search in our attachments (those things wich are attached in all the postings)
You alsways should try both cause the stuff you are looking for maybe in downloads OR in posts as attachments - thats how it is.
look at my pics how to do it - the first shows you how + the second shows you what you can find there
Please register on futures.io to view futures trading content such as post attachment(s), image(s), and screenshot(s).
hope it works for you - let me know !
The following user says Thank You to max-td for this post:
I created the BETA strategy for education purposes, ie visualizing some of the signals which meet the entry requirements and not for auto-trading. No plan to polish the BETA strategy further to make it a workable one.
Good Trading is about Trading Right!
Want What the Market Wants!
Trade With the Trend!
The following user says Thank You to wgreenie for this post:
I erroneously posted my work on a strategy for Perry's rules in Perry's thread. So, I am posting the files here at the request of Big Mike.
You see 4 files available for download.
The ones labelled as PerryStrat are the actual strategy. You can run the strategy either from Strategy Analyzer or from a chart without Chart Trader on it. However, if you run it from a chart you must be connected to your data provider. I like running from a chart when I'm doing back of the envelope analysis and don't need all the details provided by Strategy Analyzer. Running from a chart is faster. You will see you get a basic PNL report on the chart giving you a quick and dirty report of how well your strategy is performing.
Just an editorial comment about the strategy. You will find that as good as Perry's rules are for discretionary trading they are in no way a mechanical system. The strategy I wrote is a very quick way to look at the entries for the purpose of education. In other words, taking every entry as the strategy does is not profitable.
You also see files labelled DM3PlusSignals. Thes 2 files contain the indicator that displays entry signals for use by themselves. I like this indicator because it shows the entries without me having to evaluate every entry manually. I still look at the indicator to make sure it is reporting correctly. So, this indicator is for manual trading.
Good luck and hope you like them.
The following 15 users say Thank You to MWinfrey for this post:
TYVM for sharing indicator and strategy for Perry trading system.
I incorporated DMPlusSignals into Perry template and tested it on 3,4,6 and 8 Range respectively. 3 Range appeared to have more inaccurate markings of Setup bars than I could count in a sample of 10 calendar days; while no mistakes found on 4,6 and 8 Range. Is the mistake caused by NT?
I'm not programmer; I struggle to learn to read NT Script. It seems you didn't include Perry Trading Method 2 into your coding. Would you consider to add Method 2 to DMPlusSignals to broaden the effectiveness of the indicator you created? TIA!
Using DM Plus Signals...2 things to note:
1. Mine was crashing (would not save the workspace) until I upgraded to the latest NT7 version.
2. The signals appear late. I love the indicator! So, would you consider webhuddle.com with me, no software to download, I'll just send you the link, and show you what I think. Could be wrong, and perhaps one of the other indicators just wasn't there at that moment (i.e. ADX value), but the horizontal bars appear late.
You're welcome. I have no idea why the your 3 range signals are wrong. Mine look right to me so not sure what could be happening on your computer. Can you provide a screenshot? Not that I can do anything about it but I would like to see what you're talking about.
You're right. I only coded method 1. Really didn't have any intention of coding method 2 but now that you ask, maybe I will...I'll let you know. Not promising but I'll take a look.
The following user says Thank You to MWinfrey for this post: