Herman,

Thanks for the explanation.

I would be nice to summarize this knack and your example in the UKB.

Best regards

Le 04/08/2010 10:53, Herman a écrit :

Summarizing how off-loading Indicator code to the AA helps me:

    * I don't overload my system with calculations that do not need to
      be performed on each quote. For example, if I refresh my charts
      10x per second but perform complex calculation only 1x per
      second in the AA, I reduce my computer load by nearly 90%. The
      formula is executed 1/10th as often as without the AA. Using the
      AA allows me to perform complex calculations only "as often as
      required".
    * my indicators can keep up with more quote refreshes and my gfx
      gui is more responsive, i.e., I don't miss any button clicks and
      I can use requesttimedrefresh( 0.1) during live RT chart-trading
    * In the AA I can separate complex calculations by TimeFrame and
      further reduce computer load.
    * You don't need to use the AA exclusively for Indicator support.
      You can mix in short scans and explorations to the indicator
      code. When I need to run longer explorations I can launch
      another instance of AB and share the results by file.
    * Blending the best of both Indicator requirements and AA features
      I gain unique features like sorting, exporting, table displays
      (using results window instead of using Title) without code
      duplication.



Whenever new functions, methods, techniques, and AB resources are exposed this always opens the door to new innovation. I am happy this works.

Happy development,
herman


*> Herman,

> Thanks for the example. In a nutshell this idea comes
> down to one thing... that is plotting StaticVariables is
> quicker than performing calculations. I'm still not
> entirely sure where the 'net' gain comes from... since AB
> has to do the same calculation, no? You are simply
> splitting calculation rather than having in one place.
> i.e. load is taken from the chart and put into the AA. Add
> those two together and you don't end up with the same
> result as having the load in one place? Why not?

> As I mentioned, I already use this technique, but I use
> it to perform calculations on a much larger number of bars
> than I want to plot. I hadn't thought about the idea of
> taking away as much calculation as I can from the charts,
> because as I mentioned, I couldn't see the net gain.

> I guess the potential pitfalls that strike me are,

> 1. As TJ mentioned, you can only have one AA window open.
> So in my case I am already using one. That limits me as to
> using another for different purposes.

> 2. Where you have multiple charts, multiple layouts, and
> a universe of symbols, you'd need the AA to either work
> through each symbol in the universe (as a defined filter
> watchlist or something), or somehow work out which symbols
> the AA needs to work on at any given time depending on
> what symbols you are viewing on the charts right now.




> ------------------------------------

> **** 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/ <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/ <http://www.amibroker.com/devlog/>

> Yahoo! Groups Links


>     (Yahoo! ID required)

> amibroker-fullfeatu...@yahoogroups.com <mailto:amibroker-fullfeatu...@yahoogroups.com>


* * *
* *
**
* *

Reply via email to