The Simple System

I am going to take a wild guess and say that you completely failed to read all of the posts in this thread. If you did you would have read where their was acknowledgement that the program has problems and that there were three programmers currently working on fixing these problems and look forward to introducing a new and improved version.

If you want to offer advice, then follow the rules of Pip2 and contact him by PM. If you want to assist in programming, do the same. If you want to post negativity, don't.

Ok, sorry me for negativity - i don't wanna it, sorry again.
My target not offend someone - my opinion is T3MA not so good, like look at first sight...

See picture... Vertical lines - after thats candles clothes we may talking about turn of T3MA and on open next candle (arrow) we may enter...

But we may know it and with TriggerLines...

Now add STOCH-ALARM-3x - Pic 2 - very early enties, but in that points we don't know about turn of T3MA. If you wanna see right place of arrows do some change in indicator:
replace:
if(xdown==1){dnbuffer[cnt+1]=High[cnt+1]+(sep*Point);}
if(xup==1){upbuffer[cnt+1]=Low[cnt+1]-(sep*Point);}

insert that:
if(xdown==1){dnbuffer[cnt]=High[cnt]+(sep*Point);}
if(xup==1){upbuffer[cnt]=Low[cnt]-(sep*Point);}
(see pic 3)

too not so bad, but and not so good...
---------------------------------------------------------------------
And... One indicator, like thats, not right solution - need more filters and Simple System automatic transformed in Not So Simple....

Some times ago i'm programmed systems like thats and they don't have profit on "long" history...

If you have questions i will try answer and may be help, if i can...

Hi Oleg77, thanks for contributing, even in a negative way but I think you really want to help. Yes, its true I am not a programmer by profession but this is not about me. I think its better to try and maybe succeed or fail than never to have tried at all.

So I will continue trying until I achieve a measure of success. Success is measured by dollars in the BANK, and not errors etc in someones coding. I take it your first language is not English but I applaud you for trying to convey some form of information which might be beneficial to all.

Welcome Oleg77 to this thread and join isto and jam and pipsahoy and WHtenn and others who have decided to help in this effort. Like a seed that is not a plant but if you nuture it it will bear fruit. The fruits we are looking for is dollars.

If you want oleg77 I can send you what jam and isto have contributed and you can make your own changes to it. What say you? OK?

To others who are inclined to think like Oleg77, I extend to you the same offer of positive constructive criticism.

Cheers.

Pip2

Oleg77,

Thanks for pointing out the flaw in the indicator, however, I've already addressed this 2 revisions ago with the modified indicator that Snobol1 received last week and is currently testing. There were also numerous logic flaws that were corrected, resulting in a more stable indicator. Among the many issues addressed and corrected:

- Signal will fire on Bar(0) open now and stay anchored.
- Elimination of "ghost" arrows.
- Corrected problem with Buy/Sell arrows anchored on the same bar.
- Analyze signals based on the number of bars on the chart, not just
the 500 so you can better track long-term historical performance of
the signals.
- Chart will auto-refresh now to correct the problem AubreyCraller
and others have experienced. Programming code has been added to
support this feature. No manual refresh will be required.

If you wish to join the development team, you're encouraged to do so. It's always good to have additional help and a fresh set of experienced eyes to analyze a problem. Neither Snobol1 nor WHTenn have ever claimed to be programmers, which is why ISTO and I stepped in. If you care to join the effort, you're most welcome. The bottom line is making a money making system in the form of an EA - sometimes that takes hard work and volunteerism, whether it be on the trading, testing, and/or development front. All we've been asking along the way is for others to keep the conversation contructive, and if you spot any bugs to point them out, as you did, so the development team can address them - it may take a few tries and more testing before a particular problem is addressed - so patience is another key ingredient required around here.

My goal is to get the indicator to anchor signals correctly on the M1 charts, which are the most volatile. I'm not expecting it to be profitable on M1, just be able to generate accurate signals.

Thanks again for your contributions!

Jam

Hello Everyone on the Simple System Development team,

May i just express how fantastic help and support you have given to the world of Forex trading. I am really looking forward to the new release, could you give me an idea when this will be released?

Regards,

Gareth Williams

Hi garethw, the revisions jam's post above relate to is in my hands and I must thank jam for pointing in detail what he and others have accomplished. No indicator is perfect, but we will try to approach that point.

Yes, some more filtering may be required, but my philosophy is that any added filtering will be transparent to the user. All you will have is ONE, good solid reliable indicator which has many of the strengths of other indicators built right in. That way, the simple system will continue to be simple to the user, but the underlying code could be very complex. But since the code is transparent to the user, it remains a simple system.

Now Oleg77 has offered to help, that's great. I think his contributions will be worthwhile. So while Oleg is changing and testing there's no reason why the first issue of TSS cannot be made as soon as isto finishes combining his and jam's versions. When Oleg is finished there could be another release. As to timing of all this? This coming week will be used up for isto's work so the earliest would be the week after that. If this schedule changes I'll post what's going on.

In the meantime the 3x version is still usable with all its flaws now that we know what they are.

Cheers.

Happy pipping.

Pip2

plz hurry up I just can't wait

I want to thanks to all the developers of Symple System for your effort and your spirit to help each other in this thread / forum. Wish You all the best !!!

And while we are waiting for the new version to come, let's see and forward test what the 3x version can do for us.

Best Regards,
Bom-Bom

Snobol, Jam, Isto and Oleg, Is this the problem you guys try to resolve?

Please have a look a strange picture on this chart (the ellipse highlighted). The left one is the old chart, the right one is the new chart I loaded to the platform. When I took the picture, both running on the same time. Only the time it was loaded to Metatrader is different.

Is it because the refresh problem you mentioned before?

Hope you guys working on the solution on this while forward test the new indicator this week.



Thank you.

Hi,

I'm a complete newbie and this is my first post, but I'm following
this thread with great interest and would like to be helpful if I can.
(I'm still figuring out how to spell "Forex", and I'm a hacker, not a
programmer so if I'm way off base, please don't flame me to bad.

It occurs to me that since the Bar(0) arrows turn on and off (by design)
while the candle is forming, perhaps there are some glitches in transmitting
the final status when it becomes Bar(1), (one bar older in time).

Could the programmers try using either a different color for the Bar(0)
arrows, or perhaps a different shape? That way if you see the old
color/shape for anything else besides the current candle, then you know
it's a false signal that should disappear if you reload the whole timeframe.

For the opposite problem where you are looking at a chart and don't
see an old arrow where there should be -- which a reload ends up showing --
then perhaps the code needs a more definitive section to specifically
paint the Bar(1+) arrow once the candle is fully formed? (Sorry if it's
already there in the code, 'cause I am just beginning to learn how to
read/hack this MQL4 stuff).

Thanks, and I'm looking forward to working with this new promising
indicator/system!

pips4life

To Bom-Bom and pips4life, et al thanks for your comments. BB, I think the extra arrow in the left chart above is an old arrow which was not erased for some reason. Its quite simple, the arrows appear at the apices ( apex plural) of the T3MA(4,1.5) curve. To prove or disprove an arrow, put a T3MA(4,1.5) indicator on your chart and look at where the line forms a peak /\ or a valley \/. At each apex there should be an arrow at the apex if you are using STOCH-ALARM3x. If you are using another version the arrow is moved one bar to the right of an apex. So if an arrow is not in such a location, chances are it is a rogue arrow from a previous attachment of the indicator that was not erased.

Jam has included a statement to force refreshing of the chart on tics and when changes are made. His contribution is in the hands of isto who is combining both efforts into one.

Oleg77 has sent me his contribution and am also testing it. Oleg sent a clock indicator which is quite nice. It gives a countdown in minutes and seconds to end (close) of bar 0, and is usable on any timeframe. Oleg has also removed the extra lines in T3MA indicator so now you can use any background colour for your charts not just black.

I think I'll attach the clock and T3MAv3.1 in another post because they can be used right now since no more significant changes are contemplated. And that will give us time to be familiar with them.

Cheers for now.

Pip2

Bom-Bom & Pips4Life,

Pips4Life...don't worry about being flamed - it won't happen with me since I and others have better things to do with my time... Bar(0) arrow should no longer change since analysis is based on a different method, so arrow will be anchored at Bar(0) open. Changing the color of Bar(0) arrow and direction will just cause enormous confusion and that's what we're purposely trying to stay away from. We're trying to keep things very simple here, hence the name of the thread. Ultimately it really should come down to taking Buy or Sell at Bar(0) Open, so as not to cloud judgment.

Those are some of the issues that are being addressed right now. Stay tuned...

EDIT: Snobol1, the chart refresh function was something that ISTO had already incorporated in the version I modified, so he gets the credit for that.

Jam

Dear Colleagues,

I appreciate very much your efforts to make life easier.
Could you say when are you going to release the latest version of this miracle?

thanks a lot.

Serggry

EDIT: Snobol1, the chart refresh function was something that ISTO had already incorporated in the version I modified, so he gets the credit for that.

Jam
OK jam, thanks for reinforcing my points. Sorry, I thought you were the on who added the redraw function. Isto I hope you're not upset with me for this error. There's so much going on its easy to give the wrong person credit, but I'll try not to.

Oleg77 has done a bit to T3MA and so has jam who has found and fixed a flaw in tthe logic of this basic indicator. Thanks jam. As a result I have added some credits to the banner of this indicator, and renamed so that there will be no confusion with the flawed version which should not be used any more.

Isto is the man, he is working on combining the two versions. Now Oleg77 has had some input and I'll have to sort that out with isto. This will not be a miracle, far from it, but I hope we could converge on something which could beat the odds.

I have attached the new T3... indicator which is now called OT3MAv3_1, that's the one with all problems fixed until another one is found. I'll also attach Oleg77's CandleTime indicator which gives a countdown to the close of current candle, its neat!

Cheers,

Pip2

Est time of posting isto's final product is some time next week.

EDIT. Cosmetic change to OT3MAv3_1 sub-window name changed to reflect name change.

Snobol, if the T3MA had been revised, then should we change the code in "STOCH-ALARM-3X.mq4" / "STOCH-ALARM-3X_withMail.mq4" :



to this one (because of the new indicator : OT3MAv3_1 ) :



Thanks !!

Best Regards,
Bom2

Snobol1,

You forgot to post the alarm indicator that I submitted in the set, which should encompass the changes I submitted along with those ISTO and Oleg77 had made. There should now be 3 indicators in the set, namely:

- OT3MAV3_1 (Revised T3MA Indicator)
- TSSV3 (Revised Alarm)
- CandleTime

Bom-Bom: That STOCH-ALARM-3x_withMail is obsolete since I and the other developers made numerous changes to it.

Snobol1: I would strongly suggest renaming the indicators for simplicity's sake. May I suggest:

- TSS (Indicator)
- TSS_ALARM(Alarm w/Mail)
- TSS_CandleTime

Please re-post ALL indicators once Oleg77 has completed his work on all of them, otherwise it will continue to be confusing for the non-techies on this thread.

By the way, TSS stands for: "T"he "S"imple "S"ystem!

Thanks!

Jam

SA Greetings to all TSS affiliates.

Thanks for all the effort to date. I think we’re on a good wicket here. To date I had 4 profit- taking and 1 loss trade. I installed the latest Indicators posted by Snobal1 yesterday being The NewIndicator and CandleTime.

Two things now bother me though being:

1. Which Alarm works with the new indicator.
2. What now creates the signal setting off the alarm?

To this I think we need to get to a Trading Plan, which one should update as changes to the system are introduced. This I hope will then remove all confusion.

With all this said, I think we are still batting on a good wicket.

Haapy Trading!

Hi Jam, Snobol1,

Newbie that I am, yesterday I had my very first day paper trading, and if you have to start somewhere with some kind of system, I'd say this is, eh, quite a good game of wicket indeed! Since I have no idea how to play wicket, it's actually a good analogy, since I also don't yet know what I'm doing on trading, and it seemed so "simple" and fun. Kudos! I shorted EURUSD based on the H4 signal. I watched the H1 signal for buy's to take profit, and I actually correctly anticipated an H1 buy arrow 2 hours early (by luck), and my price was the same as when this mornings H4 buy arrow came with the trend reversal. I made +60 pips! I bought today exactly based on the H4 arrow alarm, and so far it's been +23 to -14 pips, but it's trending upwards at +10 pips this moment. We'll see, but it's looking good...

I'm posting because of what I highlighted in bold in Jam's message above. Jam said that the arrow will anchor at Bar(0) Open, and the system will be to buy/sell at Bar(0) Open price.

Uh, now that I have real-time experience with the STOCH-ALARM-3X version (using the old T3MA so far, which I'll replace with the update), I have to say I'm a bit concerned with the plan but perhaps I don't understand it so let me explain.

What may not be obvious to readers of this thread is the exact time the real-time arrows actually show up. You have to watch real-time action to understand how the arrows work. If you look only at old charts without understanding the timing of the arrows, then indeed, this looks like a "miracle" system as someone said. Well, it's not as good as historical charts make it look, but PLEASE don't misunderstand me, this is still GREAT so far. A "miracle" would be that you can divine the future. The charts imply that's what happened. (Absolutely no criticism intended).

Instead, here's what it's like real-time (using above soon-to-be-replaced version):
You're watching an H4 chart that has been trending upwards, and it appears to have peaked. The 00:00 Bar(1) (00:00 to 03:59) is complete, and now the 04:00 Bar(0) has opened, and it's updating with live tick action. At SOME moment between 04:00 to 07:59, at some tick price, the SELL Arrow is displayed above the 00:00 Bar(1)! If the tick price goes up again, then perhaps that Arrow was a false alarm. You don't know until the bar completes, but perhaps you have a good feel, or you're watching H1 charts and, yes, it seems like it's going down, so good, you SELL the pair. But Bar(0) Open price is long gone, and it may never happen again!! You can't necessarily follow the rules to sell at Bar(0) open because that moment is in the past, and while price may retrace, you can't be sure it will, so you have to pick a price and go with it. More often than not -- which only live action can determine -- it will probably resume the new trend and the Arrow will be validated. If you backtest the system and if you could always buy at the Open price of the bar after the Arrow (the system using this prelim. version), then your results will be stellar, even miraculous. But in live-action, you may not have the chance to trade the Open price.

(Sorry this is long...)
To get to my point, if the new code anchors Arrows at Bar(0) Open, I'm concerned this will be too late. If I'm to understand it correctly, and maybe I don't, it seems to me that compared to the current code, the Arrows will occur TWO BARS later in time, not just ONE! Why do I say that? Well today's code puts the Arrow at Bar(1), one bar back in time. One could argue that's silly, because you didn't make the Arrow during that Bar(1), rather, you made the Arrow based on what happened during Bar(0). Now I'm all for the idea to put the Arrow over the correct Bar that causes it, because it's only fair to display something during the time you determined it. But if Jam say's the arrow it going to be anchored at the Open time of the latest bar, then WHEN did you determine the Arrow?? It seems to me it was determined some time during the PREVIOUS Bar! And if that's the case, then it's later than it could be.

This is why in a previous post I suggested the idea of using two shapes (or two colors) for Arrow indicators.

Let's imagine Triangles as another shape. During Bar(0), the current Bar, if the real-time tick price detects a peak or vally, then display a Triangle at Bar(0). Once displayed, you CAN take it away if the conditions reverse, so it might blink on/off with tick action. However, if by the Close of Bar(0) the trend is confirmed, than on the NEXT Bar shift, you leave the triangle at what is now Bar(1), and you anchor an actual Arrow at Bar(0). Now your chart has both Triangles and Arrows. The Triangle says an arrow was forming during that Bar. An Arrow which follows it says, YES, that Triangle was confirmed, the new trend is in play. If you see a Triangle on the chart by itself, you won't care because you know it was a glitch, or a failure to properly remove the Triangle, because there is no Arrow which confirms the new trend. This resolves the problem with the current code where it happens to leave some old Arrows around which disappear if you repaint.

I have one additional idea which can give additional graphical data real-time. As with today's Arrows, and as I'm proposing be done with Triangles instead, can the real-time tick price which triggered the Triangle be displayed on Bar(0)? That tick price goes with the FIRST Triangle, even if you later take a Triangle away and repaint the Triangle with a brand new signal. It tells you that had you reacted to the first Triangle, that's the price you would have bought/sold. You can visually compare it to the Open price of the next Bar where the Arrow will be drawn, and I'm guessing that most of the time, it's going to be a much better price. THIS IS THE MEASURE OF THE TRIANGLE'S VALUE TO YOU! You can also get an idea of how often price retraces after the Triangle is diplayed so you won't necessarily have to jump right in immediately. Rather, with experience, you can make a better estimate.

While were on the subject, can we please add the tick price which triggers the alarm to the text of the popup (text) alarms? It tells me when the alarm occurred, but not the price. Thus I have no idea whether it was the best time to jump in unless I study tick data or Minute charts, which is tedious.

Forgive me if I'm off base here, but I think this may be a good idea to use both Triangles and Arrows as indicators, but I won't have a clue how to code it, and if the work is being done right now by expert coders, then this idea is (perhaps) worthy of further consideration.

Thanks for reading this long post... and once again, THANKS to Snobol1 (Pip2), et al, for such a great tool. I'm eagerly anticipating the new releases, but the old one is already a lot of fun.

Pips4Life

what is the settings for 5min ?

regards, philip

Hi Philip

The new version is not out yet. It may be a week or so before it is tested and placed on this thread. The program was originally developed for time frames such as 1 hour and higher. I doubt if a 5 minute version is being considered.

Great programming minds are working on a much anticipated program. I liked the old version, the new version will be great.

Good Luck