Here we have tried to answer some common questions about our products: Backtesting, Forward Testing, & Live Execution
A user can deploy their strategy anytime after 8:45 am and before market closes on days when the market is open. There are 2 ways where a user can stop a strategy and re-deploy it.
No, you will not be able to make any changes to the parameters/conditions of a strategy after it has been activated & deployed. Once you activate a strategy, we save the conditions/parameters associated with that strategy. Any changes that you make to the strategy after it has been activated will not be reflected on your deployed strategy. To make any changes to your deployed strategy, you will first have to stop it by either Squaring off or Switching to manual. Thereafter, you can deploy the newly modified strategy.
The Quantity multiplier multiplies the number of lots in each leg. If your Overall settings e.g. Overall SL, Overall Profit, and Overall TSL, are based on MTM, then they are also multiplied.
Many users buy hedges for margin benefit. In order to make sure that your sell orders are executed after your buy orders and you are able to get the margin benefit, we have added a feature of “Entry Order Delay” in your execution settings. Your execution settings open up as soon as you click on the “Activate” button for a strategy. Under these settings we have given a time dial where you can you can delay the entry of any of your legs by 0 – 50 secs.
Our backtest data is updated usually after 12 am that night, so the beginning of the next day. We go through a rigorous process of checking the data from multiple sources before it is updated to our database.
Yes, this was a conscious design choice. Even though the lot size changed over time, it makes more sense to keep it constant while backtesting using historical data. When evaluating strategies, a Rs 1 move in your favour shouldn’t show Rs 25 profit on one day, and Rs 50 profit on some other day, even though market conditions remain the same. Different lot sizes in backtests can obfuscate the signal, so we advise you to keep it constant for the duration of the entire backtest.
This was a design choice – we keep slippages 0 so as not to obfuscate the strategy result. Instead we give the user the ability to add slippage which is closest to the slippages they see in their execution. So you can add whatever slippage you think is appropriate on the backtest results. You can also change the value of slippages and re-calculate your results to see how sensitive your strategy results are to slippages.
Max trades in a drawdown: Max trades in a drawdown shows the maximum number of consecutive trades your strategy was in a drawdown phase. This drawdown period can be different from the period where your strategy incurred the maximum drawdown (monetarily), which is shown in the first field i.e. Days of Max Drawdown.
Max trades in a drawdown shows the max amount of trades taken to recover any drawdown which may or may not correspond to the maximum drawdown monetarily.
Hello and welcome to the detailed pricing page for AlgoTest. You will find a breakdown of our pricing model here.…
Introduction Options trading can be lucrative for investors looking to diversify their portfolios and take advantage of market opportunities. However,…
Introducing Our New Error Handling Feature At AlgoTest, we're excited to announce a significant upgrade to our platform with the…
Exciting news for our traders: Candle Close Implementation has arrived at AlgoTest! To understand AlgoTest’s implementation of Candle Close here…
At AlgoTest, we are constantly innovating to bring our users the most advanced and user-friendly trading tools. So we are…
In our bid to provide additional support to traders in making trading decisions, we have now launched the feature 'Margin…
This website uses cookies.