Greetings
I'm in the final days of my Wealth-Lab 8 trial. So far, I've been able to test every dataset without any problems. However, since today, when I try to backtest datasets with over 100 symbols, I only see the message "In Demo Mode you can backtest a maximum of 100 symbols at once."
Has something changed in Build 150? If so, what's the reason for this?
Thanks
I'm in the final days of my Wealth-Lab 8 trial. So far, I've been able to test every dataset without any problems. However, since today, when I try to backtest datasets with over 100 symbols, I only see the message "In Demo Mode you can backtest a maximum of 100 symbols at once."
Has something changed in Build 150? If so, what's the reason for this?
Thanks
Rename
Yes, we've added this limitation to demo mode because we lifted other restrictions that don't make as much sense in a modern tech environment.
Okay, I find this very unfortunate for all the potential new Wealth-Lab customers who want to check out the software. Especially when it comes to illustrating the issue of survivorship bias, I don't think this limitation is well-designed. The very essence of Wealth-Lab is being able to see the differences between a strategy and Wealth-Lab's survivorship-bias-adjusted dataset compared to the current dataset. All of that is now gone.
WL Data Sets
S&P 100 = 206 symbols
S&P 500 = 1048 symbols
Nasdaq 100 = 331 symbols
From now on, there's no way to get a basic impression of Wealth-Lab.
It doesn't matter to me since my trial expires tomorrow anyway, but I find it very disappointing for potential new customers.
WL Data Sets
S&P 100 = 206 symbols
S&P 500 = 1048 symbols
Nasdaq 100 = 331 symbols
From now on, there's no way to get a basic impression of Wealth-Lab.
It doesn't matter to me since my trial expires tomorrow anyway, but I find it very disappointing for potential new customers.
Wouldn't it be sensible and possible to lift the restriction, at least for the WL datasets?
We will consider it, it does make sense.
I've lifted the restriction for WealthData DataSets in demo mode for Build 151, but we'll still limit these backtests to 10 years of history in demo mode. We need some limitations in demo mode to prevent certain abuse scenarios.
Good morning, dear Glitch!
That's a good decision, although I don't understand the part about Build 51. Do you mean Build 151?
Ultimately, I'm wondering how this could be misused? You can't run WL on a virtual machine, and it's unlikely anyone would go to the trouble of having dozens of computers just to save on your license.
I can only speak for myself. I was looking for bias-cleaned data and that's how I came across you. Here in Germany, some people use Traderfox, but NONE of them use data without it, so it's all child's play. If someone becomes aware of you, they'll naturally want to take a close look at the datasets like the S&P 500 and Nasdaq 100, and of course, for a period of more than 10 years. Ultimately, the decision is yours.
Thanks for your reply.
That's a good decision, although I don't understand the part about Build 51. Do you mean Build 151?
Ultimately, I'm wondering how this could be misused? You can't run WL on a virtual machine, and it's unlikely anyone would go to the trouble of having dozens of computers just to save on your license.
I can only speak for myself. I was looking for bias-cleaned data and that's how I came across you. Here in Germany, some people use Traderfox, but NONE of them use data without it, so it's all child's play. If someone becomes aware of you, they'll naturally want to take a close look at the datasets like the S&P 500 and Nasdaq 100, and of course, for a period of more than 10 years. Ultimately, the decision is yours.
Thanks for your reply.
>> You can't run WL on a virtual machine<< You can now
Hmm, why are you allowing virtual machines? That wasn't possible before and obviously makes abuse easier.
Not allowing virtual machines and leaving everything else as is? Isn't that an option?
Not allowing virtual machines and leaving everything else as is? Isn't that an option?
I don’t want to get into too many specifics here, but this was decided after much careful consideration.
Your Response
Post
Edit Post
Login is required