<- Back to Tasks

[Build 137.1639 RC3] Signals Rules not working correctly





If I use a condition Or with brackets, it won't work  correctly, the signal won't be true as it should be. (Image 0)


If I create 2 signals instead of one signal to remove the OR condition, then it is working correctly. (please see video "Build 137 RC3 Error")


If I check the source code of the signal, (Template 17.doc), all the brackets are present and at the correct place.


I created a template with similar condition "Test Template 17 b", and it seem to work 


Please see video : 
https://drive.proton.me/urls/DYZ5AAFW1R#lkN8vLN6uj4T


(I extracted the signal from the template "M 75 Light 2" in case you want to see inside)


Please see comment below, there is another case where Signals Rules do not work correctly




Attachments
Template 17.docx
Template 17.docx
(32.42 KiB)
M 75 Light 2.sqx
M 75 Light 2.sqx
(9.57 KiB)
image-0.png
image-0.png
(130.33 KiB)
Build 137 RC3 Error.mp4
Build 137 RC3 Error.mp4
(3.38 MiB)
Test Template 17 b.sqx
Test Template 17 b.sqx
(6.99 KiB)
  • Votes +1
  • Project AlgoWizard
  • Type Bug
  • Status Fixed
  • Priority Normal

History

E
#1

Emmanuel

28.05.2023 09:04

Task created

E
#2

Emmanuel

28.05.2023 09:04
Voted for this task.
E
#3

Emmanuel

28.05.2023 13:07

Description changed:





If I use a condition Or with brackets, it won't work  correctly, the signal won't be true as it should be. (Image 0)


If I create 2 signals instead of one signal to remove the OR condition, then it is working correctly. (please see video "Build 137 RC3 Error")


If I check the source code of the signal, (Template 17.doc), all the brackets are present and at the correct place.


I created a template with similar condition "Test Template 17 b", and it seem to work 


Please see video : 
https://drive.proton.me/urls/DYZ5AAFW1R#lkN8vLN6uj4T



(I extracted the signal from the template "M 75 Light 2" in case you want to see inside)

E
#4

Emmanuel

02.06.2023 18:36
Another template example :


https://drive.proton.me/urls/VPHYWA1E8G#CkLQR9FDFW0l


E
#5

Emmanuel

13.06.2023 18:01

Subject changed from [Build 137.1639 RC3] Brackets with Or not working correctly to [Build 137.1639 RC3] Signals Rules not working correctly : Brackets with Or not working correctly

E
#6

Emmanuel

13.06.2023 18:14

Attachment Capture stop loss.jpg added

Attachment image-0.png added

Capture stop loss.jpg
Capture stop loss.jpg
(63.97 KiB)
image-0.png
image-0.png
(34.04 KiB)
Here is another example where both signals are not running correctly.  (please screen capture stop loss)


The long exit signal is true only if the   open is below the entry price -  (X time * Stoploss)


As I debug the template , I can read in my log :


15:30:27.666 [Blocking computeThread common #25 - Strategy 2.1.770] INFO  c.s.tradinglib.debug.Debugger - Debug  - ------------------------------------ Trade No  : 2.0

15:30:27.667 [Blocking computeThread common #25 - Strategy 2.1.770] INFO  c.s.tradinglib.debug.Debugger - Debug  - Pip Size : 1.0E-5

15:30:27.667 [Blocking computeThread common #25 - Strategy 2.1.770] INFO  c.s.tradinglib.debug.Debugger - Debug  - Stop loss : 100.0

15:30:27.667 [Blocking computeThread common #25 - Strategy 2.1.770] INFO  c.s.tradinglib.debug.Debugger - Debug  - Nb Level Max : 8.0

15:30:27.667 [Blocking computeThread common #25 - Strategy 2.1.770] INFO  c.s.tradinglib.debug.Debugger - Debug  - Open : 1.3321

15:30:27.667 [Blocking computeThread common #25 - Strategy 2.1.770] INFO  c.s.tradinglib.debug.Debugger - Debug  - Stop Min : 1.32444


The open is 1.3321 , clearly above the stop loss  1.32444, and the LongExitSignal2 = true, this is not possible.


If I put this condition on an exit rule, (see image 0 attached), it is working fine. But it wont work in the signal page .


It is not a matter of data because the open price is correct, it is matter of logic inside the signal page.


On my signal page, I have only 12 signals.


The source code in MT5 look correct

E
#7

Emmanuel

14.06.2023 14:46

Subject changed from [Build 137.1639 RC3] Signals Rules not working correctly : Brackets with Or not working correctly to [Build 137.1639 RC3] Signals Rules not working correctly

Description changed:





If I use a condition Or with brackets, it won't work  correctly, the signal won't be true as it should be. (Image 0)


If I create 2 signals instead of one signal to remove the OR condition, then it is working correctly. (please see video "Build 137 RC3 Error")


If I check the source code of the signal, (Template 17.doc), all the brackets are present and at the correct place.


I created a template with similar condition "Test Template 17 b", and it seem to work 


Please see video : 
https://drive.proton.me/urls/DYZ5AAFW1R#lkN8vLN6uj4T


(I extracted the signal from the template "M 75 Light 2" in case you want to see inside)


Please see comment below, there is another case where Signals Rules do not work correctly




TT
#8

Tamas

25.07.2023 07:56

Status changed from New to Fixed

The problem with brackets was fixed in SQX RC4. Please test it with the latest build.
E
#9

Emmanuel

25.07.2023 13:55

Attachment signal HS.docx added

signal HS.docx
signal HS.docx
(62.85 KiB)


Hi,


I did some test with RC4 and a signal was not working correctly as well if I added

 

Close < (Donchian middle - Donchian Lower) / 2                                                   (in the last line of the condition, please see attached word document)


instead of 


Close < Donchian middle



the bug is still in RC4


Please see the attached 




Votes: +1

Drop files to upload

or

choose files

Max size: 5MB

Not allowed: exe, msi, application, reg, php, js, htaccess, htpasswd, gitignore

...
Wait please