|
PureBytes Links
Trading Reference Links
|
Tomasz,
I also think an extra data field or two would be a very nice
addition.
Right now I have 6 data items (3 of which have values 0-9 and 3 more
have values 0-999) packed into the volume and OI fields of my
primary tickers. I could have placed this information in secondary
tickers, but that would reduce my testing speed considerably,
especially when running optimizations. optimization goes MUCH faster
once AB has the data in RAM but loading all my tickers plus their
secondary tickers exceeds the 512MB of RAM my system has. AB is
lightening fast when everything is in RAM, but things really slow
down if memory swapping to disk is required.
--- In amibroker@xxxx, 520001085531-0001@xxxx wrote:
> Hi Tomasz,
> this workaround is good, but for a "clean" and fast
> solution it would be better adding 4 or 8 bytes for
> this purpose to the price records, and allowing free use/definition
> of them by the user. I can imagine it will open more new and
> advanced possibilities and add more value to the program
> (maybe AB then will be the first program which has this
> built-in, ie. without the need for a second data file).
> Please add to wish-list :-)
>
>
> ----- Original Message -----
> From: "Tomasz Janeczko" <amibroker@xxxx>
> To: <amibroker@xxxx>
> Sent: Friday, July 26, 2002 5:20 PM
> Subject: Re: [amibroker] Re: Advances in TA: Event flags
>
>
> > Hello,
> >
> > There is even better way to code "binary" fields into OHLC fields
> > using bitwise AND and OR operators:
> >
> > Lets say that you have 8 events: Event0 upto Event7
> > You can ancode them so
> > Event0 = 1
> > Event1 = 2
> > Event2 = 4
> > Event3 = 8
> > Event4 = 16
> > Event5 = 32
> > Event6 = 64
> > Event7 = 128
> >
> > Now if you want to store the day when Event3, Even5 and Event7
> > occurs you can just
> > assign 8+32+128 as a closing price.
> >
> > Now from AFL level you can use
> >
> > IsEvent3 = Foreign("IBM_Flags", "C" ) & 8;
> > IsEvent5 = Foreign("IBM_Flags", "C" ) & 32;
> > IsEvent7 = Foreign("IBM_Flags", "C" ) & 128;
> >
> > That way you can store upto 23 events in single price field,
> > so in OHLCVOI you can store 138 events.
> >
> > Best regards,
> > Tomasz Janeczko
|