I took the MOBO indicator from this board, and I would like to see a dot  over the price when MOBO is on and no dot when when MOBO is off, but when I tried to do it I  got many dots on the screen.

An example of display would be similair to PSAR indicator except no dot's when not in a mobo.

Any advice would be welcomed.

thnx

rctrade

MOBO

((C - AVGC10) / SQR(ABS(C ^ 2 + C1 ^ 2 + C2 ^ 2 + C3 ^ 2 + C4 ^ 2 + C5 ^ 2 + C6 ^ 2 + C7 ^ 2 + C8 ^ 2 + C9 ^ 2 - 10 * AVGC10 ^ 2) / 10) <= (-.8)) * (10 - 10 * ((C1 - AVGC10.1) / SQR(ABS(C1 ^ 2 + C2 ^ 2 + C3 ^ 2 + C4 ^ 2 + C5 ^ 2 + C6 ^ 2 + C7 ^ 2 + C8 ^ 2 + C9 ^ 2 + C10 ^ 2 - 10 * AVGC10.1 ^ 2) / 10) > (-.8)) - (V >= 1.2 * AVGV30.1) - (V >= 1.5 * AVGV30.1) - (V >= 2 * AVGV30.1)) - ((C - AVGC10) / SQR(ABS(C ^ 2 + C1 ^ 2 + C2 ^ 2 + C3 ^ 2 + C4 ^ 2 + C5 ^ 2 + C6 ^ 2 + C7 ^ 2 + C8 ^ 2 + C9 ^ 2 - 10 * AVGC10 ^ 2) / 10) >= .8) * (10 - 10 * ((C1 - AVGC10.1) / SQR(ABS(C1 ^ 2 + C2 ^ 2 + C3 ^ 2 + C4 ^ 2 + C5 ^ 2 + C6 ^ 2 + C7 ^ 2 + C8 ^ 2 + C9 ^ 2 + C10 ^ 2 - 10 * AVGC10.1 ^ 2) / 10) < .8) - (V >= 1.2 * AVGV30.1) - (V >= 1.5 * AVGV30.1) - (V >= 2 * AVGV30.1))

Can you point me to some MOBO indicator resources so I can try to figure out when you do and don't want dots plotted?

Maybe something like the following Formula in a Custom PCF Indicator using the Dot Plot Style plotted in the same pane and scale as price?

AVGC10 - .8 * STDDEV10 / SGN(((C - AVGC10) / STDDEV10 <= (-.8)) * (10 - 10 * ((C1 - AVGC10.1) / STDDEV10.1 > (-.8)) - (V >= 1.2 * AVGV30.1) - (V >= 1.5 * AVGV30.1) - (V >= 2 * AVGV30.1)) - ((C - AVGC10) / STDDEV10 >= .8) * (10 - 10 * ((C1 - AVGC10.1) / STDDEV10.1 < .8) - (V >= 1.2 * AVGV30.1) - (V >= 1.5 * AVGV30.1) - (V >= 2 * AVGV30.1)))

This helped me:

http://forums.worden.com/default.aspx?g=posts&t=31729

Bruce,
Thanks very much it is almost identical to TOS version which originated from David Elliot. One difference is, in TC the code turns the MOBO off sooner than TOS.

Example AMAZON on Daily
TOS:  MOBO on: 1/5/17.......MOBO Off - 2/3/17 through 2/10/17 (Data ended)
TC: MOBO on 1/5/17...MOBO off 1/17/17...MOBO on 1/25/17...MOBO Off 1/30/17...MOBO on 2/2/17...MOBO off 2/8/17.
In TOS they have some variables, that might be of value but maybe specific to TOS.
Length - 10 periods (Everything is Daily)
Number Dev up = 0.8
Number Dev DN = -0.8
None the less you are awsome... :-)
rctrade

Thanks donv98 will look through it

I use as a True  for MOBO UP (dots below - price above)

C > BBTOP(.8, 10, 0)

and True for MOBO DOWN (dots above - price below)

C < BBBOT(.8, 10, 0)

PUT in PCF % TRUE indicator

I use these for quick alerts, if watching for the break

Just 2 clicks to alert True - A set and forget Alert, brings you back when is true and very quick to set the alert

Now reason I am here

Is there a way thru a pcf to alert the second time the Dots Cross

Close or EVEN High (high probably better)  cross mobo top line, fails then Close crosses back up top mobo x number of bars later

like a reset, SO is True, Then NOT True for a min of 3 bars, then True Again in the Next 12-15 bars

(of course formula for Both Directions)

Thanks

What makes the "second" time the lines cross different than the "third" or "fourth" time the lines cross?

I guess what I'm gettinc at is that unless there is more to your definition than is obvious to me from reading through it (which is quite possible), there isn't really a way to differentiate between a "first" or "second" cross besides besides there being a previous cross.While there will be a "first' cross in a limited data set, that might have actually been a "second" cross if the data set were bigger.

i will put the pre conditions into my scanners, this will take a sold off stock (as pre defined by other conditions)  and put you perfectly on a bull flag pattern using smaller time frame.  Since we dont have auto trendline and or might not have seen the flag developing to draw a trendline for trigger alert, This extremely close in many case.

NOT much use on a trending stock

CBI 5 min chart

https://gyazo.com/85e4fa88e8c4db87f8e23b13a6848690

[/QUOTE]

I use as a True  for MOBO UP (dots below - price above)

C > BBTOP(.8, 10, 0)

and True for MOBO DOWN (dots above - price below)

C < BBBOT(.8, 10, 0)

[/QUOTE]

I use the same C>BBTOP format, but I throw in a C>XAvgC50  (0r C<AvgC50) to be consistent withthe MBOB write up that I found.

NIce, Looks like you are looking for Swings

There isn't a way for any formula I would write to know if it was the first or second time something happened since pre-conditions were met unless those pre-conditions were actually included in the formula somehow.

i will do the pre conditions

just out like the formula for

True first , Then NOT True for a min of 3 bars, then True Again no sooner than 8 bars later

i should be able to alert what you send me if i need to tweek it

I am going to interpret that as true, then not true for 3 to 8 bars, then true. Not sure if this is correct or not, but when I try to interpret it literally, I get True, then not true for 3 bars and/or not true for 8 bars, then true.

For price closing above the top I would get the following.

C > BBTOP(.8, 10) AND ABS(SinceTrue(C1 > BBTOP(.8, 10, 1), 9) - 5.5) <= 2.5

And for price closing below the bottom I would get the following.

C < BBBOT(.8, 10) AND ABS(SinceTrue(C1 < BBBOT(.8, 10, 1), 9) - 5.5) <= 2.5

would like the first TRUE to remain in true state min 3 bars

opps did not know you already posted sorry i will see what i can do with this

THIS IS PERFECT thanks

Are you sure? Because I didn't check for true at least  bars, then false at least 8 bars, then true.

I tested for true (any number of bars), then false from 3 to 8 bars, then true.

the at least part is really what i am looking for, because indicate a pullback then recross of multiple bars, which will most of the time be a flag pattern

I have created a flag pattern recognition formula that is very good, but since i cannot draw a trendline on all the symbol in the scanners, the would bring to the scanner at a good time to see it.

SO a little tweek on the at least part would be appreciate

Thanks

Please try the following for the closing price being above the BB top.

C > BBTOP(.8, 10) AND SinceTrue(C1 > BBTOP(.8, 10, 1), 8) = -1 AND SinceTrue(C9 > BBTOP(.8, 10, 9), 446) = SinceTrue(TrueInRow(C9 > BBTOP(.8, 10, 9), 3) = 3, 446)

And the following for the cloning price being below the BB bottom.

C < BBBOT(.8, 10) AND SinceTrue(C1 < BBBOT(.8, 10, 1), 8) = -1 AND SinceTrue(C9 < BBBOT(.8, 10, 9), 446) = SinceTrue(TrueInRow(C9 < BBBOT(.8, 10, 9), 3) = 3, 446)

See the two instances of 446 in each formula? This (+9) is how many bars back the last time the closing price can have last been above (for the first formula) or below (for the second formula) the Bollinger Bands and have the program still check for the last time being at least 3 bars in a row.

I suspect you want to significantly reduce those numbers. It is highly likely that price closed above or below the bands much more recently, the very long periods make the formulas slow and unable to calculate for newer symbols, and is being above or below the BBs that many bars back significant to your analysis in any case?

Thanks for all the effort.  FWIW the first formual did NOT mark the CBI 5M chart on May 18th, but the last post nailed it just as written

Thanks

Not exactly following the 446 part, how many bars are we looking back using this 446

I am see the Down indicator showing True when the last bar True was like 45 bars ago

maybe should be True for the 3 bars min, the Not true for min of 8 and a Max of 20

that when the 2nd True appears before 20 bars pass (if not restart to the Next 3 bars min True)

Please try the following for the closing price above the BB top.

C > BBTOP(.8, 10) AND ABS(SinceTrue(C1 > BBTOP(.8, 10, 1), 22) - 14) <= 6 AND SinceTrue(C9 > BBTOP(.8, 10, 9), 14) = SinceTrue(TrueInRow(C9 > BBTOP(.8, 10, 9), 3) = 3, 14)

And the following for the closing price below the BB bottom.

C < BBBOT(.8, 10) AND ABS(SinceTrue(C1 < BBBOT(.8, 10, 1), 22) - 14) <= 6 AND SinceTrue(C9 < BBBOT(.8, 10, 9), 14) = SinceTrue(TrueInRow(C9 < BBBOT(.8, 10, 9), 3) = 3, 14)

Real Hard to tweak these into consitent usable setups.  Lets try something simplier

Low Price during last 20 candles LESS THAN 10 SMA

High Price during last 15 Candles GREATER THAN 10 SMA

now lets do 2 formulas using the above as the beginning

(#1  Part A )Low Price -.05 cents < lower (Mobo) BBBOT(.8,10,0)  ***(after the High price was greater than 10 SMA - so in the next 15 bars

(#1 Part B) Close Cross up 10 SMA)

****************************************************

Next alter Part B to the below on Formula #2

(#2 all of the above EXCEPT Part B)

(#2 Part B)  Close Crossing up upper (Mobo) BBTOP(.8,10,0)

Thanks

This is what I consider the most literal interpretation of your request (but there are numerous other possible interpretations). Here is the base formula.

CountTrue(L1 < AVGC10.1, 20) > 0 AND CountTrue(H1 > AVGC10.1, 15) > 0

#1

CountTrue(L1 < AVGC10.1, 20) > 0 AND CountTrue(H1 > AVGC10.1, 15) > 0 AND L - .05 < BBBOT(.8, 10) AND XUP(C, AVGC10)

#2

CountTrue(L1 < AVGC10.1, 20) > 0 AND CountTrue(H1 > AVGC10.1, 15) > 0 AND L - .05 < BBBOT(.8, 10) AND XUP(C, BBTOP(.8, 10))

looks like you did a great job interpreting HA! If i can read it, Thanks

Those look good on the charts could you inverse that of course using or if I change the BBBOT to BBTOP and of course the L to H etc,  I think i can get it

What is the inverse of XUP

The smart money is on XDOWN.

If you liked the results, then the inverse would probably be the following for the base formula.

CountTrue(H1 > AVGC10.1, 20) > 0 AND CountTrue(L1 < AVGC10.1, 15) > 0

#1

CountTrue(H1 > AVGC10.1, 20) > 0 AND CountTrue(L1 < AVGC10.1, 15) > 0 AND H + .05 > BBTOP(.8, 10) AND XDOWN(C, AVGC10)

#2

CountTrue(H1 > AVGC10.1, 20) > 0 AND CountTrue(L1 < AVGC10.1, 15) > 0 AND H + .05 > BBTOP(.8, 10) AND XDOWN(C, BBBOT(.8, 10))

thanks

You're welcome.