- ago
When running the backtest for my trading system it sometimes happens that for two positions it does not show them on top when sorting them by date but one on top and one a few lines below. Additionally the signals are then not up to date. How come?

Furthermore, in the latest version when running the backtest the loading status (green beam at the bottom) is not displayed. It is just showing the ticker symbols. Anyone know why?
0
655
Solved
10 Replies

Reply

Bookmark

Sort
Glitch8
 ( 15.20% )
- ago
#1
Yes, the progress bar not showing is a side effect of another change, it's already been fixed for the next Build 20.

I'm not following what you mean in your initial question. Can you post a screen shot and explain the percieved problem?
0
- ago
#2
0
Glitch8
 ( 15.20% )
- ago
#3
OK, there is one Position still open, so it's sorted to the top. The next signal was exited on September 7, 2021. I'm not seeing the problem?
0
- ago
#4
The position in line 4 is also closed yet. So there should be displayed "Sell after 1 bar" in the Exit SIgnal column - but it does not.
0
- ago
#5
Additionally, at that time I had two positions open, but it just displayed only the one at the top.
0
Glitch8
 ( 15.20% )
- ago
#6
Mmmm, if there were two positions open it would show that. Your Strategy must be selling the position by some other means, or maybe the symbol left the WealthData dynamic index on that date, so WL7 closed the position (which is also possible). We'd need to see the full strategy and backtest settings to reproduce what you're doing and give a concrete answer.
0
- ago
#7
What an inconvenient way of taking screenshots. Simply strike the "Print Screen" key and then paste into Paint (built in) or other imaging application. Save as PNG and attach. That's all it takes.
0
- ago
#8
@Braunstein
QUOTE:
The position in line 4 is also closed yet. So there should be displayed "Sell after 1 bar" in the Exit SIgnal column - but it does not.

No, you're most likely not right. The position #4 is closed but simply does not have an exit signal assigned. Which creates an impression that it's not closed.

As Glitch suggests, we'd need to review your Blocks and see which exit signal is "mute".
0
- ago
#9
@Braunstein

Looked into our building blocks (including extensions) and couldn't find even one with a 'mute' exit signal. Apparently your system uses Sell After N Bars. Can't see how it may be possible. Could you help us reproduce?
0
Glitch8
 ( 15.20% )
- ago
#10
I’m still suspecting the exit occurred due to a symbol leaving a dynamic index. We should add a signal name for that event!
2
Best Answer

Reply

Bookmark

Sort