There is no way to guarantee the order in which two separate intraday charts will update with a new bar, and thus it is likely that charts updating bars at the same time may not receive the most recent data. As an example, suppose a 1-minute chart is sending a stream to a 10-minute chart. Six times an hour these charts will update at the same time, and which updates first is usually a function of the unpredictable timing in which data is received, or other factors. Therefore at any one of those six times per hour, it is possible that the 10-minute chart will update and ask for streams a second or so before the 1-minute chart updates. The 10-minute chart will get the streams that are currently available, and will not wait for the 1-minute chart to update. Therefore it is possible that the 10-minute chart will receive 1-minute-old data from the 1-minute chart. Do not use these indicators where this could be a problem for you. Generally simultaneous updating is not as likely when at least one chart is a volume, tick, or range bar chart. To correct this problem, you can right click on the chart and select recalculate chart to manually update "out of sequence" operations.
Another time that older bars may be sent is when there are no bars to send. This could occur when there are gaps in price bars due to missing data, the market not being open, or other causes. When a new value for a bar is available, the bar may change. If you build a prediction or trading rules based on these bars, your signals could change.
Such problems may be less troublesome when sent data is received by the chart with the fastest bars.
The maximum number of Send (Stream and Group) indicators actively running at one time is 300. If you exceed this number you will get a message to restart NeuroShell. The indicator, which causes the error message, will function properly until the restart. When charts containing Send indicators are closed, the data is retained until a NeuroShell restart. These deleted controls continue to consume some of the 300 buffers until restart.
If, in an active NeuroShell environment, you permit duplicate StreamIds or (Group,MemberIds) to execute, then the system will update data in an unpredictable manner. Results will not be meaningful.
The NeuroShell ini parameter unloadcustomdlls must be set to false. This is the NeuroShell default so most users will not have to worry about this. However, if you are a DLL developer you may have set it to true, and if so, set it back before using InterChart Tools.
|