e-signal data

Quote from maxpi:

Ditch, do you think this problem lies in the data or in the software interpreting the data??
More...

I guess you mean it could be Ensign, however as long as i've used i never came across one single bug in Ensign, therefore i'm assuming it's the datafeed, also because i've noticed other errors in it as well.
 
Even though I have my share of problems with eSignals software, I'll defend them !
They have been very responsive.... better than Real Tick or Tradestation or Metastock.

The issue I have with trend lines is "Definitely" a "Software" problem - NOT a data problem.
It's on not only the same computer - it's on the same advanced chart !!!
 
There was a similar problem on this thread, which lead to a different problem with eSignal data - namely that everybody had different O/H/L/C data on the same time frame! Sadly, we never heard back from eSignal either. :(
 
Dear Esignal Support since we have your attention on this thread I have a complaint. This probably seems trivial but it has actually caused me some problems on occasion. That blankety blank disclaimer on the data manager that makes you wait about a minute before you can shut the damn thing off. I dont want to go into a long winded explanation but there are occasions when I need to switch my data between computers in a hurry and this thing drives me nuts. I doubt if there is one person living other than the author that has read the dang thing.
 
try this trick, look for esignal data manager button at the task bar, right click on it, select close, click ok. If you left click on it your are doom to stare at that claim screen for eternity.
 
Looks like we have a combination of different issues here causing a confusion. Here's an answer to Ditch's issue first:

The FAQ still does apply, actually. This is a known problem that can occur between two computers or even on the same computer or same chart. If you refresh the data on both the charts, I'm sure they will come into line. The second paragraph of the FAQ is of the most relevance here, and should help to further explain...


When you initially request a new chart, the data is supplied from our Tick Server and loaded onto your desktop. From that point forward, data is then streamed in from our Network and cached locally on your system. When you "refresh", all of the data on that chart is re-sent by our Tick Server and the cached data is cleared. If your PC clock is slightly fast or slow, this could also result in slight differences after a refresh.
More...

There is also a mention of a fix coming in the end of October. This is pretty close, but may be more like the first week in November.

One last point is that the 1-min. in your example may have been built from streaming data, but the 10-min might have been built from the historical data. If that is the case, then this may be a case of some cancelled trades correcting the data in our History Server, but these wouldn't typically correct a "locally" stored chart built off of streaming data.

Now onto ZBear's Trend Line issue:

This thread on eSignal Central discusses the trend line issue in more detail. My apologies for confusing the two different issues.
 
Quote from JayF_eSignal:

Looks like we have a combination of different issues here causing a confusion. Here's an answer to Ditch's issue first:

The FAQ still does apply, actually. This is a known problem that can occur between two computers or even on the same computer or same chart. If you refresh the data on both the charts, I'm sure they will come into line. The second paragraph of the FAQ is of the most relevance here, and should help to further explain...



There is also a mention of a fix coming in the end of October. This is pretty close, but may be more like the first week in November.

One last point is that the 1-min. in your example may have been built from streaming data, but the 10-min might have been built from the historical data. If that is the case, then this may be a case of some cancelled trades correcting the data in our History Server, but these wouldn't typically correct a "locally" stored chart built off of streaming data.

Now onto ZBear's Trend Line issue:

This thread on eSignal Central discusses the trend line issue in more detail. My apologies for confusing the two different issues.
More...

Jay,

For what it is worth, of course i did a refresh on both charts.
 
Jay,

Thanks for the link to eSig forums on this problem.
However - this problem still seems to be unresolved.
As witnessed by the most recent eSig Forum posted responses.
............. ( enclosed below )

My issue is very similar but somewhat different than those being discussed.
My posted snapshot files to Michael A.... show how the Trendline will "" JUMP""
when the price / background is dragged to the left ....... changing the relationship to the Hi / Lo from the previous time frame - obviously something very wrong here !

Once again ... check out the snapshot files I sent to Michael A....
I don't want to go through the whole thing again here.

Question is ....... "WHEN" is eSig going to fix this problem ?

I would certainly like to talk to someone about this if they could call me..... Andy or whomever !!!


.................................................................................................
FROM ESIGNAL FORUMS

From: Echelon
However, whether you want to define this problem as a "bug" or simply an enormous oversight in programing, is a matter of semantics. It is a vital issue, if for no other reason than the fact that most people probably do not know it exists, and may be using erroneous trend lines for their trading.

To have a sophisticated charting software with this basic flaw should be unacceptable to anyone paying for the service.

I have been a user of Advanced GET's software for many years, and that software did not have this issue when going from weekly to daily, or from daily to hourly, and I don't think it's too much to require the same from Esignal.

............................................................................................
From: Gspiker
I have to agree with Echelon here. Even if it is working as intended and is not a "bug" as such, it is still an issue. Note that it is not an issue with just users of trend lines, but have deeper implications than that.

The bottom line is that the software is giving erroneous results in places where a normal user wouldn't expect there to be any problems.

The question that is hard to quantify is how many users are being hit by this. As Echelon points out, some users may not even know they are having this problem. But even if it is just a few the issue is serious enough that I would hope eSignal would devote energy into fixing it. It isn't as glamerous as new features, but it might end up saving some of their customers a lot of money and agrivation.
 
You must log in or register to reply here.
Back
Top