An All-new eSignal Launches...

64 bit architecture means I can use more than 2 gigs of ram.

Windows 7 and esignal use about 950 megs of RAM. I collect a lot of tick data and generally run out of RAM when esignal has been open for about 5 days. This is really annoying.

When esignal 11 is stable, I can switch and I won't have this problem.

Stable means the ability to run a 1000 line EFS script across five different markets without ever crashing.

Arthur, you collect a lot of tick data, don't your run out of RAM as well?

Runningbear
 
Esignal was always a mess. I dumped it when... near the end of the last century actually... I just looked at what they had and what they said about it and what they charged and decided that it was unlikely that they would ever do anything stellar... if it walks like a duck and quacks like a duck and it stinks, it's probably not a duck, it's probably something that stinks...
 
Over the last two trading days, 10.6 has been freezing for 30 min or more while the market is open. After experimenting with the code of my main strategy, I found a math heavy function that, while really quite useful, I could modify around with a passable reduction in return.

This allowed me to run my strategy in eSignal 11 to bypass the latency issues, which hadn't worked before.

I have to say, eSignal 11 runs completely smoothly in contrast to the problems I just had with 10.6. I've got a duo core 64 bit machine with 6 gigs of RAM. And there actually is a lot I like about the look and feel of the new interface -- a lot of small intuitive things (option to hide all toolbars, sliders for colors, generally more responsive chart objects, tabbed pages) that counterbalance, for me, the collection of weird quirks we already mentioned.

Just running my strategy without freezing is paramount to me. That said, this is just a stop gap measure while I continue trading, as I no longer am confident that the price warrants the features.
 
Arthur

If I understand you correctly, instead of dragging the x-axis,
drag the left border of the chart. That way you can reduce the
width to about an inch.

Quote from Arthur Deco:

They giveth, and they taketh away. I was thrilled in the initial release that I could perform an extreme compression of the time scale. Now it's gone. Makes my one-second chart useless.
More...
 
And /or try this:

- Increase/Decrease Bar Width has been added (Shift + Left/Right Arrow)
- Increase/Decrease Bar Spacing has been added (Alt + Left/Right Arrow)





Quote from learner2007:

Arthur

If I understand you correctly, instead of dragging the x-axis,
drag the left border of the chart. That way you can reduce the
width to about an inch.
More...
 
Until you get what you need, have you ever tried a Range chart using a Line instead of a bar, and setting the interval to 0.001R.
This will plot every trade at every level and is what I use in addition to 1 minute charts when trading futures. This will clearly indentify S/R and you can compress it to the 10-15 minutes you want by adjusting the x-axis and width of the chart.


Quote from Arthur Deco:

Sorry I wasn't clear. I am talking about dragging the time scale for a fixed size window. For example, I run a one-second chart to see precisely what it happening at S/R, but I compress the time scale down to 10-15 minutes.
More...
 
Quote from Landis82:

I had a horrendous experience with E-Signal about 4-5 years ago in which I spent nearly 20 hours over the course of two weeks trying to HELP THEM TROUBLESHOOT an issue that they never wound-up finding a solution for ( an ES chart would freeze after a few minutes, followed by the SPY chart freezing ). Why they use their customer base (in my opinion) for "glitchy" versions and updates is absolutely beyond me.

Never again.
Never.
More...

Ditto... Exact Same Time Period and Exact Same Issue...Same Exact Exit On My Part...
 
Scott

As a long time user of esignal i've never been as disappointed with ESig service as I am now.

Releasing a version that is not ready for the market and not tested by professional traders (who you may actually have to pay big $ to for testing) are poor biz decisions on Interactive Data's part.

I felt sorry for the service tech on the phone the other day who struggled as much as I did with Version 11. He even admitted that the training they got didn't cover anything that the customers were complaining about. We couldn't even copy and paste a quote page or export to excel. That's the service department. It would be comical if I wasn't paying an ever increasing fee. I've never seen such a mess at Esignal.

Feel free to PM me if there is something you can do for me $$ wise on my bill. I was shocked to see that it went up once again.
Pass these complaints onto department heads etc so they understand how super pissed a lot of customers are.
They need to know business is RUNNING away if they haven't already figured it out.


GM



Quote from eSignal Support:

We'd recommend that current subscribers continue to use 10.6 while we continue to port existing functionality over to the 11 series (like style templates, bar replay, etc.).

Thanks.
More...
 
As a fellow coder, and you have my sympathies, my boss is an asshole, too, always wanting it done faster. I say "If you want it bad, that's how you'll get it!" But he never listens. Anyway, the fact that your blue sign-on window overlays whatever else is on the screen is highly annoying, especially since your pig takes it's own sweet time oinking. We've got better things to do that watch you brag that you load slowly. Allow the user to minimize it in the next release. See how TWS does it.
 
Another frustration: any other eSignal 11 users having problems with variables that are passed as series parameters?

For example, I'm trying to adapt a formula where I use the last x days' ATR as a coefficient for something in an intraday script. I do this by calling customATR.efs in efsexternal, passing the required parameters in full. Why do I use customATR? Only way I can define "D" as the desired interval.

I'm discovering a big chunk of the efs code that fails in 11 has to do with something like this, which is native built-in code:

var vSymbol = Symbol+","+Interval;
xATR = atr(Length,sym(vSymbol));

sym("XYZ,D") fails to recognize the interval, yet customATR itself runs fine when not called in efsexternal.

Pretty much all of my formulas that fail to port over fall apart when you pass simple concatenations or other variables as parameters. Haven't been able to dig further to determine if this guess is right or wrong, but it appears to be a consistent problem so far.

Just throwing this hypothesis out there for anyone else running into similar headaches.
 
You must log in or register to reply here.
Back
Top