|
PureBytes Links
Trading Reference Links
|
It would be more useful to define *first* P2 and then P1 [as a P2
with lower H or something like that]
This procedure would look into the future by one day, which is
somehow affordable.
Epi s procedure [as described] may look into the future by *many*
days [P2 may be two months before P1 !!!]
See a live show at
http://groups.yahoo.com/group/amibroker/message/47599
Dimitris Tsokakis
--- In amibroker@xxxxxxxxxxxxxxx, "Graham" <gkavanagh@xxxx> wrote:
> Yes can follow the principle of the problem, and as you said there
can be
> many points that define the second point backwards. It would be my
> preference to find the 3rd previous one (P3) and check if the
intervening
> point P2 is within reasonable proximity to the line between P1 and
P3. This
> would give confirmation that P3 could be correct.
> The further problem would be whether P1 is correct, if not then the
exercise
> is incorrect. Then you would go by iterative process backwards
using P2, P3
> etc as your first point and try to locate previous points to
confirm a trend
> line that is indicative of the price action.
>
> Cheers,
> Graham
> http://groups.msn.com/ASXShareTrading
> http://groups.msn.com/FMSAustralia
>
>
> -----Original Message-----
> From: DIMITRIS TSOKAKIS [mailto:TSOKAKIS@x...]
> Sent: Thursday, 11 September 2003 2:08 PM
> To: amibroker@xxxxxxxxxxxxxxx
> Subject: [amibroker] Subject: Re: TJ - Solution please
>
>
> According to the last epi description, he detects first the p1 [the
> most recent p1] and then searches into the past for a p2.
> Of course, there are many p2s before p1 and he should choose which
> one he prefers [I would suggest the closest to p1, but ...]
> As we have in zig function the last leg variable, in epi´s project
we
> have the last pair [p1,p2] variable or, to be more specific, the
last
> [p1,(p2A, p2B, p2C,...)] variable.
> We can do something from the code part, but it would be better to
> specify the selection of p2, in order not to be lost in the chaos.
Except
> epi´s special request, the subject [simultaneous definition of
> pairs of points with different properties] is interesting.
> Zig is a simple example, it links Peaks and Troughs [but with the
> same per coefficient]
> Dimitris Tsokakis
> --- In amibroker@xxxxxxxxxxxxxxx, "Graham" <gkavanagh@xxxx> wrote:
> > DT you are making my head spin decyphering that one :)
> >
> > Cheers,
> > Graham
> > http://groups.msn.com/ASXShareTrading
> > http://groups.msn.com/FMSAustralia
> >
> >
> > -----Original Message-----
> > From: DIMITRIS TSOKAKIS [mailto:TSOKAKIS@x...]
> > Sent: Thursday, 11 September 2003 1:50 PM
> > To: amibroker@xxxxxxxxxxxxxxx
> > Subject: [amibroker] Subject: Re: TJ - Solution please
> >
> >
> > As you see, it is better to describe your exact preference first
> and
> > then try the exact code [if any].
> > You should know something in advance : The p2 is known to be a p2
> as
> > soon as p1 is recognised as p1 !!
> > You will have, for example, the last 10 candles neutral and then,
> > with the new data import, all of a sudden, yesterday will become
a
> p1
> > and 6 bars ago will become a p2!!
> > You define the properties of the past, when you detect a p1 and
> this
> > is done in reverse time order.
> > In other words, the event p1 looks into the future by one bar, but
> > the event p2 looks into the future by many bars.
> > Among the others, think the alternative, to define first p2 and
> then
> > expect a lower peak p1. This detection would look into the future
> by
> > only one day , which is not bad at all.
> > The decision is yours, of course...
> > Dimitris Tsokakis
> > --- In amibroker@xxxxxxxxxxxxxxx, "epintoem" <epintoem@xxxx>
wrote:
> > > Thanks for this... We are close but not quite.
> > >
> > > Every peak will have a peak that is higher than it. so we might
> > have
> > > a situation where a higher peak might be the point for two
peaks
> > > subsequent peaks that are lower.
> > >
> > > Assume p1 is the the most recent peak at 10.50 on 9./04
> > >
> > > p2 could be a peak with a value of 10.00 on 8/26
> > >
> > > P3 could be the peak with a value of 13.00 on 7/25 that would
> > connect
> > > to both p1 and P2
> > >
> > > Thanks so much for your help
> > >
> > >
> > >
> > >
> > > --- In amibroker@xxxxxxxxxxxxxxx, "Dimitris Tsokakis"
> > <TSOKAKIS@xxxx>
> > > wrote:
> > > > Here is my definition of a peak
> > > > High greater than high previous day and following day. Most
> > recent
> > > > high greater than close two days earlier.
> > > >
> > > >
> > > > condP=Ref(H,-1)>Ref(H,-2) AND Ref(H,-1)>H AND Ref(H,-1)>Ref
(C,-
> 3);
> > > >
> > > > The conditions for the peak prior to this one are the same
> except
> > > > that the high should be greater than the peak it is connecting
> to.
> > > >
> > > > It was Dimitris who provided me the code for IB.
> > > >
> > > > Hope this helps
> > > >
> > > > ********************************************************
> > > >
> > > > If I understand well, you search for pairs P1, P2.
> > > > The green candles are all the CONDP occurrences.
> > > > The red triangles P1 have the previous peak higher.
> > > > The blue triangles have the next peak lower.
> > > > The rest green candles are of no interest.
> > > > Do you want now to link P2, P1 pair with a line, like the
dotted
> > > black line of the gif ?
> > > > Or you want a zig line connecting cascade P1,P2,P1,P2,... ?
> Please
> > > > advise.
> > > >
> > > > CONDP=Ref(H,-1)>Ref(H,-2) AND Ref(H,-1)>H AND Ref(H,-1)>Ref
(C,-
> 3);
> > > > P11=Ref(CONDP,1); H1=ValueWhen(P11,H,1); H2=ValueWhen
(P11,H,2);
> > > > H0=ValueWhen(P11,H,0);
> > > > P1=P11 AND H2>H1;
> > > > P2=P11 AND H1>H0;
> > > > PlotShapes(shapeUpTriangle*P1,colorRed);
> > > > PlotShapes(shapeDownTriangle*P2,colorBlue);
> > > > Plot(C,"",p11*colorYellow+1,64);
> > > >
> > > > Please advise.
> > > > Dimitris Tsokakis
> >
> >
> > ------------------------ Yahoo! Groups Sponsor -------------------
--
> ~--> Buy
> > Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark
> Printer
> > at Myinks.com. Free s/h on orders $50 or more to the US & Canada.
> > http://www.c1tracking.com/l.asp?cid=5511
> > http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/GHeqlB/TM
> > ------------------------------------------------------------------
--
> -~->
> >
> > Send BUG REPORTS to bugs@xxxx
> > Send SUGGESTIONS to suggest@xxxx
> > -----------------------------------------
> > Post AmiQuote-related messages ONLY to: amiquote@xxxxxxxxxxxxxxx
> > (Web page: http://groups.yahoo.com/group/amiquote/messages/)
> > --------------------------------------------
> > Check group FAQ at:
> > http://groups.yahoo.com/group/amibroker/files/groupfaq.html
> >
> > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>
> Send BUG REPORTS to bugs@xxxx
> Send SUGGESTIONS to suggest@xxxx
> -----------------------------------------
> Post AmiQuote-related messages ONLY to: amiquote@xxxxxxxxxxxxxxx
> (Web page: http://groups.yahoo.com/group/amiquote/messages/)
> --------------------------------------------
> Check group FAQ at:
> http://groups.yahoo.com/group/amibroker/files/groupfaq.html
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark
Printer at Myinks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/GHeqlB/TM
---------------------------------------------------------------------~->
Send BUG REPORTS to bugs@xxxxxxxxxxxxx
Send SUGGESTIONS to suggest@xxxxxxxxxxxxx
-----------------------------------------
Post AmiQuote-related messages ONLY to: amiquote@xxxxxxxxxxxxxxx
(Web page: http://groups.yahoo.com/group/amiquote/messages/)
--------------------------------------------
Check group FAQ at: http://groups.yahoo.com/group/amibroker/files/groupfaq.html
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
|