Restriction/prohibition on some conditions in strategy

[alexstox]

Hello. For example, there is strategy with lots of conditions. To check what conditions work fine, what not, I'd like to add some restrictions/prohibitions. Can I do it in Initialize()?
For example, I 'd like to check strategy performance with and without targetOrder (profit taking via limit order). So, can I set

Initialize()
targetOrder = null;

or something like this?
What you can advice to have opportunity to manipulate some conditions without "Comment"/"Uncomment selection" manually?

[NinjaTrader_ChelseaB]

Hi alexstox,

I'm not quite certain about the targetOrder = null;. If your strategy has code like if (targetOrder != null) { // execute code } this may prevent that condition from executing if you set this to null in Initialize().

However, it seems that you would like groups of conditions to not trigger. I would recommend that you use a variable for this and add a check for the variable to each conditional you are trying to control.

For example:
In #region Variables:
private bool evaluateAll = false; (<- I had to correct that line. Added private bool to the beginning)

In the conditions:
if (evaluateAll == true && Close[0] > Close[1])
{
// execute code
}

Set the variable to true when you would like the conditions to evaluate and false when you don't.

[koganam]

Hello. For example, there is strategy with lots of conditions. To check what conditions work fine, what not, I'd like to add some restrictions/prohibitions. Can I do it in Initialize()?
For example, I 'd like to check strategy performance with and without targetOrder (profit taking via limit order). So, can I set

Initialize()
targetOrder = null;

or something like this?
What you can advice to have opportunity to manipulate some conditions without "Comment"/"Uncomment selection" manually?

Use a boolean parameter, and only call the Set() statements if the boolean variable is true.

[alexstox]

Where can I read more about Set()?

[NinjaTrader_ChelseaB]

Hi alexstox,

.Set() is method that is available to data series. You can read about this in the help guide link below.
http://www.ninjatrader.com/support/h...ries_class.htm

[alexstox]

Please provide any example how Set() can be useful in my question?

[koganam]

Please provide any example how Set() can be useful in my question?

How did you intend to use your targetOrder?

[NinjaTrader_ChelseaB]

Hello alexstox,

Lets say that I am creating a custom data series that will hold the difference between the high and the low so that you can check back on these values.
This will be similar to looking back at past Close values.

First you can create a custom data series.

In #region Variables:
private DataSeries myDataSeries;

In the Initialize() method:
myDataSeries = new DataSeries(this, MaximumBarsLookBack.Infinite);

Now that the data series has been initialized you can set a value for this in OnBarUpdate
myDataSeries.Set(High[0]-Low[0]);

Then to call the data back a bar later, use myDataSeries[1]. (myDataSeries[barsAgoValue])


Plots on a chart are created from a dataseries. NinjaTrader will handle the creation of this for you.

To add a plot in Initialize() write:
Add(new Plot(Color.Orange, "myPlot"));

This will create a Value variable that you can use to set the plot value.
Value.Set(High[0]);

This code will plot connecting the high of the bars.

[alexstox]

Well, there is strategy, that is full of conditions: filters, enters, drawn objects etc. Sometimes it's hard to "Comment/Uncomment" selection to turn off some rules/conditions, because they are in different places. Even with not big script of 2000 rows of code. Especially when you changed something and want to redo/undo changes.
So, in this case it would be great to have opportunity to manage some conditions without boolean if() before every condition.
Is there some abilities in NT script? Maybe some restrictions in Initialize()? Or it's only via switch

switch (expression)
{  case value1:
      break;
  case value2:
      break;
   default:
      break;
}

[koganam]

Well, there is strategy, that is full of conditions: filters, enters, drawn objects etc. Sometimes it's hard to "Comment/Uncomment" selection to turn off some rules/conditions, because they are in different places. Even with not big script of 2000 rows of code. Especially when you changed something and want to redo/undo changes.
So, in this case it would be great to have opportunity to manage some conditions without boolean if() before every condition.
Is there some abilities in NT script? Maybe some restrictions in Initialize()? Or it's only via switch

switch (expression)
{  case value1:
      break;
  case value2:
      break;
   default:
      break;
}

A switch statement with an enum is one possibility, yes.

[NinjaTrader_ChelseaB]

Hello alexstox,

The switch is almost like an if statement that compares only one variable to a series of values.

It may be possible to have your code use this switch, but I can only imagine this working if you have altered versions (duplicate code sections) of the completed code in each case of the switch.

It may work for what you want, but I think its going to require some restructuring of your code.