Irrational number for decimal parameter increments

[nailz420]

Please see attached screenshot of strategy analyzer. Often the analyzer will start incrementing strategy decimal parameters as irrational numbers.

[NinjaTrader_Jesse]

Hello nailz420,

Are you using specifically a "decimal" type or double? We generally do not use decimal in NinjaScript so if that is the case I would likely want to see an example code used for the input/settings used to reproduce that. Can you test using a double instead to see if the same problem happens?

If you are already using a double, are you able to provide any specific steps which show this or does this happen randomly for you? I see you are using BTC, does this happen for other instrument types like a stock or futures instrument?

I look forward to being of further assistance.

[nailz420]

I use double type for such parameters.

[NinjaTrader_Jesse]

Hello nailz420,

Thank you for clarifying.

Is this something you can reproduce each time or does this happen randomly? Before we continue this would be good to know, we want to try and find a situation where this happens always or frequently so we can isolate whats happening.

Are you using a standard parameter with the standard attributes that you would see generated by the Strategy builder? Can you share the code for property which this is happening to?

Are you seeing any errors in the log when this happens or is there any other indication that the test may have failed to complete?

Do you use a template with this strategy? If so have you tried to clear the template prior to testing?

Additionally knowing if this is only happening for the settings you have shown would be helpful, do you see this on other combinations of instruments/BarsTypes?


I look forward to being of further assistance.

[nailz420]

Hi Jesse,

Attached please find a simple strategy I was able to reproduce this issue with and the strategy template I used. I ran this on 2-3 months of BTCUSD, Range 1000 data.

Regards,
Tim

[NinjaTrader_Jesse]

Hello nailz420,

Thank you for providing that, I was able to see the rounding with that template.

Are you able to see this happen prior to saving a template?

This seems to relate to the template and I was able to find another similar issue however the solution that was suggested was to just remove the template. If you can provide the steps you used prior to saving the template which reproduces this that would be very helpful and would likely be able to be provided as a bug report. The prior issue was unable to be reported as a bug due to the lack of information we had from the user so any details you can provide toward the steps you used would be appreciated.

I was otherwise not able to see the problem when using this strategy without that specific template.


I look forward to being of further assistance.