|
PureBytes Links
Trading Reference Links
|
------------------------------------------------------------------------
You cannot reply to this message via email because you have chosen not
to disclose your email address to the group.
To reply: http://groups.yahoo.com/group/equismetastock/post?act=reply&messageNum=5740
------------------------------------------------------------------------
Russ
You've opened up a whole can of worms here but I'll stick my neck out and
try and answer your questions from my own experience. If you're using MS 8
then some of the following suggestions may not apply.
1. Create the bulk of your code (Enter Long, Close Long, etc) as indicators
rather than within a system tests. If you really MUST use optimisation then
you will have a harder road to hoe but that's your choice. The thing with
indicators is that they can be dropped onto a chart or called by a system
test, exploration or expert or whatever. The indicator need only be changed
once and the changes are automatically applied to any other tool that uses
it.
2. Indicator code is much easier to troubleshoot and fix than code developed
in other tools (because you can see it). I strongly suggest that all your
explorations and system tests be constructed first as indicators whatever
the intended use. What you can see you can understand and probably fix. What
you can't see is much more difficult to understand and fix.
3. Create single-bar signal outputs instead of multiple-bar outputs. This
will very rarely create a problem but it sure can save a lot of heartache.
This is easily accomplished in a number of ways and the most common way to
convert a signal to a single bar (true) is to use the "Cross" function
instead of using the "<" or ">" tests. Another way to achieve the same
result is to change your "Signal" output line to "Signal AND
Ref(Signal,-1)=0". Even better, use "Signal AND Alert(Signal=0,2)". What
these are saying in English is "The Signal is true today and it was false
yesterday".
4. Learn to use "latches" in your code. These have a multitude of uses and
will enable you to solve many MS problem situations. You can read more about
latches at
http://groups.yahoo.com/group/equismetastock/files/Using%20Latches%20in%20MS
.doc so I won't labour the point here. Suffice it to say that a latch will
give you the ability to discriminate between the FIRST entry signal and a
multitude of subsequent entry signals. If you want to "remember" what price
you paid on entry then a latch is the tool that will do it for you.
5. Having just struggled with latches you're probably in no mood to be told
to look at 'Trade Equity'. So I won't tell you, but you can find more
information in the files section of this group if you want.
Sorry this is rather short on actual code but I can assure you'll learn more
by doing the work yourself. I'm happy to help if you get stuck, but if you
get stuck with the suggestions above you probably don't want my help anyway.
Roy
> I'm hoping you system test guru's have an easy way to pass values
> between buy and sell systems test. At the end of my Buy test I set
> the a variable called "BuyPrice" = close. I want to add the following
> IF statement in my sell test:
> SellTrig1 := If(close < BuyPrice * .90),1,0).......in other words if
> the close drops 10% below the sell price then SellTrig1 is 1. The
> system tester gives me an error that it doesn't recognized the
> variable name. Any ideas or examples of successful code that does
> this would be greatly appreciated.
>
> Another system test question....is there any way to display the
> values of a variable somewhere in the system test. I realize I can
> write a function to display variable values but was trying to avoid
> writing a function everytime I wanted to see a variable value.
>
> Thanks in advance for your assistance.
>
> Regards, Russ
>
>
> To unsubscribe from this group, send an email to:
> equismetastock-unsubscribe@xxxxxxxxxxxxxxx
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
To unsubscribe from this group, send an email to:
equismetastock-unsubscribe@xxxxxxxxxxxxxxx
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
|