StockFetcher Forums · General Discussion · A COMPLETE LOGIC SYSTEM - ANOTHER GIFT FROM AVERY << 1 ... 5 6 7 8 9 ... 10 >>Post Follow-up
jaketheguy
52 posts
msg #38006
Ignore jaketheguy
9/16/2005 1:47:59 PM

alf...yes, the description had the minor error. However, if you look at the logic in the filter, I think it fits what you were trying to do.

Unfortunately, StockFetcher says the filter has too many set statements. What is the workaround for that?

jaketheguy
52 posts
msg #38007
Ignore jaketheguy
9/16/2005 1:58:02 PM

Sorry Alf, I did carry through the error in the explanation statement into the filter. The corrected filter is below:

Fetcher[/* open OR close 3 days ago is below high 4 days ago
AND open OR close 3 days ago is above low 4 days ago
AND open OR close 2 days ago is below high 4 days ago
AND open OR close 2 days ago is above low 4 days ago , etc.
*/

set{hi4, high 4 days ago}
set{lo4, low 4 days ago}

set{3A, count(open below hi4, 1) 3 days ago}
set{3B, count(close below hi4, 1) 3 days ago}
set{OR31, 3A + 3B}
set{3C, count(open above lo4, 1) 3 days ago}
set{3D, count(close above lo4, 1) 3 days ago}
set{OR32, 3C + 3D}
set{AND3, OR31*OR32}

set{2A, count(open below hi4, 1) 2 days ago}
set{2B, count(close below hi4, 1) 2 days ago}
set{OR21, 2A + 2B}
set{2C, count(open above lo4, 1) 2 days ago}
set{2D, count(close above lo4, 1) 2 days ago}
set{OR22, 2C + 2D}
set{AND2, OR21*OR22}

set{1A, count(open below hi4, 1) 1 days ago}
set{1B, count(close below hi4, 1) 1 days ago}
set{OR11, 1A + 1B}
set{1C, count(open above lo4, 1) 1 days ago}
set{1D, count(close above lo4, 1) 1 days ago}
set{OR12, 1C + 1D}
set{AND1, OR11*OR12}

set{0A, count(open below hi4, 1)}
set{0B, count(close below hi4, 1)}
set{OR01, 0A + 0B}
set{0C, count(open above lo4, 1)}
set{0D, count(close above lo4, 1)}
set{OR02, 0C + 0D}
set{AND0, OR01*OR02}

set{ANDALL, AND3*AND2*AND1*AND0}

show stocks where ANDALL is equal to 1
]

But unfortunately, it has too many sets.

jaketheguy
52 posts
msg #38032
Ignore jaketheguy
9/17/2005 10:28:54 PM

alf...IT IS DONE! Below is the filter you requested, which defines a series of days whose Open OR Close falls within the High/Low Range of some bar 5 days ago. See below:

Fetcher[set{hi4, high 4 days ago}
set{lo4, low 4 days ago}

set{OR31, count(open below hi4, 1) 3 days ago + count(close below hi4, 1) 3 days ago}
set{OR32, count(open above lo4, 1) 3 days ago + count(close above lo4, 1) 3 days ago}
set{AND3, OR31*OR32}

set{OR21, count(open below hi4, 1) 2 days ago + count(close below hi4, 1) 2 days ago}
set{OR22, count(open above lo4, 1) 2 days ago + count(close above lo4, 1) 2 days ago}
set{AND2, OR21*OR22}

set{OR11, count(open below hi4, 1) 1 days ago + count(close below hi4, 1) 1 days ago}
set{OR12, count(open above lo4, 1) 1 days ago + count(close above lo4, 1) 1 days ago}
set{AND1, OR11*OR12}

set{OR01, count(open below hi4, 1) + count(close below hi4, 1)}
set{OR02, count(open above lo4, 1) + count(close above lo4, 1)}
set{AND0, OR01*OR02}

set{AND32, AND3*AND2}
set{AND10, AND1*AND0}
set{ANDALL, AND32*AND10}

show stocks where ANDALL is above 1
]

The problem and the resulting filter demonstrated well the concepts that were the subject of this thread.

Cheers!

jaketheguy
52 posts
msg #38034
Ignore jaketheguy
9/17/2005 10:37:29 PM

As alf stated earlier in the thread, the objective of the above filer was to identify areas of "congestion" on a chart, where "congestion" is defined as a minimum of 5 daily bars...made up of a "Measuring Bar" and followed by (at least) 4 subsequent bars whose Open OR Close falls within the High/Low Range of that "Measuring Bar".

And the filter below (posted earlier in the thread), defines even a tighter "congestion", where the Open AND Close of the 4 subsequent bars falls within the High/Low Range of that "Measuring Bar".

Fetcher[set{hi4, high 4 days ago}
set{lo4, low 4 days ago}
open 4 day high is below hi4
and open 4 day low is above lo4
and close 4 day high is below hi4
and close 4 day low is above lo4
]

alf44
2,025 posts
msg #38037
Ignore alf44
9/17/2005 11:13:35 PM

jaketheguy,

This is what I finally came up with:

Fetcher[set{HI4, High 4 days ago}
set{LO4, Low 4 days ago}

set{sum1, sum(Close,4)}
set{sum2, sum(Open,4)}

set{CLavg, sum1 / 4}
set{OPavg, sum2 / 4}

Show all stocks where CLavg is less than HI4
and CLavg is greater than LO4
and OPavg is less than HI4
and OPavg is greater than LO4
and Close is between 5 and 50
and Average Volume(65) is greater than 500000
and Shares Outstanding is less than 25

and Draw EMA(10)
and Draw EMA(30)
and Draw EMA(150)

and Draw Price Line at High 4 Days ago
and Draw Price Line at Low 4 days ago
and Draw RSI(10)
and Draw CEMA(RSI(10),30)
and Draw RSI(10) line at 60
and Draw RSI(10) line at 40
and Draw MACD(3,10,16)
and Draw R Squared(10)
and Draw R Squared(10) line at .80
and Draw R Squared(10) line at .20
and Draw ADX(10)
and Draw ADX(10) line at 30
and Draw ADX(10) line at 18
and chart-time is 3 months

and do not Draw CLavg
and do not Draw HI4
and do not Draw LO4
and do not Draw OPavg

add column HI4
add column LO4
add column CLavg
add column OPavg
]

---------------------------------

I tried a number of different ways using "sets" and "logic" and kept running into "SF nesting issues" (I guess that's what the prob was). Anyway, the filters wouldn't run. Much like the probs you seemed to be having earlier. I finally decided to try the "sum" feature in addition to the "sets"...I took an AVERAGE CLOSE and an AVERAGE OPEN of the last 4 days and insured that those AVERAGES were between the Range of the "Measuring Bar" 4 days ago. For the most part it seems to return what I was looking for.

The filter I posted above also has some of the indicators and critical lines on those indicators I like to look at. It has lines drawn at the HI4 and LO4 (4 days back). These lines illustrate a "channel" or "congestion" area. The idea being that you would look for a breakout (either above or below) this congestion area. Some of the other indicators I have drawn on the chart give some indication which way the "breakout" might go. That's the hope anyway. Also, the filter finds stocks with Shares Outstanding of below 25 Million...as well as Price and Volume criteria.

Anyway, congrats on your work. Nice job ! I'll check it out in more detail later. This whole exercise has been helpful to me. It has forced me to dig and study in more detail some of the stuff cegis and RumpledOne and others have been doing with their scans. Yepher's site has been very helpful too. I realize that there is a whole nuther level of expertise at using SF. I have much to learn. :)

Thanks again to you and to everyone who was helpful.

I'll post more as I play with these scans some. You do the same !

Regards,

alf44

TheRumpledOne
6,371 posts
msg #38053
Ignore TheRumpledOne
9/18/2005 1:08:25 PM

Nice work using SUM!

MAY ALL YOUR FILLS BE COMPLETE.

jaketheguy
52 posts
msg #38117
Ignore jaketheguy
9/20/2005 11:44:38 PM

BTW, is AVERY the TRO fellow, or is he someone else?

Thanks.

 shelupinin120 postsmsg #38118- Ignore shelupinin 9/21/2005 9:09:29 AMThe name of TRO is Avery. TheRumpedOne, if I expose you? :) sorry if yes...
shelupinin
120 posts
msg #38119
Ignore shelupinin
9/21/2005 9:13:39 AM

alf44, could you explain what does "and Shares Outstanding is less than 25" mean? thanks
Alex

TheRumpledOne
6,371 posts
msg #38120
Ignore TheRumpledOne
9/21/2005 9:43:57 AM

LOL.. I am Avery aka THERUMPLEDONE!!

 StockFetcher Forums · General Discussion · A COMPLETE LOGIC SYSTEM - ANOTHER GIFT FROM AVERY << 1 ... 5 6 7 8 9 ... 10 >>Post Follow-up

*** Disclaimer *** StockFetcher.com does not endorse or suggest any of the securities which are returned in any of the searches or filters. They are provided purely for informational and research purposes. StockFetcher.com does not recommend particular securities. StockFetcher.com, Vestyl Software, L.L.C. and involved content providers shall not be liable for any errors or delays in the content, or for any actions taken based on the content.

Copyright 2021 - Vestyl Software L.L.C.Terms of Service | License | Questions or comments? Contact Us
EOD Data sources: DDFPlus & CSI Data Quotes delayed during active market hours. Delay times are at least 15 mins for NASDAQ, 20 mins for NYSE and Amex. Delayed intraday data provided by DDFPlus

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.