Hi jigshir This exploration will report 1 for the Stochastic crossing above 50, and -1 for the stochastic crossing below 50. {ColA} Cross(Stoch(5,3),50) - Cross(50,Stoch(5,3)); {Filter} colA; If you want to separate crosses above from crosses below then you could use the following exploration. {ColA} Cross(Stoch(5,3),50); {ColB} Cross(50,Stoch(5,3)); {Filter} colA OR colB; Make sure that you load at least 50-100 data bars for this exercise. Do not use the "Load Minimum Records" option for number of bars to load. Doing so would be as ridiculous as trying to make sense of a chart with only 7 or 8 bars loaded. You mentioned "alert" in your request. To me that suggests getting an Alert from the Expert Advisor, which could use very similar code but is a quite different tool from the Explorer and probably not what you want. Roy

Hi jigshir

There are obvious code mistakes in your sample. MetaStock will always five you some sort of reason for the errorn even if that reason is not immediately clear..

Here are some things to check.

1. Are header comments enclosed in {}. These are called braces braces and should surround any text that is not part of the MetaStock formula you're trying to create. Anything inside braces is a comment and MetaStock ignores all comments. Any text not surrounded by braces is regarded as MetaStock code and it is checked for correct syntax etc.

2. Always terminate a variable definition with a semicolon - even the last variable or line of code. It's not strictly necessary on the last line of code but it's good practice to do so. Ensuring that semicolons are in place means that MetaStock will point to the problem variable and nowhere else (if there really is a problem). Typically the cursor will blink at the beginning of the problem variable, not somewhere further down.

3. Check that you have written the code for each variable correctly (whether named or not).

4. If necessary comment out all code but the first variable and then work your way down until the problem rears its head (shows itself). Be aware that one pair of braces must be closed before encountering another pair of braces, as shown below.

{Comment}
{first variable to test}
{Comment}
{Second variable to test}
{Comment}
{Third variable to test}

Comments must always be enclosed in braces. Variables (your code) can be selectively commented to identify the problem variable. Just be aware that commenting out a variable that is needed for a subsequent active variable will under most conditions force MetaStock to wrongly point to the active variable that cannot find its commented out element.

5. It's usually helpful to copy code from a failing exploration into the Indicator Builder as a new indicator. Troubleshooting indicator code is generally much easier to troubleshoot than experts, explorations or systems because you can check each variable or element visually. This is particularly so when your code fails to produce a result but does not signal an error condition.

Now it's time for you to troubleshoot your own code.

Roy

Edited by user Monday, August 10, 2015 5:02:17 AM(UTC)  | Reason: typo in item 5