Lower Low of last 2 bars followed by a higher Close

Author: TraDeBrum

Creation Date: 10/25/2019 11:40 AM

Wealth Lab » Trading Strategies » Lower Low of last 2 bars followed by a higher Close

TraDeBrum

10/25/2019 11:40 AM

Hi guys,

I am writing because I really need help about one strategy.

Let me try to explain,

I want to develop and convert to code-based strategy this:

The condition is when the minimum price in the current bar was lower than the last two previously bars and the closure price was higher than the last previously bar. The entry happens in the rupture of the current bar. The stop is in the minimum price the current bar.
My target is twice the amplitude of the current bar.

thank you

Eugene

10/25/2019 12:34 PM

Bom dia Aloysio,

Here's your Strategy code in WealthScript. You can optimize the number of previous Lows and the "amplitude" i.e. the profit target:

CODE:
Please log in to see this code.

Hope I understood you well. If not feel free to correct me.

Size:

Color:

Bom dia Aloysio,

Here's your Strategy code in WealthScript. You can optimize the number of previous Lows and the "amplitude" i.e. the profit target:

[code]using System;
using System.Collections.Generic;
using System.Text;
using System.Drawing;
using WealthLab;
using WealthLab.Indicators;

namespace WealthLab.Strategies
{
	public class TraDeBrum_20191025 : WealthScript
	{
		private StrategyParameter paramLows;
		private StrategyParameter paramAmplitude;
		
		public TraDeBrum_20191025()
		{
			paramLows = CreateParameter("Low (bars)", 2, 1, 10, 1);
			paramAmplitude = CreateParameter("Amplitude", 2, 1, 5, 0.5);
		}
		
		protected override void Execute()
		{
			double target = paramAmplitude.Value;
			int howManyLows = paramLows.ValueInt;
			
			for(int bar = 3; bar < Bars.Count; bar++)
			{
				if (IsLastPositionActive)
				{
					var p = LastPosition;
					var eb = p.EntryBar - 1;
					//var amplitude = TrueRange.Value(p.EntryBar - 1, p.Bars);
					var amplitude = High[eb] - Low[eb];
					
					//The stop is in the minimum price the current bar.
					if( !ExitAtStop(bar + 1, p, Close[eb], "SL") )
					
					//My target is twice the amplitude of the current bar
						ExitAtLimit(bar + 1, p, p.EntryPrice + amplitude * target, "PT");
				}
				else
				{
					//the minimum price in the current bar was lower than the last two previously bars and 
					if( Low[bar] <= Lowest.Series(Low, howManyLows)[bar] )
					
						//the closure price was higher than the last previously bar. 
						if( Close[bar] > Close[bar-1] )
					
							//The entry happens in the rupture of the current bar. 
							BuyAtStop(bar+1, High[bar] );
					
//							if( BuyAtStop(bar+1, High[bar] ) != null )
//							{
//								LastPosition.Tag = Close[bar];							
//							}
				}
			}
		}
	}
}[/code]

Hope I understood you well. If not feel free to correct me.

TraDeBrum

10/25/2019 6:16 PM

Thank you Eugene, but using the codes still confuse for me. Could you to explain with strategy from rules please?

I have already got to develop using by strategy rules the primary conditions, but not yet target and stop loss...

How I put my target (my target is 200% Fibonacci projection).
How I put my stop loss 1 tick below blue candle (blue candle is my start condition).

I attached a image to explain.

I hope to hear from you soon

request.PNG

Eugene

10/25/2019 6:58 PM

Your exits go beyond the capabilities of Rules already available. While Rules are undoubtedly powerful, not any trading idea can be expressed using them. If it were possible you'd probably be asking some A.I. (artificial intelligence) or a coding bot here instead of me! But since it's not the case yet there's at least one area where the human expertise can still be helpful -- like coding in WealthScript. :)

QUOTE:
How I put my stop loss 1 tick below blue candle (blue candle is my start condition).

Modify the stop loss line like this:

CODE:
Please log in to see this code.

superticker

10/25/2019 8:00 PM

The comma before "Tick" should be a period. But you knew that.

CODE:
Please log in to see this code.

When I first saw this, I thought it was some new "tick" parameter of the ExitAtStop(...) call I didn't know about. :-)

UPDATE: And you can delete this Post# 5 now that it's fixed. Clean it up.