riggs
313 posts
msg #33073
- Ignore riggs |
8/31/2004 6:42:56 PM
I back tested this for a week now & the results are quite remarkable.
Show stocks where volume gained more than 50 percent over the last 1 day and average volume(90)is above 100,000 and MA(3)crossed above MA(8) 1 day ago and ADX(14)is above 20 and Linear Regression(10)slope crossed above 0 within the last day and close is between 30 and 100.
Now, with me being a newbi to this site, input & critics are welcome to add to this. **Riggs**
|
robdavis
69 posts
msg #33077
- Ignore robdavis |
8/31/2004 9:46:55 PM
Riggs,
I, too, have back tested your filter for every single trading day of a recent bear market (between 6/30/04 and 7/14/04), and, based on this back testing, I couldn't find anything wrong with your filter. IT LOOKS GOOD so far!!! It looks like you chose and carefully considered all values you selected for your filter.
If I may suggest something, there is something you could do; you could use of SF's fetcher[] function, so that guys in this forum could click on your filter and back test it more extensively, without too much effort. Let me make this improvement for you...
I hope this helps.
Rob
|
riggs
313 posts
msg #33078
- Ignore riggs |
8/31/2004 11:42:46 PM
Rob, thanx for the input but, can you explain to me how one HIGHLITES these filters. I,m a bit slow to this forums functions. Thank you. **Riggs**
|
robdavis
69 posts
msg #33079
- Ignore robdavis |
9/1/2004 12:45:40 AM
Riggs,
If you have a filter, it will get highlighted automatically, if you do all the following six things:
1) Put the word "fetcher" before your filter,
2) Put a left bracket "[" after "fetcher"
3) Remove any space from between "fetcher" and the "["
4) Put a right bracket "]" after the end of your filter
5) You can make syyntaxx errrorrs, or add /*COMMENTS*/, or /*comments*/, but you cannot make your filter too long.
6) Experiment. Do "preview message" before you hit "post message". If your filter gets highlighted in "preview", it will get highlighted after you hit "post message". And the opposite of this is also true. If your filter does not get highlighted in "preview", it will not get highlighted after you hit "post message".
Here are some examples:
A) No spaces are the safest bets:
B) Space between "[" and one's filter is okay:
C) Can you see the error I've made?
Fetcher [Your filter]
D) Space between one's filter and "]" is okay:
E) Errors in grammar or syntax is also okay:
I hope this helps.
Rob
|
riggs
313 posts
msg #33081
- Ignore riggs |
9/1/2004 1:45:26 AM
Rob,
You are AWESOME my freind! Thanks for taking the time out of your busy life for me. That was great! I only hope I can return the favor in the future. **Riggs**
|
cegis
235 posts
msg #33085
- Ignore cegis |
9/1/2004 9:46:53 AM
Rob,
Is there really a limit to the length of the filter before it no longer becomes a hot-link? I know you had an issue with IE and some limit that it has with URL length (IIRC), but that's not a SF or fetcher[] limit. I have no such problem with Mozilla. IE users could always cut/paste into the new filter text box...
Just wonderin'...
C
|
riggs
313 posts
msg #33093
- Ignore riggs |
9/2/2004 3:16:24 AM
Just for a quick side-note, take a look at ALL your indicators when using this filter. This I did not expect but gladly except. **Riggs**
|
robdavis
69 posts
msg #33103
- Ignore robdavis |
9/2/2004 1:10:36 PM
C,
> Is there really a limit to the length of the filter before it no longer becomes a hot-link? I know you had an issue with IE and some limit that it has with URL length (IIRC),
Remember, in the "Help requested for shorting filter" thread in "Filter Exchange" how successfully we worked together? Well, that was thread where I especially enjoyed writing long filters. And, as you might remember, our filters got longer and longer as you and I made the filter increasingly better and more user friendly. That was the time when I noticed how sometimes long filters created additional user issues.
No, it's not exactly that there is a limit to the length of the filter before it's no longer a hot-link. But what happens is, after a certain number of characters (or lines of code) the filter still remains a hot link, but (to newly and automatically opened browsers) the hot link copies the filter, but only partially. Only imperfectly. And this, from a user's point of view, can affect the useability of filters. I believe this is an issue, because many users fail to notice the incomplete copying, and immediately (and erroneously) assume there is something wrong with the filter itself.
> I know you had an issue with IE and some limit that it has with URL length (IIRC), but that's not a SF or fetcher[] limit.
Yes, this is true, and this is exactly what Tom B. (of SF) told me, and I believe what you're saying is true. In a way this is partially my (and many other users') fault(s) because I (and millions of others) still use IE, a still very popular browser as of 2004.
> I have no such problem with Mozilla.
Mozilla sounds like a browser that is good to have, and all of us should consider using it.
> IE users could always cut/paste into the new filter text box...
That is true.
I hope this helps.
Rob
|
tomb
267 posts
msg #33105
- Ignore tomb |
9/2/2004 1:26:49 PM
Rob,
There is now a work-around for the IE limitation with respect to the posting of filters in the forums. If you have noticed the magnifying glass that has been around for a couple weeks, clicking on that will reproduce the original filter -- theoretically, regardless of browser make/model or filter size.)
Clicking on the link, within a long filter, is still bound by the same IE limitation.
Thank you,
Tom
StockFetcher.com Support
|
robdavis
69 posts
msg #33106
- Ignore robdavis |
9/2/2004 1:27:08 PM
P.S: If this is what you meant, I see now what you wanted to say. Yes, I agree, technically the wording was not 110 per cent precise when I wrote, "5) You can make syyntaxx errrorrs, or add /*COMMENTS*/, or /*comments*/, but you cannot make your filter too long." A somewhat more precise way would've been to say,
"5) You can make syyntaxx errrorrs, or add /*COMMENTS*/, or /*comments*/, or write long filters, but try not to make your filter too long, because with long filters there are known browser issues."
Rob
|