TypeConverter in Optimization

[aslane]

I am aware of the type converter sample, and have used portions of it to hide/show properties. My question is how can this be applied when in the optimizer? For example, if I have a bool property, I want to show other properties if it is set to True or Optimize.

[NinjaTrader_Jesse]

Hello aslane,

Thank you for the post.

I wanted to clarify, are you saying that currently the type converter is not working at all in just the optimization window or are you asking how to watch for both true/Optimize?

Do you also have a sample of what you made that I can take a look at? It looks like our strategy sample in the help guide only contains the type converter but is not ready to test for this situation, if you have an existing sample that would be helpful so I don't need to recreate this over again.


I look forward to being of further assistance.

[aslane]

how to watch for both true/Optimize?

Yes.

I do not have simple example, but just create simple strat with bool that hides one other prop.

[NinjaTrader_Jesse]

Hello aslane,

Thank you for the reply.

I will test this when I find time to recreate what you described and provide any information I uncover to development for review.

Please let me know if I may be of further assistance.

[aslane]

As far as I can tell, this does not work at all in the optimizer (works fine in Backtest). If triggering property starts out false, the other property is removed as expected. However, when you flip the boolean to True or Optimize, the second hidden property is not displayed. The triggering property does have the RefreshProperties attribute specified. I'll see if I can provide a basic example.

[aslane]

Attached is simple example that shows issue.

[NinjaTrader_Jesse]

Hello aslane,

Thank you for the reply,

I was able to form a sample earlier in the day and have already reported this. I will reply back here if I receive more details surrounding this situation.

I look forward to being of further assistance.

[NinjaTrader_Jesse]

Hello aslane,

I wanted to follow up as I received some further input from QA here. It looks like this is to be expected based on how the optimizer property grid works. In the situation where you have NinjaScriptProperty attribute applied to the property that will disable the custom type converter in this use case. To still utilize the type converter in the optimizer would require removing the NinjaScriptProperty attribute from that property specifically.

A work around could be to make an extra bool property for the purpose of toggling the others, this property would not be optimized and is strictly to control the properties. The hiding works as long as the property which toggles is not an optimization property. I realize this would not cover all cases if you have more than one toggle that could be problematic. I will put in a feature request to expand this area.

I look forward to being of further assistance.

[aslane]

Thanks that makes sense. However, this does not really help in the general case as you explain. I already do use bools to enable the groups, but those bools need to be optimizable also.For example, you might have a group of items that can all be turned on/off together in different combinations. This is really an advanced item, but when building large frameworks, this is really required in order to increase the usability for the end user. Please add the feature request.

[mps227]

Hello, I was curious, has the status of this challenge changed at all? The ability to show / hide numerous properties in my strategies has really made it cleaner / easier for me to work during normal strategy use, but when I want to work on Optimization in the Strategy Analyzer the inability to show / hide properties makes things a bit of a mess.

Thanks!

[NinjaTrader_Jesse]

Hello mps227,

This is currently still the case, the optimizer is not set up to utilize the custom type converters/property descriptors like a standard property grid would use.

[donto]

Hello There Jesse

you mentioned in an earlier post here that you would put in a feature request to get this added.
what is the status of this feature request and where is it in the voting rank ?
I would not see this as a feature request more a issue that should be solved.

[NinjaTrader_Jesse]

Hello donto,

This is still just a feature request but has not been changed since the last post in this thread. In this case this is expected for the reasons mentioned here and also in the other post where I had replied to you this morning. The strategy analyzer properties grid works differently than the other grids in the platform to support optimization, manipulating the property descriptor collection or doing other advanced manipulation is removed when the [NinjaScriptProperty] is used so the property can be rebuilt to support optimization.