|
|
Search
You searched for the word(s):
< 1 second(s)
-
Vinny:
Here is some code from a system test that you can use to assemble your own explorations for various RMO conditions:
{An RMO buy signal is generated on the first bar when all three conditions are met:}
{RMO oscillator is positive indicating bullish conditions}Long1:=IF(Fml(''Rahul Mohindar Osc ...
-
Thanks very much ! :)
Deleting OR renaming the file COMMLIST did the trick. MS created a new copy of the file to work with, and everything seemed fine after that.
Deleting or renaming the file EQ_SLIST did NOT solve the problem in my case.
-
Maybe this will help. The following code would set a stoploss of $0.10 below the low of the most recent day on which the BuySignal was generated. How you define whether BuySignal is true or not is up to you.
StopLoss:=ValueWhen(1,BuySignal,Low-0.10);
-
The following, I believe, would give you the linear regression slope of the last five days of the 50-day simple moving average of the close. Substitute the indicator of your choice ... ;)
Slope50:=LinRegSlope(Mov(Close,50,S),5);
-
Bump.
The problem still persists, but I can actually save the list in spite of the error message ... ???
-
Amita:
For what it's worth, here's some extremely simplistic coding I did some time ago for Elder's ''Impulse System'' .....
Entry Signal:
AVG:=Mov(Close,13,e);Hist:=Fml(''MACD Histogram'');
Avg>Ref(AVG,-1) ANDHist>Ref(Hist,-1)
Exit Signal:
AVG:=Mov(Close,13,e);Hist:=Fml(''MACD Histogram'');
Avg<Ref(AVG,-1) ...
-
My MSv10 will no longer let me save the results of explorations into new ''Favorites'' folders. It keeps flashing an error message ''Unable to add name to list file. Named list file is full.''
I deleted the old ''favorites.dta'' file, but this did not solve the problem. Is there another file I need to examine ?
-
Jason:
What you refer to sounds like the ''PowerScreener'' functionality which is in the new MS v. 10. I believe that you must pay for this service after the first 30 days.
-
Thought it was worth a try to ask ...
-
You could try something like this :
Test1:=Low<Mov(C,21,S);
Test2:=BarsSince(Test1)>=30;
And only proceed if Test2 is true ...
-
Still Can't find my vapours ... sure I left them lying around somewhere ...
Hey ... Do you think I could still be free if I don't trade the FOREX ?
-
... Durn ! I seem to be out of vapour ...
Guess I'm gonna miss this one.
-
John:
An interesting problem. Here is one way I have found of setting the initial stop loss, illustrated by some code taken from another post (# 22224) discussing the RMO system:
{variable a7 is the initial stop loss set at ''a couple of ticks'' below the low of the bar preceding the entry signal}
a5:=(Fml(''Rahul ...
-
Please try double clicking on the date bar at the bottom of the chart. This should bring up a window which allows you to specifiy how many bars of data are loaded, and how many are actually displayed.
You can also get to this window by selecting ''Format'' and ''x-axis'' from the tool bar at the top of your Metastock window.
Hope that ...
-
Blue Eyes:
Here's a bit of code for a trailing stop that I have found useful:
F1:=0.80*Close;
If(F1>=PREV AND LOW>PREV, F1, If(Ref(LOW,-1)<Ref(PREV,-1), Ref(F1,-1), PREV))
F1 is the function for the trailing stop ... in this case a 20% ...
-
Yes. Thanks for the code. I put it into my explorer, and into my system tester to set up a quick performance test to see if I was interested in pursuing further study of the RMO method.
For the last 1000 daily bars of the NASDAQ 100 (Longs only; excluding data from IOMEGA, which generated error messages), RMO generated about a 36%
|
|