StockFetcher Forums · View by Author: (120 messages)  [ Display By: Date / Subject ]<< 1 ... 3 4 5 6 7 ... 12 >> 
General Discussion · How to find the last time something happened
msg #152272
5/21/2020 5:49:50 PM


It might be better if you started a new post so more people can see your question, but it's confusing so let me ask you what you're looking for. What I mean is that you can write something like "show stocks where ma(30) has been increasing for the last 2 days" (or however many days you want) and you'll see them. Or to see ones going down just say "decreasing" instead of "increasing."

You can't do both in the same filter, as far as I know, because they'll cancel each other out. So I'm not sure what you're asking for, but like I said, more people will see it if you put it in a new post.

Filter Exchange · Deadly Combo updated
msg #152265
5/21/2020 12:10:51 PM

Someone recently mentioned the Deadly Combo filter by 13th_floor so I searched for it and found it here:
The basic idea is that "These stocks are at least 8% ADR(30) AND have run at least 10 times in the last 100 days over 10% in a day." (Quote from that post.) It's based off of TRO's Run Forest, Run filter with just enough code added to find the ADR(30). I like the RFR filter but if all you're looking for are those two things it has a lot of extra code so I streamlined it.

A quick note: Most of the original and variations I've seen of filters like RFR, or the Crock Pot, look for the difference between the high and the open. I've changed that to the difference between the close and the open. Unless a stock closes at the high it can and will drop from there. Looking at the high - open difference won't help if the stock closes slight above, or even below, the open.

About the columns:
1. I use the ADR(5) to help me determine stop limits. Feel free to ignore it or remove it if you want (just adjust the sorting column if you remove it).

2. +10% and -10% are the number of days out of the last 100 days the stock closed either at least 10% over or under the open. I often see potential loss left out of filters like this but it's important information. Just because a stock may have closed at least 10% higher 20 days out of the last 100, for example, doesn't mean anything if you don't know that it closed at least 10% lower on 40 days out of the last 100. You want to risk your money on half a picture? Go for it. I don't.

3. Days is how many days since it closed at least 10% up or down. (Thanks again, Ed!) It doesn't affect the filter but I like to know if this is something that's happening recently as opposed to something that happened months ago.

4. Score is simply the up days divided by the down days. You could sort on it if you wanted to but I use it as a quick way of comparing the results. ADR30 is simply the Average Day Range for 30 days.

5. Ouch is the number of days a stock had a low that was at least 10% below the open, regardless of where it closed. I do percentage stop limits so it's useful info for me. The days column next to it is the same as the other ones.

So is it a good filter? Maybe. Sometimes. Click on it and look for SAVA if it's still there. It looked okay on 5/14 but I'd hate to be the person who bought in that day only to wake up on 5/15 to see that it had dropped over $6 a share. Never rely on just a filter result to pick stocks or ETFs. At the very least find out what the company is and what they do. There are plenty of web sites where you can get more information to make an informed decision.

Fetcher[/* 13th Floor
"These stocks are at least 8% ADR(30) AND have run at least 10 times in the last 100 days over 10% in a day." Based on TRO's Run Forest, Run filter */

market is not OTCBB
market is not ETF

set {dayup, close - open}
set {gain, dayup / open}
set {win, count(gain > .10, 100)}

set {daydn, open - close}
set {loss, daydn / open}
set {lose, count(loss > .10, 100)}
set {score, win / lose}

set {toolow, open - low}
set {damn, toolow / open}
set {ouch, count(damn > .10, 100)}

Show stocks where close is between 2 and 100
Average Volume(90) is > 250000
Average Volume(30) is > 500000
Average Day Range(30) is > 8
win is > 9

do not draw Average Day Range(30)
do not draw win
draw ma(21)
draw ma(50)
draw Center Linear Regression Line(28,1.0)

add column Average Day Range(5) {adr5}
add column separator
add column win {+10%}
add column days(gain > .10, 100) {days}
add column score
add column Average Day Range(30) {adr30}
add column separator
add column lose {-10%}
add column days(loss > .10, 100) {days}
add column ouch
add column days(damn > .10, 100) {days}
add column separator
add column industry
add column sector
sort column 7 descending

General Discussion · How to find the last time something happened
msg #152264
5/21/2020 11:11:17 AM

They haven't updated it since it was first released? Sheesh! That's just crazy!

General Discussion · How to find the last time something happened
msg #152262
5/21/2020 10:09:38 AM

That's perfect! Thanks, Ed!

I actually searched the manual for "days(" since I knew I'd seen something like that but I couldn't find it.

General Discussion · How to find the last time something happened
msg #152258
5/20/2020 10:57:27 PM

I looked through the manual and tried searching the forums but I have no idea how to search for what I want to know. Hence, this post.

The question: Is it possible to find out how many days since something happened, like a stock closing 10% or more above its open?

Let's say I have a line of code that counts how many times a stock price rose up to close at least 10% above its open in the last 100 days. If you've seen any of the Crock Pot variations you'll know what I mean but for those who aren't familiar with that legend let me give you this (I know that most of the ones I've seen use "high - open" but I want to know where it closed rather than how high it went since I can't be watching for the high all the time):

set {dayup, close - open}
set {gain, dayup / open}
set {win, count(gain > .10, 100)}
add column win

Simple enough, right? In my own Crock Pot version I broke it down into five 20 day periods in order to see if it was happening more recently. To me, a stock that's closing 10% higher in the last month is more interesting than one that hasn't done it in six months or more. But even that didn't tell me exactly when it happened.

So I'm on a quest to see if there's some SF code that can tell me "it's been this many days since the last time this event happened." I hope there is.

ETA: I know I can use the "days ago" phrase to see if something happened x number of days in the past, but that would mean creating a lot of set statements, depending on how much I wanted to narrow down the time. I'm hoping there's an easier way to do it.

General Discussion · Weekly close
msg #152257
5/20/2020 10:09:33 PM

Compare it to what?

You can make a weekly version of a moving average but couldn't create a monthly one the same way. Maybe a custom moving average would work.

Fetcher[close is > 2

draw ma(50)
draw weekly ma(50)

ETA: I don't know why I read monthly instead of hourly, but for hourly the answer is definitely no. SF doesn't use intraday prices for their charts.

Filter Exchange · This might be impossible
msg #152244
5/19/2020 10:06:07 PM


Right. I'd forgotten about that post. Thanks!

Filter Exchange · This might be impossible
msg #152239
5/19/2020 12:22:43 AM

I'm looking forward to seeing that filter. I'm playing around with xarlor's filter to see how to predict a low volume to breakout pattern but I haven't come up with anything yet.

I'm curious. Why those MA's? Did you try different ones and found those worked best?

Filter Exchange · Price Coming Off of a PVI Low
msg #152157
5/11/2020 4:42:07 PM

Thanks, nibor! That would explain why it ran sometimes but not others. I should have seen that.

Filter Exchange · Price Coming Off of a PVI Low
msg #152149
5/11/2020 1:18:22 AM

Making kossvet's xarlor filter clickable. It's telling me there's a problem with variable 8 but I'm not sure what the problem is or how to fix it.

average volume(5) > 100000

set{diff1,ma(5) - ma(10)}
set{diff2,ma(10) - ma(20)}

set{vol2,average volume(5) 5 days ago * 2}

set{var1,count(volume > vol2,1)}
set{var2,count(ma(5) increasing for last 3 days,1)}
set{var3,count(ma(10) increasing for last 3 days,1)}
set{var4,count(ma(20) increasing for last 3 days,1)}

set{var5,count(diff1 increasing for the last 2 days,1)}
set{var6,count(diff2 increasing for the last 2 days,1)}

set{var7,count(atr(30) 3 days ago < .2,1)}
set{var8,count(reached a new high 3-month high,1)}

set{buy1,var1 * var2}
set{buy2, buy1 * var3}
set{buy3, buy2 * var4}
set{buy4, buy3 * var5}
set{buy5, buy4 * var6}
set{buy6, buy5 * var7}
set{buy, buy6 * var8}
buy > 0
buy 1 day ago equals 0

/* Comment out the 2 lines above and uncomment the 2 lines below to see all hits within the last year */
/* chart-time is 14 months */
/* count(buy > 0,251) > 0 */

draw ma(5)
draw ma(10)
draw ma(20)

StockFetcher Forums ·  · << 1 ... 3 4 5 6 7 ... 12 >>

*** Disclaimer *** 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. does not recommend particular securities., 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 2018 - 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.