Machine Learning in ProOrder ProRealTime
Forums › ProRealTime English forum › ProOrder support › Machine Learning in ProOrder ProRealTime
- This topic has 454 replies, 32 voices, and was last updated 2 years ago by Khaled.
Tagged: machine learning
-
-
04/24/2020 at 2:27 PM #127816
Yes, Fifi’s itf worked for me too … but then, so does this one on DJ 15m with 8 years TBT, no error message. Only on Daily I get the tbt warning
123456789101112131415161718192021222324IF high > renkoMax + boxSize THENWHILE high > renkoMax + boxSizerenkoMax = renkoMax + boxSizerenkoMin = renkoMin + boxSizeWENDELSIF low < renkoMin - boxSize THENWHILE low < renkoMin - boxSizerenkoMax = renkoMax - boxSizerenkoMin = renkoMin - boxSizeWENDENDIFc1 = renkoMax + boxSizec2 = renkoMin - boxSize// Conditions to enter long positionsIf c1 thenBuy N CONTRACT at renkoMax + boxSize stopEndIf// Conditions to enter short positionsIf c2 thenSellshort N CONTRACT at renkoMin - boxSize stopEndIf1 user thanked author for this post.
04/24/2020 at 2:42 PM #127821Only on Daily I get the tbt warning
But you have got the While and Wend in the code you are getting the problem with … this is what Fifi has been trying to tell us (While and Wend loop causes Issues? ).
Also – as you pointed out – we ditched (or should have?) the While and Wend on the first page??
EDIT / PS
Or am I misreading you? Are you saying you get tbt warning on Fifi code AND the code above with While and Wend on DAILY … so the While and Wend does not appear to be the Issue?
Maybe we should delete this whole Topic and start again!!?? 🙂
1 user thanked author for this post.
04/24/2020 at 3:04 PM #127830Fifi’s code solves the tbt problem on all TFs but the results are terrible. The original (with While and Wend and at renkoMax + boxSize in the entry conditions) gives 8 years TBT on 15m TF and acceptable results. There’s just something about the Daily that it doesn’t like.
Attached is my version with Fifi’s changes (i think – unless I blundered in the conversion). Run them both and you’ll see what i mean. Makes me think that While and Wend is actually doing something important.
1 user thanked author for this post.
04/24/2020 at 3:13 PM #127835Attached is my version with Fifi’s changes (i think – unless I blundered in the conversion)
I get above version to go back to 1971 on Daily and 100,000 bars on every other TF down to M1 with no tbt warning.
But now we just need to get a version that makes profit? 🙂
04/24/2020 at 3:26 PM #127838Maybe it just doesn’t like my settings – ValueX is now box size and I changed the reset and reps. But where mine makes ~23k profit, the other makes ~10k loss, they are clearly v different animals.
04/24/2020 at 3:31 PM #127839Thanks, good idea, which I followed – pls see screenshot. It still gives me 4x to 5x more profit than the original non VRT system?
The only way I can get the VRT to turn off and match that much lower profit from the non VRT system is to // the VRT code. Why does VRT create so much more profit?
I’ve posted the newly amended nonetheless itf, which I had downloaded just now as advised. Thanks again, hopefully it’s just a simple oversight of mine.04/24/2020 at 3:43 PM #12784404/24/2020 at 4:47 PM #127865get above version to go back to 1971 on Daily and 100,000 bars on every other TF down to M1 with no tbt warning.
When I looked later the Tick by Tick box was not enabled so it may not work on all TF’s with no tbt warnings??
04/24/2020 at 5:11 PM #127874I rest my case; While/Wend is there for a reason.
1 user thanked author for this post.
04/24/2020 at 5:23 PM #12788004/24/2020 at 5:51 PM #127884I have never seen the stop loss written as “Set stop trailing ” … esp when there is no trailing stop code.
The heuristics will work with ValueX as the stop value the way I have it.
It will also run at 30m TF but at 1 hour and higher it gets the tbt warning.
04/24/2020 at 5:56 PM #12788604/24/2020 at 6:24 PM #127893Hi everybody, has there been any consensus as to what the problem really is with the daily tick by tick (tbt) warnings and this code? I really wish there was an admin that could sort this tbt daily warning problem out once and for all because it is taking an inordinate amount of time and energy to resolve.
Even with Fifi’s code using Wend/While, I still get tbt warnings on daily charts!
I still get TBT Warnings on DAILY with:1234567891011121314151617181920212223242526c1 = renkoMax + boxSizec2 = renkoMin - boxSize// Conditions to enter long positionsIf c1 thenBuy N CONTRACT at MarketEndIf// Conditions to enter short positionsIf c2 thenSellshort N CONTRACT at MarketEndIfAnd with this code too://Fifi//c1 = renkoMax + boxSize//c2 = renkoMin - boxSizeIf close = renkoMax + boxSize thenBuy N CONTRACT at marketEndIfIf close = renkoMin - boxSize thenSellshort N CONTRACT at marketEndIfI’ve also downloaded some of the recent itf’s here (and thank you for posting them) to find they either trade no more than one position or produce tbt daily chart warnings. The slightest modifications, which are then put back to the original itf version, cause problems. I download the original again and it trades okay (although without profit). It’s like the code is SO sensitive it’s ridiculous. See: https://www.prorealcode.com/topic/machine-learning-in-proorder/page/9/#post-126323
I’ve transferred in Nonetheless fast working backest code (even though it looks to all intent and purposes identical to my own) because my 1M ML system had become very slow to backtest, only to find the next day that the nonethless version of code that I’ve put into a newly named system had become sluggish too! (compared to the original nonethless itf and other ML itf’s that have been uploaded here and which I am backtesting in parallel).
Tbt tests:
I suspect the Wend/While conditionality is causing the issue, why it seems to be on the daily chart I don’t know, but I suspect it is this loop code because this is the only time I have ever had so many problems with a tbt test. The problem for me though is that: “at market” is not the same as “at renkoMax + boxSize stop.” Despite all the problems with tbt warnings, this explains the better profits with “at renkoMax + boxSize stop” on backtests where warnings are not being issued. Wend and While are important conditions.If anyone has a definitive answer to the Wend/While, and/or tbt daily warning issue it would be gratefully received!
04/24/2020 at 6:38 PM #127894Well spotted, I copied from the Renko forum, shouldn’t that be:
1Set Stop pTrailing ValueX?https://www.prorealcode.com/blog/learning/kinds-trailing-stop-proorder/
Are we back on track!? No tbt warning for 2018-2020:
Ps/ Noticed the C1 and c2 is incorrectly written. Try:
Long/Short Conditions12345678910c1 = renkoMax + boxSizec2 = renkoMin - boxSizeIf c1 thenBuy N CONTRACT at marketEndIfIf c2 thenSellshort N CONTRACT at marketEndIfProblem is:
12If c1 then Buy N CONTRACT at marketEndIfthe same as..
12Buy N CONTRACT at renkoMax + boxSize STOPEndIf?
04/24/2020 at 7:07 PM #127905Apparently Set stop trailing and Set stop ptrailing are both correct, I’d just never seen it before. But all the variations in your previous post give me the tbt error on the Daily TF.
-
AuthorPosts
Find exclusive trading pro-tools on