Rank: Newbie
Groups: Registered, Registered Users Joined: 5/29/2011(UTC) Posts: 3
|
Is there a way of modifying the MACD Buy Signal explorer to only show those securities that have MACD cross over below the '0' line. If it can show the MACD cross-line in a deep slope down, that would be even better.
Many thanks for any guidance.
norm82
|
|
|
|
Rank:: Advanced Member
Groups: Registered, Registered Users, Subscribers Joined: 5/13/2005(UTC) Posts: 715 Location: Midwest, USA
Was thanked: 1 time(s) in 1 post(s)
|
>>Is there a way of modifying the MACD Buy Signal explorer to only show
those securities that have MACD cross over below the '0' line.
Add the condition: AND MACD()<0
>> If it can show the MACD cross-line in a deep slope down,
Not sure which line you mean here -- the MACD or the SignalLine?
And, don't you mean "steep slope up"? Which would have to be the case, if the MACD is crossing up over the Signal Line for a BUY signal?
Either way, you could use ROC to see how fast whichever line you're interested in is rising or falling.
|
|
|
|
Rank: Newbie
Groups: Registered, Registered Users Joined: 5/29/2011(UTC) Posts: 3
|
Thanks Jonathan. I put the AND MACD()<0 into the filter and it seems to work well.
I am new to metastock and first time on the forum. When you said use ROC, could you expand on the coding, please. Also, would it go into the filter as well?
Many thanks from a newbie.
Norm82
|
|
|
|
Rank:: Advanced Member
Groups: Registered, Registered Users, Subscribers Joined: 5/13/2005(UTC) Posts: 715 Location: Midwest, USA
Was thanked: 1 time(s) in 1 post(s)
|
>When you said use ROC, could you expand on the coding, please.
Code example: ROC(C,3,%)>0.1; Look up details in HELP (F1).
>Also, would it go into the filter as well?
If you want -- you're the one who thought it up! Use another AND statement with the rate of change function.
>Many thanks from a newbie.
Suggestion: So you can visually see what you are creating/combining, add new Inner Windows and plot each element of your code into it's own window. Then, put the combined code into a Custom Indicator and drag that down into the main window, so you can see if it's doing what you want (in comparison to the separate "pieces".
Also: Look up the use of FML and FMLVAR in the manual or Help -- since you can call an indicator from an Exploration, it's better to keep only one version of your code -- this can prevent repeating mistakes in logic, typos, settings, etc.
|
|
|
|
Users browsing this topic |
Guest (Hidden)
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.