clearpicks
As I understand it the historical daily bars are received from the History Servers while the current daily bar comes from the Data Manager and is based on the daily snapshot transmitted by the exchange. It is not built using intraday data.
Alex
As I understand it the historical daily bars are received from the History Servers while the current daily bar comes from the Data Manager and is based on the daily snapshot transmitted by the exchange. It is not built using intraday data.
Alex
Originally posted by clearpicks
Hello Jason,
Thank you for your response.
If you remove all sym() and inv() in the test script and replace with something like getValueAbsolute(...., "UNG,1") etc. and you would not see non-zero dms being printed out. That is the reason I thought it was introduced by sym() and inv(). Due to the relative large value of dms in esignal 10 compared to 8, the loading time of my layout page is also much slower than that in esignal 8. It seems sometimes such CPU usage spike duing startup may cause the incorrect last daily bar being built. I asked a question about how esignal builds the last daily bar on charts but got no complete answer. I suspect these two threads are closely related.
- Clearpicks
Hello Jason,
Thank you for your response.
If you remove all sym() and inv() in the test script and replace with something like getValueAbsolute(...., "UNG,1") etc. and you would not see non-zero dms being printed out. That is the reason I thought it was introduced by sym() and inv(). Due to the relative large value of dms in esignal 10 compared to 8, the loading time of my layout page is also much slower than that in esignal 8. It seems sometimes such CPU usage spike duing startup may cause the incorrect last daily bar being built. I asked a question about how esignal builds the last daily bar on charts but got no complete answer. I suspect these two threads are closely related.
- Clearpicks
Comment