|
PureBytes Links
Trading Reference Links
|
Thanks I appreciate the support and the help. I tend to push these products to the limits and find odd use cases and areas for improvement rather quickly. That said a lot of it is probably that I'm not that knowledgeable about the nooks and crannies of AB, but sure enough there are some areas where AB probably took the wrong approach. I don't think there's anything wrong with pointing those cases out since it can only help to make the platform better.
--- In amibroker@xxxxxxxxxxxxxxx, "brian_z111" <brian_z111@xxx> wrote:
>
> Hi Conrad,
>
> I didn't think you 'flooded' the forum with questions in your thread,"I'm having a very hard time doing something that I think should be simple".
>
> It doesn't matter how much money you are spending the principle is the same for all:
>
> - your questions were well researched, informed and relevant
> - if Tomasz answers via support then his time (x) benefits 1/x; if he answers via the forum then it benefits (interested% * 9000+)/x;
>
> The thread could have been shortened anytime by receipt of the answer:
>
> "Plugins do send updates if certain market is closed .........
>
> ....... for the reasons above, most plugins sent "general update" every second. It does
> not however
> mean that your chart will refresh at that frequency. That depends on settings, I
> mentioned in my previous reply."[Tomasz]
>
> Over to your latest question:
>
> > Now if I can just figure out how to determine the number of visible >padded bars.
>
> Could you please elaborate in laymans language (if possible).
> That doesn't sound too hard ..... maybe someone can help if you can define the problem for us.
>
>
>
> --- In amibroker@xxxxxxxxxxxxxxx, "Conrad Joach" <consolejoker@> wrote:
> >
> > I've yet to do any serious benchmarks yet of C# vs. AFL. That said, I chose AFL because it is a) well supported b) one of the few apps that lets you draw arbitrarily anywhere on the charting canvas) and c) has good data connectivity options.
> >
> > It does appear pretty quick, and I want to make it a mainstay in my firm. I just need to get a slightly more clear understanding of what I am seeing.
> >
> > We *greatly* appreciate the help given from other users and AB support. Don't let the frustration fool you, but if you put in 20+ hours and some basics don't add up, the whole affair will begin to wear thin :)
> >
> > Now if I can just figure out how to determine the number of visible padded bars. Without that I am back up the creek without a paddle. I will end up drawing into the price margins and no user would put up with that.
> >
> > --- In amibroker@xxxxxxxxxxxxxxx, "sidhartha70" <sidhartha70@> wrote:
> > >
> > > Conrad, granted that it does seem inefficient to run an entire AFL just for interpretation window output. That's something I have thought myself in the past... perhaps someone can comment on why that is required...?
> > >
> > > However, bottom line for me is, whatever the slight idiosyncrasies, AFL code does seem to execute orders of magnitude quicker than other C# based systems that I tried.
> > >
> > >
> > > --- In amibroker@xxxxxxxxxxxxxxx, "Conrad Joach" <consolejoker@> wrote:
> > > >
> > > > I'm not questioning AB's capabilities or credentials. Let me be clear, I am not at all here to dump on AB. I have spent close to 20 hours so far trying to get a good grasp on how the behavior of this app is setup precisely because I am so impressed with its capabilities. That said, it's rough on some edges and it definitely looks like a platform that has evolved over a long time. Lots of things don't seem like they would be there if it were redone from scratch today. Those things are causing me a bit of grief.
> > > >
> > > > We wouldn't have plunked the money down on something to test if we didn't think it has the potential. What I'm having a hard time with is the very cryptic behavior that it displays.
> > > >
> > > > Yes I tried ActionEx, and yes it shed light on things, I appreciate the suggestion and I appreciate your help.
> > > >
> > > > Now it does make sense (sort of) to understand that when you click outside your chart pane, AB no longer feels the need to call your AFL to update the Interpretation pane. It is very weird still to me though to know that a block of code must be called a separate time just for the interpretation pane. It seems very inefficient.
> > > >
> > > > Nevermind though, I have disabled my script so that if the ActionEx doesn't fall within a narrow set of reasons, it will not run. This is going to make a huge difference in debugging things.
> > > >
> > > > There are some other weird things I'm still grappling with, that I could use a hand with. I will post them in another thread but I am sure at this point people aren't reading my questions any more other than you and a few others :)
> > > >
> > > > --- In amibroker@xxxxxxxxxxxxxxx, "sidhartha70" <sidhartha70@> wrote:
> > > > >
> > > > > I'm not sure I agree on the visible bars issue you are trying to raise. I don't believe that would be the case...
> > > > >
> > > > > There are plenty of people using AB for RT trading, and quite a few for fully automated real time trading via IB... it's got 1,000's of users and it rock solid in my experience. Any fears you are raising are much more likely to come from your lack of understanding of AB than anything else...
> > > > >
> > > > > Herman on this list has written a lot about Automated RT trading... so he's a good port of call for you. I personally am a discretionary trader.
> > > > >
> > > > > However, as I said before, to get some more visibility trying using Status("actionEx").... have you tried that yet...?
> > > > >
> > > > > --- In amibroker@xxxxxxxxxxxxxxx, "Conrad Joach" <consolejoker@> wrote:
> > > > > >
> > > > > > Because it is absolutely critical to fully understand the circumstances that cause your code to be invoked and what your code can expect to see when it is invoked.
> > > > > >
> > > > > > The example I gave in this thread is borderline insane, because think about it, your code is attached to one chart pane, and yet it is invoked twice every second. But only if a user clicks inside your chart pane. And then if it is invoked twice, the first time it will see a view from *the top chart pane*.
> > > > > >
> > > > > > That means that the number of visible bars will return *different* than the number of visible bars for which the user actually applied your code to.
> > > > > >
> > > > > > That makes debugging your code an absolutely head banging task, because you can't understand why your code is reporting one thing when clearly the pane it was applied to has a known set of state to you.
> > > > > >
> > > > > > Any system that wants to be used with real money has to explain in total detail these basic things.
> > > > > >
> > > > > > Maybe these facts are not relevant to most people here, so be it. But if I'm to end up spending hundreds of hours building a system and then thousands of dollars to buy the number of AmiBroker licenses that I would need to deploy in my firm, I want to know exactly what I'm dealing with up front.
> > > > > >
> > > > > > --- In amibroker@xxxxxxxxxxxxxxx, "sidhartha70" <sidhartha70@> wrote:
> > > > > > >
> > > > > > > Conrad, why are you so obsessed with the minutiae of AB's calls to different chart panes...??
> > > > > > >
> > > > > > > How is that going to help you...? I get the feeling you are looking at AFL like an event driven language...
> > > > > > >
> > > > > > > --- In amibroker@xxxxxxxxxxxxxxx, "Conrad Joach" <consolejoker@> wrote:
> > > > > > > >
> > > > > > > > Maybe I'm the only person in the world having a hard time getting grips on how AmiBroker actually works. I'm about to give up because I just can't get a strong understanding of these basic things. And yes I've submitted this to support but it's the weekend and I'm wasting hours on this.
> > > > > > > >
> > > > > > > > Do the following and tell me what you see.
> > > > > > > >
> > > > > > > > 1) Create a new blank chart with minutely interval. Add a Price series on it. Make sure that your chart refreshes are set to once per second (1) in the Intraday tab in Preferences.
> > > > > > > >
> > > > > > > > 2) Using the following AFL script, create a 2nd chart pane and add the AFL below.
> > > > > > > >
> > > > > > > > Script: _TRACE(NumToStr(NOW(4)));
> > > > > > > >
> > > > > > > > 3) Now click inside the pane that has the AFL from below. Notice that every time its invoked, its invoked twice? Look at the seconds part of the time, there are two printouts per second in the trace window, and one value is for the top pane, and the other value is for the bottom pane.
> > > > > > > >
> > > > > > > > 4) Now click in the top pane (not where the AFL is applied to), you'll see it goes back to printing just once per second.
> > > > > > > >
> > > > > > > > Why is this happening? If I create a 2nd pane in a chart window, and add AFL to it, why on earth would it be called twice when I click *inside* the pane and once when I click outside the pane?
> > > > > > > >
> > > > > > > > Am I wrong or shouldn't it only be called once per chart update interval, not twice? And to make matters worse, when it is called for the top chart pane (not the one we applied it to) it will receive a very different view of the state of AmiBroker. Things like number of visible bars may be different than the bottom pane.
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
------------------------------------
**** IMPORTANT PLEASE READ ****
This group is for the discussion between users only.
This is *NOT* technical support channel.
TO GET TECHNICAL SUPPORT send an e-mail directly to
SUPPORT {at} amibroker.com
TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
http://www.amibroker.com/feedback/
(submissions sent via other channels won't be considered)
For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/amibroker/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/amibroker/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:amibroker-digest@xxxxxxxxxxxxxxx
mailto:amibroker-fullfeatured@xxxxxxxxxxxxxxx
<*> To unsubscribe from this group, send an email to:
amibroker-unsubscribe@xxxxxxxxxxxxxxx
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|