- Drop a compiled strategy (1 or 5-minutes interval) with at least one parameter into SM
- change the default value to something else.
- Wait for the strategy to run then through the debugger look at the value. It is not changed.
this almost makes parameter setting outside of backtesting useless.
- change the default value to something else.
- Wait for the strategy to run then through the debugger look at the value. It is not changed.
this almost makes parameter setting outside of backtesting useless.
Rename
Confirmed.
Fixed in Build 9.
Thank you
There is a new broken issue in build 11. It used to work in build 10.
if you drop a strategy with a parameter twice in SM and change the value of the parameter of one instance it will change the value of the parameter in the other one.
to repro you should save the workspace and reopen and check the parameter values again.
if you drop a strategy with a parameter twice in SM and change the value of the parameter of one instance it will change the value of the parameter in the other one.
to repro you should save the workspace and reopen and check the parameter values again.
Is this new issue a compiled strategy issue? If not it may be optimal to start a new topic.
Yes. it is only repro in compiled strategies.
Apparently parameters are saved per strategy. As a workaround you could create a copy of the compiled strategy under a different class / name?
I can't confirm this one. I dropped the same compiled strategy into the SM and changed the parameter for each one. As expected, the ones with the lower parameter values produced more signals. I even saved it as a Workspace and the saved parameter values were correctly re-established.
Parameter settings here are NOT saved per strategy, they are saved with the Strategy Monitor Item.
Parameter settings here are NOT saved per strategy, they are saved with the Strategy Monitor Item.
Your Response
Post
Edit Post
Login is required