|
PureBytes Links
Trading Reference Links
|
A good system is always going to have multiple open orders ......
1) fixed-from-entry stop loss
2) quick profit take-out stop
These are just a few examples.
The fact that WhichExit() and WhichEntry() capabilities are absent in
TS2000i is simply a reflection of the poor customer relations and DRAMATIC
lack of attention-to-detail that has plagued Omega Research thru the TS2000i
debacle thus resulting in a crippled company incapable of moving forward in
a changing environment.
Totally amazing to see the tech support response to this "enhancement
request"; It took about 3 attempts to get them to even UNDERSTAND the issues
related to this.
> -----Original Message-----
> From: Rich Estrem [mailto:estrem@xxxxxxxxxxxxx]
> Sent: Monday, August 07, 2000 8:59 PM
> To: omega-list@xxxxxxxxxx
> Subject: RE: Same day exits
>
>
> I fail to see how these proposed functions would help Mel. The
> solution has always been to move to a smaller timeframe until only
> 1 event is likely to occur in each bar. Bill's reply is right on.
> Trying to shoehorn multiple trades into a single bar is asking
> for trouble. I liked the toggle option in old System Writer Plus
> of not allowing stops on the bar of entry. It was scary on daily
> data, but amazing how often it improved test results.
>
> rich
>
> BTW - requests for enhancements to TS2000i are like asking for
> enhancements to DOS 6.2 from Microsoft. Its a "legacy" product.
>
>
>
>
> At 04:10 PM 8/7/00 -0500, you wrote:
> >Bill - there is an enhancement request into Omega on this for TS2000i:
> >
> >WhichExit(0) and WhichEntry(0)
> >
> >These intrinsic functions are to return the actual coded entry
> and exit and
> >maintain a history of the values similar to EntryPrice() and
> BarsSinceExit()
> >
> >if H > 1430 then ExitLong("Xlong") at Stopval Stop;
> >
> >if the above results in an exit, then WhichExit(0) will have a value of
> >"Xlong"....
> >
> >This functionality is BADLY needed. Current workaround: create a
> >COM-compliant DLL and use the DEVKIT API functions to access the Message
> >center data.
> >
> >Anyone care to try ?
> >
> >> -----Original Message-----
> >> From: Bill Wynne [mailto:tradewynne@xxxxxxxxxxx]
> >> Sent: Monday, August 07, 2000 12:11 PM
> >> To: melsmail@xxxxxxxxxxx; omega-list@xxxxxxxxxx
> >> Cc: code-list@xxxxxxxxxxxxx
> >> Subject: Re: Same day exits
> >>
> >>
> >> >From: "Mel F" <melsmail@xxxxxxxxxxx>
> >>
> >> >I am trying to exit on the bar of entry only using following code
> >> >Buy{setup condition} next bar at open + Value1;
> >>
> >> >In a separate signal I have two exits as follows
> >> >If marketposition <> 1 then begin
> >> > ExitLong("1stDayProfit") Open tomorrow + Value10 limit;
> >> > ExitLong("1stDayLoss") Open tomorrow - Value20 stop;
> >> >end;
> >>
> >> Since you have a limit and a stop in the same bar it is
> impossible for TS
> >> (or any program) to know in which order they occurred after your
> >> entry from
> >> OHLC daily data. In short: forget about it. The only thing you
> know about
> >> the order of the OHLC is that the Open was first and the Close
> >> was last. The
> >> order of everything in between is unknown without tick data, so
> >> even if your
> >> idea is programmed "right" the data will be useless.
> >>
> >> Bill Wynne
> >>
> >> Bill@xxxxxxxxxxxxxxx
> >>
> >> >What I am finding is that if the Entry price is greater than the
> >> >ExitLong("1stDayProfit") price it exits at the Entryprice
> >>
> >> Try exitlong at entryprice + valueX.
> >>
> >> >If I change from limit to a stop order for ExitLong("1stDayProfit")
> >> > and the high is less than the ExitLong("1stDayProfit") price it also
> >> >exits
> >> >at the entryprice
> >> >
> >> >How can I code it to exit correctly on the same day as entry?
> >> >
> >> >Mel
> >> >melsmail@xxxxxxxxxxx
> >> >
> >>
> >
> >
> >
>
|