A Free Range Breakout indicator for Prorealtime
- This topic has 15 replies, 7 voices, and was last updated 3 weeks ago by
.
-
Hi SweTrade,
Have you downloaded the latest version of the indicator? The last version date is 2024/11/19.
I just copied and pasted the code from this topic on my Prorealtime platform, and it works.
Please try to download the indicator and restart the backtest.
I hope that will solve your problem.
1 user thanked author for this post.
Hello,
You have the latest version of the indicator. The previous code is not a trading system but a backtest.
It is a code example that can help you find a setup for manual trading.
You could add the PRELOADBARS instruction in the code and set a minimum number of contracts to fix potential issues.
Here is the code, including PRELOADBARS and a minimum number of contracts:
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384//--------------------------------------------------------//// *** Range Breakout Strategy - Nasdaq - 15-minutes *** ////--------------------------------------------------------//// Author: Vivien Schmitt// Website: https://artificall.com// Indicator: Range Breaker//--------------------------------------------------------//DEFPARAM CUMULATEORDERS = FalseDEFPARAM PRELOADBARS = 1000//--------------------------------------------------------//// *** SETTING BLOCK *** ////--------------------------------------------------------//// Capital to investONCE CapitalToInvest = 1000// Minimum number of contractsONCE NumberOfContractsMin = 0.5// Position SizeNumberOfContracts = MAX(ROUND(CapitalToInvest / Close, 2), NumberOfContractsMin)// Type of Breakout. Values: 1 to activate; 0 to inactivateONCE BullishBreakout = 1ONCE BearishBreakout = 0// Length of the range. Best values: 50; 100; 200ONCE RangeLength = 20// Extension of the RangeONCE RangeExtension = 10// Min range height (%)ONCE HeightMin = 20// Max range height (%)ONCE HeightMax = 50// Breakout conditions. Values: 1 to activate; 0 to inactivateONCE ValidatedBreakout = 0// Volume FilterONCE VolumeIncreases = 0// Trend FilterONCE PositiveTrend = 0ONCE NegativeTrend = 0// Target and Stoploss levelsONCE TargetLevel = 6ONCE StoplossLevel = 6// Starting YearONCE StartingYear = 2000// Font SizeONCE FontSize = 12// Return target and stoploss. Values: 1 to activate; 0 to inactivateONCE ReturnData = 1//--------------------------------------------------------//// * INITIALIZATION OF THE VARIABLES * //ONCE myBreakout = 0ONCE myTargetLong = 0ONCE myStoplossLong = 0ONCE myTargetShort = 0ONCE myStoplossShort = 0ONCE myHeight = 0ONCE myTrend = 0// *** IMPORT OF THE RANGE BREAKER INDICATOR *** //// -> TO DO BEFORE RUNING THE BACKTEST / A FAIRE AVANT DE LANCER LA BACKTEST //// * Uncomment the following line before running the backtest (Remove de "//" at the beginning of the line)// * Decommentez la ligne suivante avant de lancer le backtest (supprimez les "//" au début de la ligne)myBreakout, myTargetLong, myStoplossLong, myTargetShort, myStoplossShort, myHeight, myTrend = CALL "RANGE.BREAKER"[BullishBreakout, BearishBreakout, RangeLength, RangeExtension, HeightMin, HeightMax, ValidatedBreakout, VolumeIncreases, PositiveTrend, NegativeTrend, TargetLevel, StoplossLevel, StartingYear, FontSize, ReturnData](close)IF close >= myTargetLong THENmyBreakout = 0ENDIF// *** LONG POSITION OPENING *** //// NOT OnMarket ANDIF NOT OnMarket AND myBreakout = 1 THENBUY NumberOfContracts CONTRACTS AT MARKETSet Target Price myTargetLongSet Stop Price myStoplossLongENDIF// *** SHORT POSITION OPENING *** ////IF NOT OnMarket AND myBreakout=-1 THEN//SELLSHORT NumberOfContracts CONTRACTS AT MARKET//Set Target Price myTargetShort//Set Stop Price myStoplossShort//ENDIFI ran the code on Probacktest today and have no issues.
Kind Regards
Vivien
1 user thanked author for this post.
Hello Vivien,
I did not try anything – I just follow this thread with interest. 🙂
To avoid misunderstanding, your code does not run on Demo (or Live for that matter). The fact that it runs in Backtest does not tell much – or at least not everything.
It is a known issue that array-based code may run will in backtest but does not run in Demo/Live with not-understandable errors. So the least you need to do is run it yourself in Demo and see what happens. Next, chance is quite high that you will not be able to solve those errors.
A small chance exists that if you could elaborate as much as possible about where your code fails, people with the appropriate experience may be able to help.
In any event : though you may think it will be obvious that the Demo/Live environment behaves differently than Backtest, the issue most probably will be an internal PRT issue, that won’t allow “seeing-though” and therefore may not be solved at any time.N.b.: When I read druby’s post yesterday, I immediately wanted to advise you to eliminate all what’s arrays, if that is possible; notice that moist we do in PRT code can be done without arrays as well. Most, but not all. Just try it.
Regards and thank you for your work,
PeterIG Demo …Not to go too far down the array rabbit hole, the
‘defined or access an invalid index in an array’
error, does stop the proOrder algo if:
- An array is accessed and the array has not been defined.
- An array is defined but the array element is not defined.
The meaning of ‘define’ I think refers to, NO actual code, defining the array[element] = something, or, the defining definition is within a logic block that has not been executed before using.
Those appears to be different to, defining the array and, UNdefining the element, array[element] = UNDEFINED, which appears allowed.
The latter doesn’t appear to stop the algo even if it is accessed and used in a logic path, since UNDEFINED is probably taken as FALSE possibly.
In a calculation, it may be a different story, making the result n/a, and depending on where its used, maybe gives erroneous data and/or throws a different error.
Additionally, if a call’ed file RETURNS a not-defined array/element then you get the same error message.
Sending and/or/then RETURN’ing a UNDEFINED variable or array element from a called file gives the error:
‘server.strategy.probacktest.error.missing_data.call’
Also it appears that the array index works when zero.
Further, I couldn’t trigger an error for a FOR/LOOP or ARRAY INDEX being too big.
Maybe that’s a breeding ground for some bugs, I wonder what’s happening there!
Not yet seen any other array error’s, but not been deep down rabbit hole with complex code example, I keep #Peter’s advisory’s/warnings always in mind though.
#Vivien can you verify that array(s) ARE used in the Indicator, did early version come out before array’s in v11.
I also noticed that the contract size could be an issue in proOrder, re: your modification, but it didn’t get that far.
Still early days but Indicator and back-test work ok, had a good indication on DAX 15m today, reach 2nd target within 1 stop.
Only other thing that bugged me was with the y-axis auto scale, having to resize because some variables initially at zero or low values.
Not so bad when setup, but never fun.
Its a pity that it won’t run with proOrder, I second Peter suggestion to change that if possible.
Regards All
Find exclusive trading pro-tools on 
