Thread: The sexy stochastic indior

Hello everybody, for individuals using the alluring stochastic egy developped by Boxingislife this is going to be a huge helper

You can loe the egy here :

https://www.forexsoutheast.asia/fore...e-journal.html

I have decided to release this indior to the wild as I believe that it isn't the indior that things, it's the trader.

Attached is your indior together with the code. I have documented it obviously but I intend to produce a guide for it.

The alarm system has been adjusted by ACS. Enormous thanks to him
https://www.forexsoutheast.asia/gene...fed-speak.html
https://www.forexsoutheast.asia/atta...6473474134.mq4

I've updated my indior and made a manual for it

Assess the last portion of my signal

https://www.forexsoutheast.asia/fore...urrencies.html

Originally Posted by ;

Hi everyone, for people utilizing the sexy stochastic egy developped by Boxingislife that this will be a huge helper

You can loe the egy here :

https://www.forexsoutheast.asia/fore...ixthsense.html

I've finally decided to publish this indior to the wild as I beleive that it is not the indior that matters, it is the trader.

Attached is your indior with the code. I've recorded it clearly but I intend to produce a guide for it.

I has one difficulty I hope the community will solve. The awake and mail process is functioning but it sends 4 moment the awake (one for every subsequent candle, watch this subject https://www.forexsoutheast.asia/gene...115-swaps.html for additional information)

Hello melpheos,

I am going to take a crack at it. It looks like a few people have indied somethings and you are going to check them out (from the other thread). I've got two questions (assuming the next chart signals show the case-numbers of the indior):
1. If the repeat mails are always four or it changes (from the chart in primary thread, it may be 1-5 signals for every case, case2 having most repetitions)?
2. Are they on consecutive candles (from the chart you posted in the primary thread, I expect them not be consecutive)? If it was 4 consecutive signals for every case, the case2-buy from the following post chart would create 16 emails!!!
Https://www.forexsoutheast.asia/fore...py-trades.html

If those are silly and not appropriate, pardon me. I believed these may have some relevance to the problem.


On another note, you've placed the email alert inside the pop-up Alert and when DisplayAlert is disabled, then email also will be disabled. I think they should be seperated.

Regards,
chandra

Originally Posted by ;

Hi ,

I am going to take a crack at it. It seems like a few people have indied somethings and you are likely to test them out (in the other thread). I've got two questions (supposing the following chart signals reveal the case-numbers of the indior):
1. Whether the replie mails are always four or it varies (in the chart in primary thread, it may be 1-5 signals for each circumstance, case2 having most repetitions)?
2. Are they really on sequential candles (in the chart you posted in the primary thread, I expect them not be sequential)? If it had been 4 sequential signs for each case, the case2-buy in the subsequent post chart would produce 16 mails!!!
Https://www.forexsoutheast.asia/gene...ing-breed.html

If those are silly and not correct, pardon me. I thought these might have some relevance to the issue.


On another note, you've put the email alert inside the pop-up Alert and if DisplayAlert is disabled, then email will be disabled. I believe that they ought to be seperated.

Regards,
chandra

1/ Allways four times whatever the case as far as I could tell. Of course, if a new signal look before the 4th candle, the alarm will be replaced by the new signal (for instance an up trend case 1 accompanied by an up fashion case 2)

2/ As clarified by someone on the first thread I left, the indior gives an alarm for each candle where the situation is confirmed. Since the indior check the standing of 3 candle back in time and put the signal on the candle, we provide 4 alarms and could presume the loop happens 4 times.
I could take a screen shot tomorrow of this awake occuring.

As for your email alert, this line Inserted Code if (emailAlert) SendMail(message Symbol(), message Symbol() , Stage() min chart); ought to check if the email is whether or not.

Originally Posted by ;

1/ Allways four times whatever the situation as far as I can tell. Of course, when a new sign appear before the 4th candle, the alarm will be substituted by the new sign (for instance an upward trend case 1 followed by an upward fashion case 2)

2/ As explained by someone on the first thread I left, the indior gives an alarm for each candle in which the situation is confirmed. As the indior check the standing of 3 candle back in time and put the sign on the candle, we can assume the loop occurs 4 times and give 4 alerts.
I can have a screen shot of the alert occuring.

As for the email alert, this line Inserted Code if (emailAlert) SendMail(message Symbol(), message Symbol() , Stage() minutes chart); ought to assess if the email is enable or not.

Hello melpheos,

I do not see any loop occuring 4 times. MT4 checks upto two previous candles current one. But I really don't think that is the issue. Since my alerts do not do so repetition.

I think the major issue is that you're specifying the CaseShown booleans inside the start function and reinitializing at every tick! The information about tick is missing everytime. From sending the alerts every tick it prevents! The booleans have to be defined before init function and should not be initialized inside the start function (you should take care of these booleans exactly like you're treating the lastAlertTime). In that situation we do not even require the control. Please assess this. I believe this has to be the reason and four candles might be just a coincidence (could be it takes four bars to get beyond that condition).

About email, I'm mentioning the email routine will be called only if the DisplayAlert is set to true (then pop-up also will come and we cannot have email without pop-up, even though we can have pop-up without email).

Regards,
chandra

Originally Posted by ;

Hi ,

I do not see any loop occuring 4 times. MT4 checks upto two past candles current one. However, I really don't think that's the issue. Since my alerts do not do so rep.

I think that the major issue is that you're specifying the CaseShown booleans inside the start purpose and reinitializing at each tick! The info about tick is lost everytime. LastAlertTime in the SendAlert function prevents it from sending the alerts every tick! The booleans have to be defined until init function and shouldn't be initialized inside the start purpose (you need to take care of these booleans just as if you're treating the lastAlertTime). In that situation we do require the control. Please check this. I believe this must be the reason why and four candles might be only a coincidence (may be it requires four bars to get beyond that state).

About email, I am mentioning that the email routine will be called only if the DisplayAlert is set to true (then pop-up also will come and we can't have email without pop-up, though we can have pop-up without email).

Regards,
chandra

I personnaly didn't want the email awake only when I made it and, as I had this repaeting alert issue I forgot about it, however, you're right about the logic of this programming. I'll change that as I might want now to get rapid alert (popup) on some chart rather than other people and email alert for longer TF chart.

As for the 4*moment I dont really get your explaination I am not an Excellent coder)

Originally Posted by ;

I personnaly did not need the email alert only when I created it as I had this repaeting alert issue I forgot about it, however, you are right on the logic of the coding. I'll change that as I might want now to receive rapid alert (popup) on some chart rather than others and email alert for more TF chart.

As for the 4time I really get your explaination I'm not an excellent coder)

Hi melpheos,

Here are the three problems.

1. Is going to be re-initialized while the calculation are done at next tick. That values are not kept secure. The Case1_Shown sort of items when you specify within the start function, will constantly have the start value as zero (means false for boolean). So, initializing it is uncessary. Whatever value they have been delegated in the last cycle of calculation will be dropped. Consequently, if the Case1_Shown was set to True from the last tick calculation, it will be reset to False automatically at the end of that group of calculations (so for every new signal the Case1_Shown will start as False). Consequently, if you would like the last data to be recalled, it must be defined where you have described the lastAlertTime (out of any function, I think these are called global variables).
Option: I moved them near lastAlertTime (made them global factors).

2. The whole purpose of saving is missing, if you keep re-initializing. It will work only until the end of the remaining part of the loop and at every new tick that value will be and you'll acquire new alert (only the lastAlertTime control saved you out of accessing the alerts at every tick).
Option: I added initializing at very different places.

3. You are not assessing if Case1_Shown was authentic while assessing for states of Case1 (others too). I think (I am not sure on this) we do not want to check for Case1, once the Case1_Shown is currently correct. So, in that list of conditions for each situation, you have to add additional control before assessing fresh whether the Case1_Shown == False to assess. Here we may get confusion since both up and down states use the same factor Case1_Shown... May be that they have to made as two different sets.
Option: I left the additional conditions, and made them separate and added that a set of Case3_Shown also.

I do not understand how the calculations work and whether it is feasible for the conditions to be authentic at consecutive candles. So, I am not sure if will fix the issue or add more! I attached to a chart and assessed for the signs and they seem to be OK. I did not check the alerts. Please check if this works as you anticipated. I don't understand the fourth set of calculations (that has two forms), but because it did not have alerts, I did not bother much.

I also fixed the Alert and Mail functions. Now they ought to function independantly.

Please check and let me know if they are any better!

Regards,
chandra

EDIT: I think it might have a issue of Alert and Email for past signals too (that will be too many). If you become such signs for past scenarios, it ought to be fixed from the call to sendAlert by altering as shown below (in most 6 loions; I lt; 3 is OK or I == 0 must be used, I am unsure):
Current line:

Originally Posted by ;

SendAlert ( Stochastic Downtrend Case 3 ; }

New Line:

Originally Posted by ;

if (I lt; 3) SendAlert ( Stochastic Downtrend Case 3 ; }

EDIT: See the last version from the first post.

1 Attachment(s) No shift

It repeating four times like previously...

The timestamp of this alert are somewhat weird that is because of the late hour and the market is not so busy...
https://www.forexsoutheast.asia/fore...ixthsense.html

Originally Posted by ;

No change

It repeating four times such as previously...

The timestamp of the awake are somewhat odd that is due to the late hour and the market isn't so active...

Hello melpheos,

I am sorry that my final work failed to fix the problem. I also checked only on 1M chart and it did exactly the same. I had to do a crackdown on the code.

I threw out all the Case_Shown things from the code. Since the symbols were looking properly, I used those for making the alerts also (my apps utilize this manner). In order to make this work, I had to make the buffer initialization values to zero (the earlier used EMPTY_VALUE gave the replie signs even with this modifiion).

Currently for the 2 signs I got, there was just 1 awake for each (it was 3 and 1 -up instances, 4 down case failed to show signal, since I didn't program it, but it can be used easily).

Please check this out and let me know. I hope to find a face!!!

Regards,
chandra

EDIT: See the final version in the first post.

I'm testing it now but its late as well as on M1 I will not have an alarm.

I'll check tomorrow however, the repair appears to be a pretty great idea, didn't yet about that

just one problem, falling the case_shown can now provide multiple awake whenever there is mutiple sign on precisely the same candle (up and down sign cannot appear at precisely the same time but indie 2 and 1 or other mix can appear at precisely the same time ^^ ) I believe I could survive with this this does no occur all of the time

Thanks for the work you are doing.

Edit : I just had an alarm to M1 and it appears OK but I also changed the settings so the sign does no repaint above each other and there is rather a lot of mutiple sign doh