Posts made by Julianrob

@l-andorrà Thankyou!

Hi,

There seems to be a big issue with trailing stop glitches. Not just when it's used with ATR but also when it's used with fixed pips. And it took me 40 hours of painstaking testing to find when the issue occurs. On backtest sometimes it will go backwards, (TS should never go backwards), jitter up and down a bit, I've even seen it flash right back to initial stoploss quickly, then back to profit. (I tried to attach short video but it's not accepted here).

Here is a snapshot of my trailing stop setting. There are no other conditions that are connected with this trailing stop in my code, and no I don't have other trailing stops connected to it, so nothing else should affect it. The ATR multiplier variable 'ts_atr_mult' is set to 1.0 in this instance and I've had nothing but troubles with the stop jittering up and down once the price gets close to TP. But strange enough, when I change the ATR multiplier to 2, the trailing stop appears to work without glitches.
Now here's what I found really helped the issue:
When I open new trades, the initial stoploss is set to ATR 20 X 3, and this is when the issue is worst. I discovered by accident if I changed the initial stoploss to ATR 20 X 2, it seems the problem goes away. Or at least in most instances that I'm aware of. It seems that there's some kind of conflict between the initial set stoploss and the trailing stop. It's particularly troublesome on backtesting as it slows down a lot while processing a lot more unnecessary and invalid stop moves. Please can this issue be fixed?

I noticed with several text objects continually updating, it slows backtesting waaaay down to a crawl. So I've got a version for backtesting with all that disconnected

Thanks jstap. It took me several searches here to realise comments can't be deleted. Not as convenient, because creating labels, then variables, all need their own text blocks because there aren't optional multiple labels and values, also no way to control decimal places. I guess I have to convert to text blocks.

Could we request this as a bug fix, to be able to delete comment blocks? It would be so good. Thanks

Hi,

I have been trying to figure this out for so long with trial and error. Now to the forum... I am trying to simply delete a chart comment once a trade closes.
I have tried if 'no trade' - turn off blocks with comment ID. I have tried 'check trades count, for each closed trade, etc., but no luck.

Here is what I have;
https://fxdreema.com/shared/NGMV3Tt6

Someone please assist? Thanks in advance!

@roar I know this robot, while it won't be perfect, will be capable of good consistent returns because I've manually researched a lot of history data and applied the principles to the charts to see. But I have to stop forward testing at the moment to fix critical errors in the program to do with variables not updating and it's not closing trades when it's supposed to. Jstap is helping me with this, I hope to resume forward testing soon, in the meantime the issues have affected the forward testing. As soon as it's running sweet again, I'll set up a Myfxbook for tracking

The equity curve can't be included on a statement only on a backtest. But no issue with equity. Yes I'd post less often but I'm answering roar

@roar One week forward test results. Too many trades to print so here's just the details. Ended the week up just under 1,045 pips. It's taken me a whole week to figure out how to get certain variables to modify themselves under special conditions. Work in progress

Yes, range trading is tricky and needs to be done at certain times. I mean, when upper band is falling and candle touches it, sell and when lower band is rising, and candle touches it, buy

@felix2828 I have developed a similar strategy for one of my robots using bollinger bands. Can't help you with the flags thing, never saw it. But I can say, a useful filter to the bands strategy is to sell off the upper band when its also decreasing in value, and buy off the lower band when it's increasing in value. This can improve the signal quality slightly and help you selling off the top band while the candles continue piercing upwards

@p3ym4n Thanks, but 'if trade' isn't an option in conditions. I'm not sure how to do this. 'Close profitable trades' is the closest option but still doesn't achieve what I'm wanting. They must all be only profitable trades

Hi,

I am trying to write a condition that if every current open trade in the account is in profit, then do something.

I have tried under trade statistics > gross loss (now - current trades only) = value (numeric) 0 but this isn't working. Can someone help please?

@seb-0 Well now I've got a few days of actual forward testing data. So far it's looking alright and actually confirms the strategy. Let's see how we go

@RGoo Forward testing simply means I'm running the robot on a demo account and waiting to see the actual results, as opposed to just backtesting. Forward testing is a much more accurate way to see if a robot is likely to be profitable because it's not so much based on a theoretical idea but a more realistic trading environment

@TipsyWisdom When backtesting on M1 bar data, the ticks generated to build that candle are interpolated. That means, there are ticks that make up the OHLC of the candle, but everything in between is made up of random ticks that travel somewhat up and down.

Therefore, let's assume a candle has a high and low wick. Has it reached the high first before the close, or the low? This question is the key and holds a critical answer, at which most scalpers will be given false hopes that their system will yield real results after the backtesting looks good.

The only real way to test your strategy properly is forward testing, on a demo account. This will be very accurate and will be as close to live trading results as you're likely to get

So HERE are some forward testing demo results for FALCON robot: The moment I've been waiting for. But I only have 2 days of trading results at the moment - It's not working the way I want it to, I've had problems with it not closing batches of trades at a particular time that it's supposed to. But this is nevertheless a glimpse into how the results might work moving forward, so far so good::

I will post more results as and when I get them, for now I really want to fix the batch trade close issue

Yes this is great jstap.

I am finding success with timing the trade exits, more so than relying just on stop losses. Particularly when it comes to trading multiple currency pairs in the account. I can monitor the equity swings closely and I'm recording when the equity highs occur to help refine the strategy

@seb-0 The main reason backtesting is giving me inconsistent results is because it can't simulate the real spread variation particularly at the turn of the day. That is what I'm working on solving

Well it's taken me longer to get some real time data forward testing as I've had to make a lot of unexpected changes to the trading robot in order to get it to work the same way on forward demo trading than how it's backtested. And now it will take me a bit longer than expected to get solid forward testing results as I've had to apply new filters to the trades since backtesting.

But, first impressions are looking good forward testing now. Today, here's a screen grab of 13 open positions, all in profit. I know it's not much real info yet, but first optics are looking good and confirming my strategy. This is the FALCON robot you see. I'm really getting a good feel for what certain assets do at different times of day

I will keep updates coming in future discussions