Bullish to Bearish

[gravityflyer]

Hi all,

I'm fairly confident in how I entered everything into Strategy Builder, but looking at the strategy analyzer it does not appear to be correct.

As a minimum working example, say I want to enter short after a bullish candle and current price falls below open of previous bullish candle. I would assume the proper C# would be:

if ((Close[1] > Open[1]) && (CrossBelow(Close, Open, 1)))

However, when looking at the strategy analyzer chart it appears as though it is entering after bearish candles? Screen shots attached. I've also attached an example of desired entry points circled in blue.

Any guidance would be greatly appreciated!

[NinjaTrader_Jesse]

Hello gravityflyer,

The entries would be based on the condition you made so if they were submitted that would mean the price values at that time allowed the condition to enter.

You could use a Print at the time of the entry to see what the values were at that time to better understand why the condition was true. Alternatively you would have to take a look at the bar values at the time of the circled areas and see how those values work with the condition you made.

[gravityflyer]

I tried a few more tweaks but still getting the same strange result, i.e. it is entering when crossing the close of a previous bullish candle. Almost the exact inverse of my desired strategy!



It's driving me crazy. Lol. Any additional suggestions would be greatly appreciated!

[NinjaTrader_Jesse]

Hello gravityflyer,

Really you need to use a print here to better understand why that condition was true. Prints can be accessed from the actions -> Misc -> Print.

From the chart I can't tell what values were seen for the two parts of your condition. You are comparing the previous bars close vs its open and also checking if the close crossed the open. Without knowing what prices the open and close were for each of those conditions we couldn't really say why the condition as true. I can say that It was true because the prices allowed for it so that may not be the correct condition for the use case.

The cross method with 1 period works by comparing the last and current bars value to check if a crossing happened, to find out why that was true you would need to print both the current and last bars values.

You can also use a chart with the data box to view each bars values however you would need to write those values down so you can apply them to your condition to see why it was true.

[gravityflyer]

Hi Jesse,

First off, thank you very much for taking the time to help solve my issue -- greatly appreciated!

As you suggested, I did a print() of open/close values and confirmed that my coding and I agree that my conditions are not matching my desired result. See attached.




I suppose I should take a step back from this minimal working example and ask what would be the appropriate conditions for my desired short entry point? I assumed that

Close[1]>Open[1]

would determine whether the prior bar was bullish (i.e. close > open), and subsequently

&& CrossBelow(Close, Open,1)

would serve as the trigger of current bar price crossing below the open of the previous bullish bar. Clearly this is incorrect?

[gravityflyer]

By way of follow-up, I think I narrowed my problem down to defining whether the previous candle is bullish (defined as close>open). I did a simple code to enter after a bullish bar:

 protected override void OnBarUpdate()
{
if (BarsInProgress != 0)
return;

if (CurrentBars[0] < 1)
return;

// Set 1
if (Close[1] > Open[1])
{
EnterShort(Convert.ToInt32(DefaultQuantity), "");
}

}

Unfortunately the strategy analyzer reveals some inconsistencies, i.e. sometimes it enters after a bullish candle, but other times it entered after a bearish candle!



Any insight would be greatly appreciated!

[NinjaTrader_Jesse]

Hello gravityflyer,

For the incorrect entries you would need to identify what part of the price condition at that time allowed for it to be true. In a backtest the strategy is evaluated OnBarClose so if the price condition happens but then the next bar is a large drop like pictured it would end up entering within that bars values based on the historical fill engine. You may want to try playing through playback data to see if the condition executes in a more correct way in realtime data. You would otherwise need to determine what the values are in the highlighted yellow area and then see if there is some factor that you can put in additional conditions for to avoid that situation.