We are currently trying Monte Carlo simulations on simple dip buyer market systems.
With the "Equity Curve Scramble" method we can make good evaluations.
With all other 4 methods we get no data. If you click on "Start" you can see that Wealth Lab is not "working".
What could be the cause?
With the "Equity Curve Scramble" method we can make good evaluations.
With all other 4 methods we get no data. If you click on "Start" you can see that Wealth Lab is not "working".
What could be the cause?
Rename
Does your CPU peg to 100% and does your "Runs" number start increasing like here?
Dip buying strategies will have possibly tens or hundreds of thousands of positions to process so it could take significant time to complete the analysis.
Dip buying strategies will have possibly tens or hundreds of thousands of positions to process so it could take significant time to complete the analysis.
The number of runs remains at 0. It also doesn't appear that anything is running in the background.
I've now waited 10 minutes and still no data. The Simulations tab remains empty.
We tried this parallel on different computers. Locally and on virtual servers (with 8 cores and 16GB ram). Should not be a hardware problem.
Always with the same results = 0.
I've now waited 10 minutes and still no data. The Simulations tab remains empty.
We tried this parallel on different computers. Locally and on virtual servers (with 8 cores and 16GB ram). Should not be a hardware problem.
Always with the same results = 0.
What simple dip buyer strategies can demonstrate this and on what data?
No data...
I used KarlD77's strategy and settings, and I got the same outcome as KarlD77 - no runs, no results, nothing.
I think there must be a bug with Monte Carlo when using block strategies. We'll look into it.
We're not able to duplicate the problem. When it happens are there any messages in the Log Viewer?
Hello to all.
The problem is not only related to block strategies and it is not new. Previously, it showed inconsistent behaviour in my environment, i.e. sometimes it worked (most of the time) and sometimes it did not. If I reloaded the strategy and tried again, it usually worked fine.
But since version 32 (maybe 31) it just doesn't work here either.
My best guess would be to check the multithreading logic for, say, two reasons.
The first is that this behaviour can be very different in different user environments.
The second is just an observation that sometimes it looks like it starts but stops immediately. In such situations, the run counter starts but is reset to zero ad hoc and the process stops. (It feels like threads are simply terminated by a master thread. You can look for race conditions.).
I find this analysis tool very useful and would be happy if you could go deeper into the topic, especially the multithreading implementation. Thank you very much.
The problem is not only related to block strategies and it is not new. Previously, it showed inconsistent behaviour in my environment, i.e. sometimes it worked (most of the time) and sometimes it did not. If I reloaded the strategy and tried again, it usually worked fine.
But since version 32 (maybe 31) it just doesn't work here either.
My best guess would be to check the multithreading logic for, say, two reasons.
The first is that this behaviour can be very different in different user environments.
The second is just an observation that sometimes it looks like it starts but stops immediately. In such situations, the run counter starts but is reset to zero ad hoc and the process stops. (It feels like threads are simply terminated by a master thread. You can look for race conditions.).
I find this analysis tool very useful and would be happy if you could go deeper into the topic, especially the multithreading implementation. Thank you very much.
In the cases above (paul1986 duplicated), "0 Runs" indicates that it's not even starting.
If it starts an stops, almost certainly information will be available in the Log Viewer.
If it starts an stops, almost certainly information will be available in the Log Viewer.
Ok, I definitely don't want to mix things up. At the moment, nothing is happening at all, as others also report. It's just that sometimes it flashes briefly and then nothing happens. The result is 0 runs in both scenarios. Unfortunately, I don't have any information in the log viewer that indicates a problem.
I'm currently playing around with the backtest settings and various setups and have had no luck finding anything significant.
So, I've been looking at the change log of the Monte Carlo extension and the WL builds. Build 31 and build 27 worked on the "LimitOnClose" behaviour that was introduced in Monte-Carlo build 2. I know this is just another guess, but according to the build information there is a small chance of finding something.
So, I've been looking at the change log of the Monte Carlo extension and the WL builds. Build 31 and build 27 worked on the "LimitOnClose" behaviour that was introduced in Monte-Carlo build 2. I know this is just another guess, but according to the build information there is a small chance of finding something.
Hey everyone, unfortunately there was a change in a Backtester method signature that broke the connection to Monte Carlo Lab, we just need to rebuild MC Lab and will do so for the next release cycle. I'm away this week but will get this out early next week.
Your Response
Post
Edit Post
Login is required