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

Re: [EquisMetaStock Group] TRAILING STOP LOSS



PureBytes Links

Trading Reference Links

Hi - Shootingstar
that is exactly the problem. thus the system tester is not giving accurate results. I have given up at present and reverted back to excel programming for this system. But this is a major problem with metastock then. Most systems would like a Trailing Stop and thus optimising and testing on meta is useless. Firstly - repeating all the entry conditions in the exit long section - slows down the testing dramatically and to top that - a repeat Buy signal resets the Trailing Stop. There must be a simpler way out - surely. Metastock is so good in all other respects.
 
Hi Richard
Saw the link - but it asks for inputs to determine the trailing stop. That is not possible for system testing nor for multiple stocks - since then manually entering the data everyday wud be cumbersome.
 
Is there not anyone else who has cracked this issue ? Roy - surely you must have ?
 
Regards
Sharad Lohia
 
 
----- Original Message -----
Sent: Tuesday, May 24, 2005 5:14 AM
Subject: RE: [EquisMetaStock Group] TRAILING STOP LOSS

This is why I wrote an external DLL to do the trailing stop referenced to the entry day.
 
See:
 
Even better, it's free.
 
Best regards,
Richard Dale.
Norgate Investor Services
- Premium quality Stock, Futures and Foreign Exchange Data for
  markets in Australia, Asia, Canada, Europe, UK & USA -
 


From: shootingstar_720 [mailto:booki100@xxxxxxxxxxx]
Sent: Monday, 23 May 2005 13:35
To: equismetastock@xxxxxxxxxxxxxxx
Subject: Re: [EquisMetaStock Group] TRAILING STOP LOSS

Hello Sharad, was just doing a little (actually, a lot!) of research
on this very problem and came across this thread. If I understand
correctly - you are looking for a way to designate / tell the system
tester on which day a position was opened - such that any trailing
stop can be programmed to operate from this day? My particular issue
is that if you have several varying entry signals, yet you want to
tell the system tester to trail a stop from the day of entry, it is
impossible for it to discern from which day it should begin
calculating (since, if one of the entry signals occurred 2 days ago,
but the system was already long, then the trigger for the
calculation of the trailing stop would have occurred 2 days ago -
not the result intended.) Curious if you have found any solution /
work around to this issue? Haven't given up hope yet..



Yahoo! Groups Links