RE: [amibroker] AmiBroker 5.14.0 BETA released, AmiBroker Email List Archive

Re:

Thanks …
I guess I’m dense … I did read it but I don’t see how it applies …
If I wasn’t running 5.14 there wouldn’t be a QuickAFL box to check … would there ? …

Beyond that there is no custom backtest procedure

I’ll read it again for the fifth time … Maybe I’ll discover what I’ missing …

From: amibroker@xxxxxxxxxxxxxxx [mailto:amibroker@xxxxxxxxxxxxxxx] On Behalf Of Tomasz Janeczko
Sent: Friday, July 04, 2008 5:25 PM
To: amibroker@xxxxxxxxxxxxxxx
Subject: Re: [amibroker] AmiBroker 5.14.0 BETA released

Hello,

Probably a typo in the docs. Should be sbrAll (not sbsAll). sbr comes form (S)et(B)ars(R)equired

Explained in the picture here:

http://www.amibroker.com/kb/quickafl

Something is wrong on your end. Either it is not turned on or you are not using 5.14 or your custom backtester

procedure (if you are using any) is taking 99.9% of time.

= = =

3... Did you bother to read http://www.amibroker.com/kb/quickafl

That is MUST READ. It has to be read CAREFULLY. Specifically part about

Setbarsrequired AND using "Check And Profile". Once you read that, you would know

that certain functions like Cum() or AddToComposite.

Best regards,
Tomasz Janeczko
amibroker.com

----- Original Message -----

From: Fred Tonetti

To: amibroker@xxxxxxxxxps.com

Sent: Friday, July 04, 2008 10:12 PM

Subject: RE: [amibroker] AmiBroker 5.14.0 BETA released

TJ,

In regards to item #7 …

-          I seem to get a syntax error when using SetBarsRequired(sbsAll, sbsAll) … to the effect that … variable sbsAll used without having been initialized … Any ideas ?

-          If one has for loops etc how does one tell where the first bar is ? i.e. if I write

Beg = LastValue(ValueWhen(Status(FirstBarInRange”), BarIndex()));

End = LastValue(ValueWhen(Status(LastBarInRange”), BarIndex()));

For ( i = Beg; I <= End – 1; i++ )

{

            X = C[i];

}

I get messages to the effect that I have a subscript out of range … Is there something that I can do to check that a variable of an array is not out of range or some value I can set Beg to in advance of the loop to keep these messages from occurring ?

-          For good size watchlists, I’m not seeing much if any difference in optimization times for some specific number of iterations. This with AA From/To dates set to the last two years and QuickAFL turned on as opposed to all quotes which span some 20+ years. Can you provide any insight as to why that might be ?

Thanks in advance

From: amibroker@xxxxxxxxxps.com [mailto:amibroker@xxxxxxxxxps.com] On Behalf Of Tomasz Janeczko
Sent: Friday, July 04, 2008 5:39 AM
To: amibroker@xxxxxxxxxps.com
Subject: [amibroker] AmiBroker 5.14.0 BETA released

Hello,

AmiBroker 5.14.0 BETA is released now:

http://www.amibroker.com/devlog/2008/07/04/amibroker-5140-beta-released/

CHANGES IN VERSION 5.14.0 (as compared to 5.13.0):

added support for Quarterly and Yearly intervals in all parts of the program

Changes to drawing made in v5.13 caused improper drawing lines located PAST the last available quote (trendlines and pitchforks) when timestamping method was “START TIME of interval”. This is fixed now.

Fixed AddSummaryRows so ‘onlycols’ parameter default (zero) is applied properly

Implemeted “Select all” via Ctrl-A keyboard shortcut for all list (result list in AA for example)

Mouse cursor shape (moving/sizing) reflects the selected study priority when more than one study exists under mouse position

new multiple Volume At Price charts at user-defined points via new PlotVolumeOverlayA function

QuickAFL can now be used in Automatic Analysis (Settings: General: “Use QuickAFL” - check this box) - this can speed up explorations, scans and backtests by factor of 2+ if range is less than “all quotations”. More on this: http://www.amibroker.com/kb/quickafl

Range Bars compression now uses TickSize as “1R step”. TickSize defined in the Symbol Information, if its value is zero, then 1R would be equivalent to 0.01 movement (for backward compat)

selecting date in multiple linked charts is now faster because redraw is not made when selected line in higher compressed interval remains in place

selector line in linked charts works OK now, regardless of selected time compression timestamping method

SetBarsRequired accepts now values -2 in special meaning: reference ALL bars

Sometimes progress bar did not show the name of optimization engine used. Now it is fixed

Status(”ActionEx”) provides more codes than Status(”action”) to detect special executions states

Streaming chart update could stall if trend line handle was clicked in attempt to resize and released in the very same position (without moving the mouse). Now it is fixed.

TimeFrameMode() now supports mode == 4 - which expresses RANGE bars in TickSize units (as opposed to mode 3 that uses dollars for backward compatiblity)

when display chart timing option is turned on and RT stream is active the application STATUS BAR now displays TOTAL time for all charts, it should be BELOW 1 second for RT trading

Best regards,
Tomasz Janeczko
amibroker.com

I am using the free version of SPAMfighter for private users.
It has removed 497 spam emails to date.
Paying users do not have this message in their emails.
Try SPAMfighter for free now!

I am using the free version of SPAMfighter for private users.
It has removed 497 spam emails to date.
Paying users do not have this message in their emails.
Try SPAMfighter for free now!
__._,_.___

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.amibroker.com/devlog/ For other support material please check also: http://www.amibroker.com/support.html

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___