Changing the inputs in the menu

[Aporshnev]

Hi,

I have a strategy with a few inputs, which are the position entry prices. Depending on market conditions I change them before starting the strategy. In the basic script in strategy builder the inputs are fixed on exact meanings.

And as I see on the test chart - it works. There are trade markers as you may see.


But if I change the inputs in the start menu (without reprogramming the script in the builder itself) - the new prices do not work. However, the logic of the strategy remains same.



Maybe, because there are commas, but script can read dots... Maybe some other reasons? What may be the problem?

[NinjaTrader_PaulH]

Hello Aporshnev,

Thanks for your post.

If your strategy is working with the defaults that appear to be set with commas I would expect new values to be treated the same.

Can you post a screenshot of where the inputs are used in the condition builder?

[Aporshnev]

Here you go: Set1; Set2; Set3 a so on...

[Aporshnev]

The logic is associated with the price graterEqual of UserInput wich I call "LEVEL"

[NinjaTrader_PaulH]

Hello Aporshnev,

Thanks for your reply.

I don't see anything obvious in your conditions that would be an issue.

What I suggest at this point would be to have the strategy builder print out what values it is working with.

I've attached a short video that shows a process of building a print statement for debugging purposes. In your case I would suggest printing out the various inputs to see if they match your defaults and then to see that they match when you input the new values.

https://paul-ninjatrader.tinytake.com/tt/MzYyODQyNV8xMDk5MDc5Nw

[Aporshnev]

Paul, Thnx for the video. It appears that given the logic GreterEqual, I need to place my price levels ascending if I play short, so that the first level should be the closest to the market. If the inputs scheduled descending, then script is confused and doesn`t work...

[koganam]

Depends on what you are doing. Anything being triggered on multiple conditions that should be greater than some values, must be evaluated from the highest to the lowest. That is the only way mathematically and logically that you can ensure that the conditions fall through to lower values. Conversely, conditions triggered by something being lower than values must be evaluated from the lowest to the highest. Keyword: MUST.

[NinjaTrader_PaulH]

Hello Aporshnev,

Thanks for your post.

I agree with member Koganam's reply in post #7.

The order/sequence must be coded relative to the direction.