If we find that double-clicking is too much work, it is possible to mark Sync chart on select option in Analysis window settings menu:Īnd then single click to select a chart is enough to sync the symbol in the chart. When we want to sync a chart with the selected symbol in the Analysis results list, it is enough just to double-click on the particular line in the list and AmiBroker will automatically switch the selected symbol and interval to match the Analysis window.Īdditionally, when we browse through Scan or Backtest results, double-clicking would be an equivalent of Show arrows for all raw signals option from the context menu and would display trading arrows in the chart to match the signals generated by the formula. The above operations do not affect the underlying database at all – the prices are overridden only for the purpose of calculation of this particular formula and other charts / indicators are not affected at all.
Then – when we call MACD() function which uses Close as input – it will be based on the modified values.
#Amibroker file examples code#
The code first calculates the custom array (we use just use average of High and Low prices in this example, but of course the calculations may be more complex), then assigns the result of these calculations to Close overriding the regular values stored in close array. Plot ( Signal ( 12, 26, 9 ), "Signal", colorBlue ) Plot ( MACD ( 12, 26 ), "MACD", colorRed ) calculate our function, MACD and Signal in this case Global SaveO, SaveH, SaveL, SaveC, SaveV As a simple example, let us consider calculating MACD indicator out of average of High and Low prices as input. For this purpose, it is enough to override OHLC arrays (or just Close if the indicator only uses Close as input) within the code before calling given function and assign our custom array. Plot ( RSIa ( customArray, 14 ), "RSI from (H+L)/2", colorRed )īut many of the built-in indicators available in AFL as functions refer indirectly to standard OHLC arrays and their parameters do not offer array argument as one of inputs.įortunatelly there is an easy way to provide custom array as input for any other built-in functions.
For example RSI from average of High and Low prices could be written as follows: customArray = ( High + Low ) / 2 In this case it is very easy to calculate the indicator based on user defined value. Some functions like RSI or CSI have additional versions (RSIa, CCIa respectively) that accept custom input array. Sometimes we may want to calculate indicators based not only on standard OHLC prices but on some other user-definable values. In Portfolio tab, enter 0 in Limit trade size as % of entry bar volume box. Allow position size shrinking – turn it On.set Periodicity to the appropriate interval.Using the following settings may be helpful to minimize chances of not entering trades because of various constraints: Once you run backtest in Detailed Log mode you will be able to find out exact reasons why trades can not be opened for each and every bar: To check what is going on, it is best to switch Report mode to Detailed log and re-run backtest. the constraints set in the settings prevent trades from being opened mainly because requested position size is too big or too small. If Scan works fine and returns trading signals, but backtester still does not produce any output, it usually means that the settings are wrong, i.e. If there are none, then we need to check the formula and make sure that data interval we are working on are correct (in Periodicity in Analysis->Settings->General). This allows us to check if we are getting any Buy or Short signals at all. To verify if we are getting any signals – the first thing to do is to run a Scan. our settings do not allow the backtester to take any trades.our system does not generate any entry signals within the tested range.The main potential causes are the following: When we run backtest and get no results at all – there may be several reasons of such behaviour.
0 kommentar(er)
