ScalpMaster 10S
Forums › ProRealTime English forum › ProOrder support › ScalpMaster 10S
- This topic has 66 replies, 14 voices, and was last updated 3 years ago by javi cano.
-
-
05/01/2020 at 4:28 PM #129258
Since the trend of the moment is low timeframe systems, here is my proposal.
Based on the “Pivot Support / Resistance Zones” indicator by robertogozzi.Position Size= 1
Spread= 0.7EURUSD for now but maybe optimizable on different forex pairs
ScalpMaster1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980defparam cumulateorders= falsedefparam flatbefore= 090000defparam flatafter= 220000once longtrading=1once shorttrading=1TIMEFRAME(15 minutes, updateonclose)// Settingsema1= exponentialaverage[20](close)ema2= exponentialaverage[10](close)bullish = close>ema1 and close>ema2 and ema1>ema2ema1= exponentialaverage[20](close)ema2= exponentialaverage[10](close)bearish= close<ema1 and close<ema2 and ema1<ema2TIMEFRAME(10 seconds)// IndicatormyPivotSupportResistanceZones, myPivotSupportResistanceZones2 = CALL "Pivot Support/Resistance Zones"if longtrading then// Longif close crosses over myPivotSupportResistanceZones thenif bullish thenbuy 1 contract at marketendifendifendifif shorttrading then// Shortif close crosses under myPivotSupportResistanceZones2 thenif bearish thensellshort 1 contract at marketendifendifendif// Stop Lossset stop ploss 15// Trailing Stoptrailingstart= 50trailingstep= 2// Rest Stoplossif not onmarket thennewsl= 0endif// Manage Long Positionsif longonmarket then// First Moveif newsl= 0 and close-tradeprice(1)>=trailingstart*pipsize thennewsl= tradeprice(1)+trailingstep*pipsizeendif// Next Movesif newsl>0 and close-newsl>=trailingstep*pipsize thennewsl= newsl+trailingstep*pipsizeendifendif// Manage Short Positionsif shortonmarket then// First Moveif newsl= 0 and tradeprice(1)-close>=trailingstart*pipsize thennewsl= tradeprice(1)-trailingstep*pipsizeendif// Next Movesif newsl>0 and newsl-close>=trailingstep*pipsize thennewsl= newsl-trailingstep*pipsizeendifendif// Stop Order To Exit The Positionsif newsl>0 thensell at newsl stopexitshort at newsl stopendif05/01/2020 at 4:37 PM #129262Sorry, there is an error with the code, from line 22 to 39 its
1234567891011121314151617if longtrading then// Longif close crosses over myPivotSupportResistanceZones2 thenif bullish thenbuy 1 contract at marketendifendifendifif shorttrading then// Shortif close crosses under myPivotSupportResistanceZones thenif bearish thensellshort 1 contract at marketendifendifendifUpdated results
05/01/2020 at 4:41 PM #129268Good job.
Are you running it on your demo account?
05/01/2020 at 4:41 PM #129269Good job.
Are you running it on your demo account?
Just ultimated it today, i will run it from monday 🙂
05/01/2020 at 5:52 PM #129276Update v2
-minor optimization on the indicator
-system now works with both breakouts and bouncesScalpMaster v21234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980defparam cumulateorders= falsedefparam flatbefore= 090000defparam flatafter= 220000once longtrading=1once shorttrading=1TIMEFRAME(15 minutes, updateonclose)// Settingsema1= exponentialaverage[20](close)ema2= exponentialaverage[10](close)bullish = close>ema1 and close>ema2 and ema1>ema2ema1= exponentialaverage[20](close)ema2= exponentialaverage[10](close)bearish= close<ema1 and close<ema2 and ema1<ema2TIMEFRAME(10 seconds)// IndicatormyPivotSupportResistanceZones, myPivotSupportResistanceZones2 = CALL "Pivot Support/Resistance Zones"if longtrading then// Longif close crosses under myPivotSupportResistanceZones or close crosses over myPivotSupportResistanceZones2 thenif bullish thenbuy 1 contract at marketendifendifendifif shorttrading then// Shortif close crosses under myPivotSupportResistanceZones or close crosses over myPivotSupportResistanceZones2 thenif bearish thensellshort 1 contract at marketendifendifendif// Stop Lossset stop ploss 15// Trailing Stoptrailingstart= 50trailingstep= 2// Rest Stoplossif not onmarket thennewsl= 0endif// Manage Long Positionsif longonmarket then// First Moveif newsl= 0 and close-tradeprice(1)>=trailingstart*pipsize thennewsl= tradeprice(1)+trailingstep*pipsizeendif// Next Movesif newsl>0 and close-newsl>=trailingstep*pipsize thennewsl= newsl+trailingstep*pipsizeendifendif// Manage Short Positionsif shortonmarket then// First Moveif newsl= 0 and tradeprice(1)-close>=trailingstart*pipsize thennewsl= tradeprice(1)-trailingstep*pipsizeendif// Next Movesif newsl>0 and newsl-close>=trailingstep*pipsize thennewsl= newsl-trailingstep*pipsizeendifendif// Stop Order To Exit The Positionsif newsl>0 thensell at newsl stopexitshort at newsl stopendif05/01/2020 at 6:06 PM #12928705/01/2020 at 6:52 PM #129296Synonymous of robustness and no overfitting?
…or perhaps synonymous with getting something to work on a tiny part of history!
05/01/2020 at 7:07 PM #129298This is the main problem of working on systems with a low time frame,I have also repeatedly expressed my being doubtful about them.
Personally don’t know if I would ever start such a system on my live account1 user thanked author for this post.
05/01/2020 at 7:44 PM #12930005/01/2020 at 7:49 PM #12930105/01/2020 at 7:53 PM #12930205/01/2020 at 8:00 PM #129304I Think it’s because Francesco must have customized the indicator to return the two values, which is not in the original indicator, written to just plot segments, not returning data.
@Francesco please post your version of the indicator, ad TXT and/or ITF file.1 user thanked author for this post.
05/01/2020 at 8:03 PM #12930505/01/2020 at 9:01 PM #129313Haha Thanks Francesco …. can’t wait for Monday now to try it out!! 🙂
Its good on DJI 5 sec and not a loser on DAX and USTech … if I recall correctly? I just flashed it over what was in my List.
Might it not be even better if the Indicator was not called but included within the strategy code and then below could be optimised ?
Or maybe I need to understand how it all hangs together, before making suggestions.
I’ll probably try this and that anyway over the weekend.
Keep up the Good Work!
12PivotBAR = 3 //3 bars AFTER pivotLookBack = 4 //4 bars BEFORE pivot1 user thanked author for this post.
05/01/2020 at 9:52 PM #129321Yes GraHal, i guess it could be easily adapted for different assets, heres what we can optimize:
First of all PivotBAR and LookBack, but for eurusd 3 and 4 is already optimized. And yes! we can easily include the indicator in the strategy without the call in order to better optimize the values; v3 will have that for sure, already tried now!
Then the periods of the ema’s for the bullish and bearish detection (maybe ML on that?)
And of course sl and ts.
-
AuthorPosts
Find exclusive trading pro-tools on