Cone asked me to mention this error message here that pops up in SignalsPublisher when I try to connect a WealthLab META strategy to WealthSignals.
It seems that the connection between WealthLab and WealhSignals is established correctly via the Publisher, the open positions are detected correctly, the historical data is loaded correctly but the following error occurs during the Running Backtest:
Error: Object reference not set to an instance of an object
I use 4 different strategies here in WealthLab as a META strategy. All 4 strategies have their own portfolio.
In addition, I have created my own DataSet, in which ALL shares from the 4 sub-strategies occur. Can the error message be due to the fact that each strategy has its own portfolio?
Regards Christian
It seems that the connection between WealthLab and WealhSignals is established correctly via the Publisher, the open positions are detected correctly, the historical data is loaded correctly but the following error occurs during the Running Backtest:
Error: Object reference not set to an instance of an object
I use 4 different strategies here in WealthLab as a META strategy. All 4 strategies have their own portfolio.
In addition, I have created my own DataSet, in which ALL shares from the 4 sub-strategies occur. Can the error message be due to the fact that each strategy has its own portfolio?
Regards Christian
Rename
It's definitely the DataSet that's the issue. The Signals Publisher's configuration allows only for a single DataSet. One position sizing rule is also an incompatibility. Let's see what @Glitch thinks about a MetaStrategy overriding those settings for use in the Signal Publisher.
A MetaStrategy simply isn’t compatible with the Signals Publisher. I need to add some messaging to indicate this and prevent them from being added.
Your Response
Post
Edit Post
Login is required