|
PureBytes Links
Trading Reference Links
|
>>After that
:trade I was doing some system testing, and found that Chart Scanner
:running on 1/27 no longer reflects the trade I executed on 1/26 nor the
:signal it gave me on 1/26.<<
The first step I'd take is to determine whether the trade signal on 1/26 was supposed to happen. Also for 1/27. Have you worked out the calcs manually? What result did you find?
Manual calculation isn't so bad when you transcribe most of the system into an indicator and plot the relevant values. You can then inspect the indicator values using the View / Data Window command.
-Mark Jurik
-----Original Message-----
From: Peter2150@xxxxxxx [SMTP:Peter2150@xxxxxxx]
Sent: Wednesday, January 27, 1999 11:32 AM
To: omega-list@xxxxxxxxxx
Subject: Re: Need Help with TS Inconsistency
In a message dated 99-01-27 14:17:11 EST, magnus@xxxxxxxxxxx writes:
> Welcome to the wonderful world of TradeStation!! This shit happens to me at
> least twice a quarter. The only solution that I came up with is to run 2 TS
> on 2 different computers. Once you get a signal, exit one TS and its
Server.
> Then enter the offline server. If the signal is there, it's valid. Then
> re-enter the online server. Later that night, paste in data from the
machine
> that was never touch.
>
> If anyone has another solution, please let me know.
Not sure its just Tradestation. I used to work in the Data processing of
oilfield siesmic and regular well log data, using DEC Vax computers, and in
house software. It was always wise to have an idea of the answers expected,
to verify what the computer said made sense. Seems to me that applies here
also. Once should understand ones system well enough, that when the computer
gives a signal you can verify it by looking at the data. This would seem
wise, anyway in view of the fact that how the decimals stack up could mean the
difference between a signal and no signal, on the slightest variance in the
data. Saw this with mechanical devices. Every part had a tolerance,
|