NAS 2m HULL-SAR trading system
Forums › ProRealTime English forum › ProOrder support › NAS 2m HULL-SAR trading system
- This topic has 343 replies, 42 voices, and was last updated 1 year ago by bege.
-
-
12/30/2020 at 3:57 PM #155697
In the 2 weeks that I’ve been running it, the first trades were 12700, 12687, 12691 within 16 minutes between the first and last (Dec 21).
The second entries were 12681, 12706, 12715 about 40 minutes apart (dec 24).
Then one position opened on the 29th at 12914, still open.
Is that what you’ve got?
Judging from previous versions, this seems typical. If the entries were more widely spaced then either you’d be buying at a much worse price, or it’s fallen so far that the broader conditions are no longer met – in which case it may well be a losing trade and you’ll be pleased that there’s only one entry.
1 user thanked author for this post.
12/30/2020 at 4:58 PM #155711As I write I just started it a few days ago.
It took 3 trades (all Long) on Dec 28 at 12828 (17:14), 12835 (17:20) and 12836 (17:28), those were all closed (with a profit) on Dec 29 at 07:55.
Then it took 3 trades (all Long) on Dec 29 at 12914 (14:34), 12917,8 (14:42) and 12917,0 (14:52). Those were sold with a loss today at 15:38. Strange that it only took 1 trade for you, but 3 trades for me.
At 15:38 it just immediately opened a Short after it closed the positions above.
So you are correct. The trades are not taken immediately after eachother, they are spaced 6-10 minutes apart, or something like that. Does the behaviour seem accurate you think?
12/30/2020 at 5:16 PM #155714I’m talking about
which is long only. Which algo are you running?
Also, did you adjust the Ctime settings for Sweden?
12/30/2020 at 7:34 PM #15572712/30/2020 at 8:22 PM #155730v3b.3 was developed with just a 1 year backtest, so I wouldn’t recommend.
v5.3L is built on 6 years of data 75/25 so should be more reliable (in theory) and making it Long only improved performance dramatically. If you’re on GMT then it should be good to go with no changes.
1 user thanked author for this post.
12/30/2020 at 8:41 PM #15573101/19/2021 at 12:06 PM #158465Hi @Paul, I’ve been working on an ATR TS version of this in combination with your breakeven code but I’m finding that it doesn’t want to move the stop. This is the code I’m using:
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869// break even stop incl. cumulative positionsonce enablebe = 1if enablebe then//====================once besg = 0.3 //% break even stop gainonce besl = 0.04 //% break even stop level (+ or -)besensitivity = 2 // [1] default [2] hl [3] lh [4]typicalprice(not use once)//====================if not onmarket or ((longonmarket and shortonmarket[1]) or (longonmarket[1] and shortonmarket)) thenbenewsl=0mypositionpricebe = 0endifpositioncountbe = abs(countofposition)if benewsl > 0 thenif positioncountbe > positioncountbe[1] thenif longonmarket thenbenewsl = max(benewsl,positionprice * benewsl / mypositionpricebe)elsebenewsl = min(benewsl,positionprice * benewsl / mypositionpricebe)endifendifendifif besensitivity=1 thenbesensitivitylong=closebesensitivityshort=closeelsif besensitivity=2 thenbesensitivitylong=highbesensitivityshort=lowelsif besensitivity=3 thenbesensitivitylong=lowbesensitivityshort=highelsif besensitivity=4 thenbesensitivitylong=typicalpricebesensitivityshort=typicalpriceendifif longonmarket thenif besensitivitylong-positionprice>=((positionprice/100)*besg)*pointsize thenbenewsl=positionprice+((positionprice/100)*besl)*pointsizeendifendifif shortonmarket thenif positionprice-besensitivityshort>=((positionprice/100)*besg)*pointsize thenbenewsl=positionprice-((positionprice/100)*besl)*pointsizeendifendifif barindex-tradeindex>1 thenif longonmarket thenif benewsl>0 thensell at benewsl stopendifif benewsl>0 thenif low crosses under benewsl thensell at marketendifendifendifif shortonmarket thenif benewsl>0 thenexitshort at benewsl stopendifif benewsl>0 thenif high crosses over benewsl thenexitshort at marketendifendifendifendifmypositionpricebe = positionpriceendifbut if you look at the attached image, the stop should have moved when the price hit 12878.3, no?
01/19/2021 at 12:08 PM #15846601/19/2021 at 12:35 PM #15847601/19/2021 at 6:13 PM #158548No, the min distance on the NAS is only 4. This should go to b/e after about 40 points, but it went over 90 and still nothing.
I always feel better once i know a position is all locked up and can’t lose money.
01/20/2021 at 6:17 PM #15871701/21/2021 at 6:33 AM #158762Still working on it, but doesn’t look quite as promising as the NAS.
1 user thanked author for this post.
01/21/2021 at 8:28 PM #158861hi nonetheless , I didn’t saw your previous post with the question regarding the breakeven. I haven’t looked into this, but it’s probably not relevant anymore now you ‘ve the code from Roberto. I’am curious how it would perform on this strategy.
01/22/2021 at 1:46 PM #158908Thanks Paul, I’ve been playing around with all different TS for this, and yes now Roberto’s is another option – still tinkering with that one.
Curious about your breakeven + ATR TS, it seems to behave properly (ie positions do close as if the stop had moved) but it’s not indicated in the open positions window. Also on the IG web platform, the SL display never changes but then the position will mysteriously close, as if the stop had moved.
Have you ever seen this?
01/23/2021 at 9:10 PM #159131Hi guys, I did a small backtest on the Dax time frame 2 minutes with excellent results even if only for a month, but the real time strategy I tested on Friday 22 January did not open any positions, while the backtest shows 2 open positions. Can anyone explain to me why and if there is an error to correct? Thanks.
-
AuthorPosts
Find exclusive trading pro-tools on