[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Entering on a stop: Bug in Tradestation 4.0?



PureBytes Links

Trading Reference Links


TS acts as your broker MIGHT DO - if the price is touched but not 
exceeded your broker might trade for you or might not (depends on the person 
or the firm) - down to the rules he should buy MARKET as soon as the STOP is 
hit, but some use discretion and "want to help you" :--)))....as it shows in this 
case, its not always better :--))...makes TS nearly human....

rgds hans




> I just discovered a possible bug in TS 4.0 and I wonder if somebody else
> has any knowledge/experience of it.
> 
> Here's the deal.  Let's say you've got a system applied to a chart and you
> are wanting to enter on a stop.
> 
> You've set up your stop price with something like:
> LEntryPrice = xxx;
> where xxx is some value you've calculated.
> 
> You have a statement something like
> BUY AT LEntryPrice STOP;
> 
> This should cause TS to enter a trade (let's assume you are flat) on the
> next bar if the LEntryPrice is touched.
> 
> I have run into a situation where it does not do this. Here are the
> specifics.  Note that all have been verified with print statements.
> 
> 5 minute chart.
> LEntryPrice = 840.35
> At 15:20 the BUY AT LEntryPrice STOP  statement is executed.
> At 15:25 the bar has an Open = 840.35.  This is also the high of the bar.
> This is the first bar at which the LEntryPrice has been reached. The 15:30
> bar is completely below 840.35. The 15:35 bar opens at 841.00.  This is
> the low for the bar as well. TS enters on the 15:35 bar at 841.00.
> 
> In the EasyLanguage manual it states, "A Stop order in a buy statement
> tells TradeStation to take a long position on the next bar at the *Extra
> measure* price level or anything higher."  LEntryPrice *is* the "Extra
> measure" price.
> 
> IMO, TS should have entered on the 15:25 bar at 840.35.  Does anyone have
> any insight as to why this is not happening?  I checked the Omega Bug list
> and it is not mentioned.
> 
> Thanks,
> Chris McMurry
>