Support Board
Date/Time: Fri, 28 Feb 2025 09:06:19 +0000
Parallel backtesting with ACSIL
View Count: 514
| [2021-08-11 02:20:19] |
| User785723 - Posts: 58 |
|
Let's say we have a main study (S1) with a trading strategy written in ACSIL. We can change one input of the main study with another study, namely S2. The study S2 also runs the backtest of S1 for a number of values for the input. How this works is that we first add S1, then add S2. As soon as S2 is added to the chart, it begins to replay S1 with the first value of the input. After the first backtest is done, it begins to replay the second input value and so on. What if we want to do the backtests in parallel (at the same time) with multiple Sierra instances? Is it doable in ACSIL? Please share the related documentation if any. |
| [2021-08-11 13:58:25] |
| John - SC Support - Posts: 38259 |
|
It is not possible to control different Sierra Chart instances with a single DLL. Each Sierra Chart instance is its own executable, therefore there is no "cross-talk" between the programs, and there is nothing built into the system to allow this to occur.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2021-08-12 15:11:39] |
| ForgivingComputers.com - Posts: 1015 |
|
What if we want to do the backtests in parallel (at the same time) with multiple Sierra instances? Is it doable in ACSIL? Please share the related documentation if any.
As was mentioned in message #2, different instances don't have direct methods of communicating with each other. It is possible to create an ACSIL study to write live data to a file and have another study, in a different instance, read the file. Direct Message me for a quote on a turnkey solution. |
To post a message in this thread, you need to log in with your Sierra Chart account: