Although not necessarily related to Yuki problem
The statement If Base time interval is NOT EOD, then you do not use EOD data, you are using compressed intraday data instead. Compression uses your individual intraday settings. Is not always correct in my experience when MIXED EOD/intraday is selected. In signal, intraday data is only available for the last 60 days, the rest are all EOD. Is that your intention to cover that situation, or are you just referring to Yuki's situation. _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tomasz Janeczko Sent: Wednesday, 21 March 2007 12:24 AM To: [email protected] Subject: Re: [amibroker] data conflicts only apparent in AB Yuki, Apparently you are mixing things. To get EOD data in AmiBroker from eSignal you have to have Base time interval set to "EOD" in File->Database Settings If Base time interval is NOT EOD, then you do not use EOD data, you are using compressed intraday data instead. Compression uses your individual intraday settings. Explained in the KB. http://www.amibroke <http://www.amibroker.com/kb/2006/03/19/how-does-the-daily-time-compression- work/> r.com/kb/2006/03/19/how-does-the-daily-time-compression-work/ To compare you would need to display INTRADAY data in eSignal as well. Best regards, Tomasz Janeczko amibroker.com ----- Original Message ----- From: "Yuki Taga" <[EMAIL PROTECTED] <mailto:yukitaga%40tkh.att.ne.jp> att.ne.jp> To: <[EMAIL PROTECTED] <mailto:amibroker%40yahoogroups.com> ps.com> Sent: Tuesday, March 20, 2007 11:07 AM Subject: [amibroker] data conflicts only apparent in AB >I have three independent EOD data sources, and they agree with each > other nearly 100 percent. > > Today, I have numerous erroneous data problems in the eSignal > database, but when I open up the native eSignal application, its EOD > data agrees with my other EOD data sources, but not with what AB is > showing me. > > Can anyone explain why this happens? If eSignal indeed is correcting > data after the fact on its servers, but a force backfill on all > symbols is not possible, it really presents a problem, doesn't it? > > I'm at a loss to explain how this happens, or as to the most > efficient way to fix numerous errors like this once they become > apparent. This does not happen often, and eSignal *seems* to have > gotten better recently. However something went dreadfully wrong > today. > > Yuki > > > > > Please note that this group is for discussion between users only. > > To get support from AmiBroker please send an e-mail directly to > SUPPORT {at} amibroker.com > > For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG: > http://www.amibroke <http://www.amibroker.com/devlog/> r.com/devlog/ > > For other support material please check also: > http://www.amibroke <http://www.amibroker.com/support.html> r.com/support.html > > Yahoo! Groups Links > > > > >
