I get it TJ. Sure I know the difference between scaler and array.

And I understand that AB provides Basic, Intermediate and Advanced
User functionality. Admittedly, unless I am really motivated, I am
often just plain too lazy to dig into the 'Advanced' area of coding.
In other words, some ideas simply don't merit the effort required to
implement them as an individual user.

So when I read a post about a desired feature from someone else that
makes sense to me, then I'll join in and express the an opinion about
a possible AB enhancement that might be of value to a larger audience.

And in the future I won't be surprised to receive a response from you
about "Advanced User Functionality" being an appropriate solution to
any given problem. Won't offend me in the least. But you deserve to
know when more than one Customer thinks a feature might be of value
and enhance AB's value.

With great respect and best regards.

Phsst


--- In [email protected], "Tomasz Janeczko" <[EMAIL PROTECTED]> wrote:
>
> You guys don't get it at all. 
> 
> Most metrics are SCALARS (single number) !
> Your plots will look like this:
> 
> Plot( 0.8, "Sharpe Ratio", colorRed );
> 
> These metrics DO NOT CHANGE over time because they are all
calculated ONCE when backtest is complete
> and result is single number (scalar), *not* array.
> 
> Best regards,
> Tomasz Janeczko
> amibroker.com
>   ----- Original Message ----- 
>   From: Phsst 
>   To: [email protected] 
>   Sent: Sunday, May 18, 2008 3:36 PM
>   Subject: [amibroker] Re: System Performance Indicators [was: Can
someone fix this OLE code?]
> 
> 
>   Herman,
> 
>   Your case for System Performance Indicators is a good one.
> 
>   A further idea...  there should be no need for User code to
accomplish this. The plots should be a native feature of AB (just like
the Equity plot).
> 
>   Instead of plotting "flat lines" for single numbers, gfx
Horizontal plots of each performance metric could be presented against
a "good / bad scale" defined in the form of a Param value for each
performance metric that the User could alter from a base set of
default values. Of course the gradient colors of the plots would go
from red (bad) to green (good). 
> 
>   For example, the default Param for Sharpe Ratio could be 1.00, and
some Users might want to use  .80 as a Param value where the gradient
color starts changing to green.
> 
>   My two cents worth.
>


Reply via email to