Adding Filter: SPY above 40 SMA

01439

#1

8/15/2019 6:47 PM

I am new to WealthLab coding and am trying to add a simple piece of code to below. Have looked through the forum and found some help but cannot get it to work?

All I want to do is say that SPY must be greater than 40 SMA.

CODE:
Please log in to see this code.

Eugene

#2

8/15/2019 8:35 PM

This question has been raised numerous times on the forum, for example:

Buy/sell signal using external symbol SPY or .SPX
SPY criteria

QUOTE:
All I want to do is say that SPY must be greater than 40 SMA.

You're now authorized to use Community.Rules with conditions like:

* External Symbol Price is above (below) its Moving Average

This is the simplest option which requires no programming. Anyway, here's code sample as requested:

CODE:
Please log in to see this code.

Size:

Color:

This question has been raised numerous times on the forum, for example:

[link=https://www.wealth-lab.com/Forum/Posts/Buy-sell-signal-using-external-symbol-SPY-or-SPX-38951]Buy/sell signal using external symbol SPY or .SPX[/link]
[link=https://www.wealth-lab.com/Forum/Posts/SPY-criteria-30220]SPY criteria[/link]

[quote]All I want to do is say that SPY must be greater than 40 SMA. [/quote]
You're now authorized to use [link=http://www2.wealth-lab.com/WL5WIKI/CommunityRules.ashx]Community.Rules[/link] with conditions like:

[i]* External Symbol Price is above (below) its Moving Average[/i]

This is the simplest option which requires no programming. Anyway, here's code sample as requested:

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

namespace WealthLab.Strategies
{
	public class MyStrategy : WealthScript
	{
		protected override void Execute()
		{			
			var spy = GetExternalSymbol("SPY".Trim(), true);
			var spyClose = spy.Close;
			var spyMA = SMA.Series(spyClose, 40);
			
			DataSeries roc = ROC.Series(Close,20);
			DataSeries BBUp = BBandUpper.Series( Close, 100, 2 );

ChartPane paneROC = CreatePane(75,true,true);
			PlotSeries(paneROC,roc,Color.SlateGray,LineStyle.Histogram,20);
			PlotSeries(PricePane, BBUp, Color.Blue, LineStyle.Solid, 2 );
			PlotSeries(PricePane, (Close - ATR.Series(Bars, 5) * 3.50) >> 1, Color.Red, LineStyle.Solid, 1);

for(int bar = GetTradingLoopStartBar(101); bar < Bars.Count; bar++)
			{
				if (IsLastPositionActive)
				{
					Position p = LastPosition;
					if (p.EntrySignal.Contains("Group1|"))
					{
						double Stop = p.EntryPrice * (1 - 30.00 / 100.0d);
						SellAtStop(bar + 1, p, Stop, "Group1");
					}
					if (p.EntrySignal.Contains("Group2|"))
					{
						SellAtStop(bar + 1, p, Close[bar] - ATR.Value(bar, Bars, 5) * 3.50, "Group2");
					}

}
				else
				{
					if( spyClose[bar] > spyMA[bar] )
						if (roc[bar] > 10 )
						{
							if (CrossOver( bar, Close, BBUp ))
							{
								BuyAtClose(bar, "Group1|Group2|");
							}
						}
				}
			}
		}
	}
}[/code]

01439

#3

8/15/2019 8:48 PM

Thank You Eugene

Eugene

#4

8/15/2019 9:06 PM

At your service.

LenMoz

#5

8/15/2019 9:32 PM

Eugene, why did you express the SPY variables as "var" in stead of DataSeries? I wrote the code as I would have written it and see no difference.

CODE:
Please log in to see this code.

Eugene

#6

8/15/2019 9:39 PM

Len, it's just syntactic sugar (and less room for error for new users).

superticker

#7

8/16/2019 1:41 AM

QUOTE:
why did you express the SPY variables as "var" in stead of DataSeries?

QUOTE:
less room for error for new users

As us computer professionals on the forum know, strongly typed languages (like C#) were specifically created to reduce errors. The intent is to discover the errors (and spelling typos) at compile time, not at run time. I think that's the subtle point being made in Post# 5.

There are situations where the returned type is "unknown" like in a Linq query or data read from an Excel XML file when "var" may be necessary; otherwise, we want to use the power of a strongly typed language to catch errors early (compile time).