Mother of Dragons trading strategy…
Forums › ProRealTime English forum › ProOrder support › Mother of Dragons trading strategy…
- This topic has 522 replies, 50 voices, and was last updated 3 years ago by LaurentBZH35.
-
-
03/28/2020 at 11:27 AM #12368703/28/2020 at 12:06 PM #123688
Please write here
Please respect the forum rules
See Attachment.Moderators note: I have edited bona25’s last post to remove his text from the ‘Insert PRT Code’ box and tidy up his ugly post.2 users thanked author for this post.
03/28/2020 at 12:09 PM #123690what happens when you create something brilliant
Thanks for the praise but I think a quick reality check may be in order: we don’t know yet if it’s brilliant or not. Based on the data we’ve got, it looks like it could have potential — and that’s about it. 32 months is still a very short back test. PRT v11 will hopefully be available later this year and then we’ll see what it looks like with a proper 10 year back test. Could be a bust.
Some of the best trading advice I ever received (and often v hard to follow) is, always look out for reasons why a trade might fail. It’s all too easy to talk yourself into a false optimism — and I am the world’s worst offender!
If you look at the equity curve for example, there is a very flat bit from April to Oct of 2018. It does virtually nothing for 6 months. That’s a long time to wait, not knowing if it’s ever going to fly. That could happen again in 2020, in which case we’ll all be disappointed.
Of course I hope that it makes us all stupidly rich. But as they say, don’t count your yachts until they’re on the water.
(I think that’s what they say, don’t they? something like that?)
03/28/2020 at 12:13 PM #123691what happens when you create something brilliant
Hi nonetheless
And in the code there is a lot of important things missing so that the algorithm is not rejected.03/28/2020 at 12:19 PM #123692things missing so that the algorithm is not rejected
Oh no — help! Like what, par exemple?
03/28/2020 at 12:22 PM #12369303/28/2020 at 12:33 PM #12369803/28/2020 at 12:37 PM #12369903/28/2020 at 12:37 PM #123700C’est pourtant bien là que j’ai écrit !
Look at your post higher
03/28/2020 at 12:39 PM #123701Opening and closing times of the market. Holidays. To check: if there is too much volatility do not take a trade.
Does time have to be specified even if I want it to run 24hrs/day? I have tried it using “Ctime = time >= t1 and time <= t2” but there was no time range that improved performance.
My assumption is if it’s a holiday then the market is closed, therefore no trades. No?
I would have no idea how to code for volatility. May be something in the snippet library, I’ll have a look.
03/28/2020 at 12:44 PM #12370303/28/2020 at 12:50 PM #12370403/28/2020 at 1:01 PM #123705If it is Friday and it is more than 11 PM and algo want to make a change.
Okay, I double checked and results are almost identical with Ctime = time >= 0 and time <= 230000
That solves the Friday problem, no? Can’t open a trade after 11pm.
But why Monday? If market is open from 11pm Sunday.
03/28/2020 at 1:23 PM #123707you could try a drop / rise exit … so if you are going the wrong way ‘> x bars’ and / or ‘> x bars AND > x drop / rise’
You gotta explain this to me like I’m 4 years old. What would the code look like? How is that different from yer basic stoploss?
03/28/2020 at 1:50 PM #123709If it is Friday and it is more than 11 PM and algo want to make a change.
Okay, I double checked and results are almost identical with Ctime = time >= 0 and time <= 230000
That solves the Friday problem, no? Can’t open a trade after 11pm.
But why Monday? If market is open from 11pm Sunday.
And are the indices open on Sunday?
-
AuthorPosts
Find exclusive trading pro-tools on