[124.2018] - AlgoWizzard <EMA Cross> H4 - no Result

Problems with backtest. No result is displayed.

I have:
- the example Cross <EMA Cross> is selected and loaded
- edited the values ​​of (Shift) for all <TradingSignals> from "1" to "0"
- "TimeFrame" H4 selected
- Updated variable <FastEMA> to "14"
- Updated variable <SlowEMA> to "50"
- I have retained the remaining variables and settings

Afterwards I started "Run Full Backtest" -- without result.
Attachments
20191002_AlgoWiz_Backtest-Result.png
(16.89 KiB)
20191002_AlgoWiz_Backtest-Preview.png
(15.91 KiB)
20191002_AlgoWiz_Backtest_Setting-Data.png
(26.75 KiB)
  • Votes +3
  • Project StrategyQuant X
  • Type Bug
  • Status Fixed
  • Priority Normal

History

HH
#1

Hans

02.10.2019 14:20

Task created

MF
#2

Mark Fric

02.10.2019 15:29

Status changed from New to Waiting for information

please attach the strategy
HH
#3

Hans

07.10.2019 18:59

Attachment EMA-Cross_adv.sqx added

The Strategy is your inside-example "EMA Cross ".

I have only changed the above named variables.


I saved it again separately and hope all parameters / variables have been adopted

HH
#4

Hans

07.10.2019 19:20
Here an addendum may have a role:
I have in parallel the builder for the generation of new strategies in operation. That means, I partially use the AlgoWizzard additionally.
MF
#5

Mark Fric

09.10.2019 13:10

Status changed from Waiting for information to In progress

MF
#6

Mark Fric

10.10.2019 13:58
Hans, I'm unable to reproduce it. I tried the steps that you described, also your strategy and it always backtest sproperly, there are some trades.


Isn't this problem somehow caused by data?



Also, from your screenshot I can see that it is waiting for quick backtest (Automatic quick backtest: waiting for a change), it doesn't seem that full backtest was started.

HH
#7

Hans

15.10.2019 23:54
Hello Marc,

...sorry, I currently have problems with my vps and can not dedicate the fault.
As soon as I have the opportunity again, I will try to narrow down the cause. Sorry for the delay.
Dw
#8

Diwi

20.10.2019 12:13
Voted for this task.
b
#9

beppil

22.10.2019 07:01
Voted for this task.
MF
#10

Mark Fric

31.10.2019 14:21

Status changed from In progress to Waiting for information

HH
#11

Hans

03.12.2019 09:00

Attachment AlgoWizzard.mp4 added

Attachment log_2019_12_02.log added

Attachment log_2019_12_03.log added

Attachment Server_Uptime.png added

Attachment SQ_Global Configuration.png added

Attachment SQ_Prozessoraffinitat.png added

Attachment SQ_RunningTime.png added

Attachment SQ_Prozessoraffinitat.png deleted

Attachment log_2019_12_03.log deleted

Attachment SQ_RunningTime.png deleted

Attachment AlgoWizzard.mp4 deleted

Attachment log_2019_12_02.log deleted

Attachment Server_Uptime.png deleted

Attachment SQ_Global Configuration.png deleted

Attachment AlgoWizzard.mp4 added

Attachment SQ_Global Configuration.png added

Attachment SQ_Prozessoraffinitat.png added

Attachment SQ_RunningTime.png added

Attachment log_2019_12_03.log added

Attachment log_2019_12_02.log added

Attachment Server_Uptime.png added

Enclosed more details
HH
#12

Hans

20.01.2020 08:19
Voted for this task.
MF
#13

Mark Fric

12.03.2020 10:26

Status changed from Waiting for information to Fixed

the problem was caused by running Builder, the message that backtest was finished was lost among other messages about build progress, Thats why UI didn't know backtest already finished.


This should be fixed now. However, if you have a build with long running tasks - such as optimizations, it might take a long time until AlgoWizard backtest is performed.


Votes: +3

Drop files to upload

or

choose files

Max size: 5MB

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

...
Wait please