|
PureBytes Links
Trading Reference Links
|
Ron:
You need to be more specific than "sometimes it does not work".
Print out your order date-time, the buy stop value for the next
bar; than, print out the date-time of the NEXT bar along with the
value of the high. Compare the two values. If it is indeed the
case that your system fails to buy when the stop price is reached
or exceeded then you have a coding error.
(As far as I know, TS is completely reliable and bug fee in its
behavior.)
Leslie
Ron Mihaley wrote:
>
> Can someone tell me if I forgot to do something that
> will make my strategy not work all of the time.
> Using TS2000i, with Windows 2000.
>
> Problem is that I code a buy signal such as defined by
> EasyLanguage:
>
> Buy next bar at buyprice or higher.
> or
> Buy next bar at buyprice stop.
>
> The help in EasyLanguage states:
> context used within a strategy.
> Higher means stop when used in the following context:
>
> Buy next bar at 75 or Higher;
> Or
> Buy next bar at 75 Stop;
>
> Generates an order to enter a long position on the
> next bar at a price of 75 or higher.
>
> But, when I test this, sometimes it works and
> sometimes it does not.
>
> I am using 5 minutes timeframe, so I must be using the
> 1 min data in the Global Server.
>
> If I code an indicator, I find that sometimes the
> indicator shows the High higher than buyprice yet the
> strategy did not work. Other times the strategy works
> correctly.
>
> If this is one of the may "bugs", then is there a work
> around?
>
> =====
> Ron
--
Regards,
Leslie Walko
610-688-2442
--
"Life is a tragedy for those who feel, a comedy for those who
think"
Horace Walpole, 4th earl of Orford, in a letter dated about 1770
|