ron22
255 posts
msg #153825
- Ignore ron22 |
8/30/2020 11:26:36 PM
@DMOBRIEN
Thank you for your reply. Your input helps a lot.
|
nibor100
1,031 posts
msg #153835
- Ignore nibor100 |
8/31/2020 11:35:53 AM
1. I don't know if anyone on the basic subscription is having issues with running DMOBRIEN's lengthy filter but just in case here is a short version that only has the filtering components and no chart indicators:
2. I have no real idea how one is supposed to trade the results of this filter as it seems the Alpha portion of the total Score sometimes dwarfs the contribution of the 2 true/false indicators. BuyOSC and XPMA22.
In other words, one could use just Alpha as the sort and get most of the same top stocks.
In fact, I'm not sure when we are supposed to run this filter; after the close each day or during the day, or both.
3. Also, there are some curious use of variables and calculations that need further exploring for me to see what is really going on. He has gone to great lengths to calculate his own chart indicators which explains much of why there are so many lines in his filter. I'm fairly certain I can streamline some of it.
For example, the 6 set statements to create the pivot point variable PIV can be replaced by the SF "PP" indicator.
Ed S.
|
DMOBRIEN
363 posts
msg #153847
- Ignore DMOBRIEN |
8/31/2020 11:01:28 PM
Following up again ..... and of course the commentary I see, and am engaged. The primary issue as I see it is the strength of the price movement relative to 12 and 24 week Camarilla modeling, if you will. The filter can be run by score column (default setting), buy osc, or simply z %. Cross reference then, whether the 5 day and 20 day (meant as an average) accumulation / distribution slope is in a positive direction vs. what you see in price. How committed are the buyers volume wise and at what price? The bottom box will tell you whether the price movement was selling or buying. Moreover, please keep the thread alive, as constructive input is welcomed, and, I am a raw coder with and a little light on elegance. That being said .... let's try another one
|
Cheese
1,374 posts
msg #153849
- Ignore Cheese |
9/1/2020 12:58:36 AM
@DMOBRIEN @compound_gains @nibor100
THANK YOU very much for taking the time to share your filters and your posts.
They are helpful and thought provoking.
Dave's second filter seems to go beyond T.A.
Very interesting.
|
Cheese
1,374 posts
msg #153861
- Ignore Cheese |
9/1/2020 12:45:11 PM
@DMOBRIEN
CRM was one of the picks from your filter #2
Were you actually able to go into that trade and if so, were you able to go in before the ramp up?
Thank you, Dave.
|
DMOBRIEN
363 posts
msg #153872
- Ignore DMOBRIEN |
9/2/2020 2:17:16 AM
It pulled JMIA and CONN, and now has GNPX and DLTH on watch.
|
DMOBRIEN
363 posts
msg #153873
- Ignore DMOBRIEN |
9/2/2020 2:35:07 AM
I think its generating some pretty good buy signals. On CRM a very good one imo on Aug 14 .... even on a red day it would have made you think, and really just cross reference with "APOS". if a signal is given. RPAY, for example now looks like it has buyers coming in b/c APOS bottomed out and reversed upward to perhaps newer highs. If it gets past 28 probably breaking out
|
Cheese
1,374 posts
msg #153877
- Ignore Cheese |
9/2/2020 9:51:35 AM
@DMOBRIEN
You also have some good filters in the past (money flow for example).
Are there any gems you've posted over the years that are still top of your mind?
Thanks.
|
nibor100
1,031 posts
msg #153887
- Ignore nibor100 |
9/2/2020 4:13:03 PM
@cheese,
I just ran his 2nd filter for each of the past 30 trading days and CRM never came up in the results.
How are you getting CRM to show using his 2nd filter?
having the first line:
rsi (7) > rsi (7) one day ago
Thanks,
Ed S.
|
nibor100
1,031 posts
msg #153888
- Ignore nibor100 |
9/2/2020 4:55:44 PM
@dmobrien,
FYI, in the first filter you posted in this thread you have used 3 set statements that may not be contributing to your filter as you originally expected.
1. set{VBW,BOLU - BOLD}
The variable 'VBW' is not used anywhere else in the filter, that I can find, but it may be important to you.
2. set{diff, myoscillator - var1}
The variable 'diff' is not used anywhere else in the filter, that I can find, but it may be important to you.
3. set{ACDST, sum(EQ3(22),22) / 22}
SF interprets this statement to be the same as set{ACDST, sum(EQ3,22) / 22}; so if your intent was to sum the EQ3 variable of 16 days prior for each of the past 16 days, before dividing by 16, SF can't do that with that set statement.
Hope this helps some,
Ed S.
|