The newer version of heikinAshi indicator is incompatible or wrong (cf.
https://bitly.com/xSIG2o) As per documentation, the result array contains prices in the following order: OPEN, CLOSE, MIN, MAX.
--- a/tst_rc2_14022012_013010.csv 2012-02-13 20:00:10.000000000 +0000
+++ b/tst_rc2_14022012_013110.csv 2012-02-13 20:01:10.000000000 +0000
@@ -1,1070 +1,1070 @@
2012.02.13 20:30:10,2012-02-06 00:00:01 [GMT]
2012.02.13 20:30:10, HA [
- [1.31252, 1.31246, 1.31241, 1.31253],
- [1.31246, 1.31240, 1.31236, 1.31246],
- [1.31240, 1.31252, 1.31240, 1.31264]]
+ [1.31253, 1.31246, 1.31253, 1.31241],
+ [1.31249, 1.31240, 1.31249, 1.31236],
+ [1.31244, 1.31252, 1.31264, 1.31240]]
2012.02.13 20:30:10, DC [
[1.31563, 1.31563, 1.31563],
[1.31563, 1.31110, 1.31110]]
2012.02.13 20:30:10, T3 [1.31561, 1.31552, 1.31535]
The MIN and MAX are transposed in newer version.
Why not hOPEN, hHIGH, hLOW, hCLOSE, or an order and, or naming like OHLC?
Seems this indicator has been developed/maintained quite carelessly.
Moreover, most of the other indicators, see the DC (Donchian Channels) above return arrays in wrong order; try using
numberOfCandlesBefore = 2 or more for any indicator you will get a transposed array except for the heikinAshi.
