Difference between revisions of "Comparing Charts to Scanner"

From MultiCharts
Jump to navigation Jump to search
(Created page with "==Comparing the instrument values on charts and in the scanner== When you have one and the same symbol used in the scanner and on a chart it is natural to start comparing the...")
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Comparing the instrument values on charts and in the scanner==
+
==Comparing instrument values on charts and in scanner==
When you have one and the same symbol used in the scanner and on a chart it is natural to start comparing the data values in both windows. This is when you can spot slight differences. As a rule they are caused by the difference in the symbol settings in these windows. Cross-check that the following settings are identical:
+
When you have one symbol, that is the same, in both the scanner and on a chart it is natural to start comparing the data values in both windows. This is when you can spot slight differences. As a rule they are caused by the difference in the symbol settings in these windows. Cross-check that the following settings are identical:
 
# Data source and symbol;
 
# Data source and symbol;
 
# Chart type - regular or [[:category:Non-Standard_Chart_Types|non-standard]];
 
# Chart type - regular or [[:category:Non-Standard_Chart_Types|non-standard]];
Line 9: Line 9:
 
# [[Data_Range|Data Range]]* - should be specified as Bars/Days Back on the chart because there’s no From-To data range in the scanner; make sure that the pin position is identical in both cases;  
 
# [[Data_Range|Data Range]]* - should be specified as Bars/Days Back on the chart because there’s no From-To data range in the scanner; make sure that the pin position is identical in both cases;  
 
# [[Time_Zone|Time Zone]]*.
 
# [[Time_Zone|Time Zone]]*.
The easiest way to guarantee that the settings are similar is to create a chart for a symbol used in the scanner! [[Working_with_Grid#Creating_Chart_Directly_from_a_Scanner_Window|See here}. <br>
+
The easiest way to guarantee that the settings are similar is to create a chart for a symbol used in the scanner! [[Working_with_Grid#Creating_Chart_Directly_from_a_Scanner_Window|See here]]. <br>
<div style="background-color: #e0ffff;">'''Note:''' It is worth mentioning that even with all of these settings being identical, the values in the scanner might not coincide with the data series on the chart. That’s because of the fact that the scanner uses a special realtime source for the data – the same as the one that’s used for the Status line of the chart. And in case your data provider sends different status line values compared to the chart values, there’s nothing that can be done to rectify this.</div>
+
<div style="background-color: #e0ffff;">'''Note:''' It is worth mentioning that even with all of these settings being identical, the values in the scanner might not coincide with the data series on the chart. That is because the scanner uses a special realtime source for the data – the same as the one that is used for the Status line of the chart. And in case your data provider sends different status line values compared to the chart values, there is nothing that can be done to rectify this.</div>
<div style="background-color: #b6e1fc;">'''Note 2:''' the following data sources don’t have status line values: ASCII Mapping, CSI, Free Quotes, Metastock.</div>
+
<div style="background-color: #b6e1fc;">'''Note 2:''' The following data sources do not have status line values: ASCII Mapping, CSI, Free Quotes, Metastock.</div>
<div style="background-color: #87cefa;">'''Note 3:''' Avatrade, LMAX, OANDA, Universal DDE don’t supply or return zeros for some or all of these values to status line: Open, High, Low, Prev, Volume.</div>
+
<div style="background-color: #87cefa;">'''Note 3:''' Avatrade, LMAX, OANDA, Universal DDE do not supply or return zeros for some or all of these values to status line: Open, High, Low, Prev, Volume.</div>
  
 
==Comparing indicator values on charts and in scanner==
 
==Comparing indicator values on charts and in scanner==
If there’s a discrepancy in the chart and scanner indicator’s calculations, then it may be related to:
+
If there is a discrepancy in the chart and scanner indicator’s calculations, it may be related to one of the following:
* different symbol settings (see point 1 of this article);
+
* different symbol settings ([[Comparing_Charts_to_Scanner#Comparing_instrument_values_on_charts_and_in_scanner|see point 1 of this article]]);
 
* different indicator settings. In this case compare and adjust:
 
* different indicator settings. In this case compare and adjust:
 +
 
# the [[Indicator_Settings#Setting_Input_Values|input values]];
 
# the [[Indicator_Settings#Setting_Input_Values|input values]];
 
# the [[Indicator_Settings#Setting_Maximum_Bars_Back|Max Bars Back setting]];
 
# the [[Indicator_Settings#Setting_Maximum_Bars_Back|Max Bars Back setting]];
# the [[Indicator_Settings#Advanced_properties|Update on every tick option state]];
+
# the [[Indicator_Settings#Advanced_properties|Update on every tick option]] state;
# the [[Indicator_Settings#Advanced_properties|Skip identical ticks option state]].
+
# the [[Indicator_Settings#Advanced_properties|Skip identical ticks option]] state.
 +
 
 +
Also verify that you did not use an additional data series in the indicator’s calculation on the chart, because in the Scanner you can only use Data1 for calculations. If you still observe the differences in the indicator values, cross-check the logic of the indicator.
 +
 
 +
[[Category: Real-Time Market Scanner]]

Revision as of 13:57, 30 October 2019

Comparing instrument values on charts and in scanner

When you have one symbol, that is the same, in both the scanner and on a chart it is natural to start comparing the data values in both windows. This is when you can spot slight differences. As a rule they are caused by the difference in the symbol settings in these windows. Cross-check that the following settings are identical:

  1. Data source and symbol;
  2. Chart type - regular or non-standard;
  3. Resolution;
  4. Quote Field;
  5. Sessions;
  6. Build volume on;
  7. Data Range* - should be specified as Bars/Days Back on the chart because there’s no From-To data range in the scanner; make sure that the pin position is identical in both cases;
  8. Time Zone*.

The easiest way to guarantee that the settings are similar is to create a chart for a symbol used in the scanner! See here.

Note: It is worth mentioning that even with all of these settings being identical, the values in the scanner might not coincide with the data series on the chart. That is because the scanner uses a special realtime source for the data – the same as the one that is used for the Status line of the chart. And in case your data provider sends different status line values compared to the chart values, there is nothing that can be done to rectify this.
Note 2: The following data sources do not have status line values: ASCII Mapping, CSI, Free Quotes, Metastock.
Note 3: Avatrade, LMAX, OANDA, Universal DDE do not supply or return zeros for some or all of these values to status line: Open, High, Low, Prev, Volume.

Comparing indicator values on charts and in scanner

If there is a discrepancy in the chart and scanner indicator’s calculations, it may be related to one of the following:

  1. the input values;
  2. the Max Bars Back setting;
  3. the Update on every tick option state;
  4. the Skip identical ticks option state.

Also verify that you did not use an additional data series in the indicator’s calculation on the chart, because in the Scanner you can only use Data1 for calculations. If you still observe the differences in the indicator values, cross-check the logic of the indicator.