Howdy, Stranger!
Categories
- All Categories
- 2.3K StockCharts
- 395 SharpCharts
- 145 Other Charting Tools
- 69 Saved Charts and ChartLists
- 1.5K Scanning
- 72 Data Issues
- 176 Other StockCharts Questions
- 217 Technical Analysis
- 154 Using Technical Analysis
- 2 InterMarket and International
- 19 Market and Breadth Indicators
- 42 Market Analysis
- 107 Trading
- 107 Trading Strategies
- 163 S.C.A.N the StockCharts Answer Network forum
- 65 Using this StockCharts Answer Network forum
- 98 s.c.a.n. archives
- 5 Off-Topic
- 6 The Cogitation & Rumination Emporium
- Forum Test Area
New Members: Be sure to confirm your email address by clicking on the link that was sent to your email inbox. You will not be able to post messages until you click that link.
Alert Capacity
I have asked a similar question in the past and you advised that I delete every scan and alert and rebuild them all. I have not done that because it's a massive effort. Not sure that I have the vocabulary to describe this mess but here goes again. A while back I noticed that some of my alerts and even some of my scans would not save the full 8000 characters any longer and we assumed that it was somehow because of all the cutting and pasting that I have done that somehow limited the number of characters that the machine would save in a scan or alert. Just this morning, I noticed that I was having the same problem with another large scan that I was attempting to modify. However, when I changed the name of the alert, it saved just fine, just like it used to do before I started having the problem. If it helps, there is some kind of autofill that likes to use previous alert names that have been used before. If I change the name of the scan to something that I have never used before, it seems to accept and save it. Does that help you to understand what the problem with saving large scans might be and what to do about it?
0
Comments
It may not be an "autofill". Instead it may be a length limit on naming, so that if the first x characters of the scan name, up to the character limit for scan names (whatever that is, I don't know), are the same, it does something different from what you expect.
It also occurs to me that the scan name may be included in the character limit for the whole scan, which you may not be accounting for.
Both those thoughts may be wrong.
Unfortunately, when you do things unconventionally and push the limits at the same time, you get into situations where solutions are hard to find, possibly because the system designers did not anticipate the system would be used in that way. On the other hand, it's possible you think you are doing one thing, but really you are doing something else without realizing it. There's no way to tell which, I don't think.
Also, apparently the purpose of such massive scans is to save time and effort, but it seems they are costing you a lot of time and effort, too, which is counter productive. I have found its pretty challenging to verify the results of scans with just a few conditions. I wouldn't know where to begin when the scans get so large. But, that is for you to decide. Just as I don't know the particulars of Stockcharts behind the scenes, I don't know your methods either. If you think it is working for you, that's great.
It occurs to me you could run scans for the longer term MACD conditions only at the end of the week or month, since that is the only "valid" value for those lengths.
(I'm assuming those do cross over during the week or month and those events do trigger an alert and maybe you want to trade those events, even if they are not "valid". So maybe you won't go for these suggestions.)
After you run the long term scans, over the weekend, or after month end market close, put the results into lists (i.e., replace the contents of the appropriate list) where they will stay until next week/month, regardless of what happens in between; or you can move them between lists if something dramatic happens so you "know" they are not coming back) - so maybe you would have a list for monthly above, monthly below, weekly above, weekly below, or some such combination. Probably sometimes there would be empty lists, other times, everything might be in one list for each time frame.
Then run your daily time frame alerts against the appropriate list(s). Over the weekend, or month end, you could choose which alerts to activate depending on which lists are populated.
That might make the alerts run faster and more accurately because they are triggering for just one time frame.
I would like for the scan engine to consider the top line and then the second line separately. The way I have it composed it does not work the way that I'd like for it to work.
[[Favorites list is 23] or [Favorites list is 40]]
and [[MACD Hist(60,130,0) > 1 Day ago MACD Hist(60,130,0)] or [MACD Hist(60,130,0) < 0.0]
or [MACD Hist(72,156,54) > 1 Day ago MACD Hist(72,156,54)] or [MACD Hist(72,156,54) < 0.0]]
and [[[MACD Hist(60,130,0) > 1 Day ago MACD Hist(60,130,0)] or [MACD Hist(60,130,0) < 0.0]]
or [[MACD Hist(72,156,54) > 1 Day ago MACD Hist(72,156,54)] or [MACD Hist(72,156,54) < 0.0]]]
which line are you calling the top line? The favorites list, or the MACD 60 ?
Are you happy if only one condition of the four is true?
Or, do you want at least one of each pair to be true ?
Also, do you care if both conditions of the first pair are true?
And do you care if both conditions of the second pair are true?
For the first part, the way you have it,
if MACD 60 is above 1 day ago MACD 60, it can be above or below zero and be a hit;
if MACD 60 is below zero, MACD 60 can be above or below 1 day ago.
So you should get all instance of MACD 60 above 1 day ago, regardless of where it is vs. 0, and all instance of MACD 60 below zero, regardless of whether MACD 60 ticked up or down.
In other words, you should get all MACDs below zero, but above zero, only hits with MACD ticking up.
Is that what you want?
Then the question is, do you want the same set conditions to be true for MACD 72 at the same time, or it doesn't matter for MACD 72 what MACD 60 is doing.
Now, do you want a symbol to be a hit when both the MACD 60 AND the MACD 72 are true, or just one?
and [ // begin top level 'or'; where 'a' is true, or 'b' is true, or both are true gets a hit
[ // 'a'
[MACD Hist(60,130,0) > 1 Day ago MACD Hist(60,130,0)] or [MACD Hist(60,130,0) < 0.0]
] // end 'a'
or
[ // begin 'b'
[MACD Hist(72,156,54) > 1 Day ago MACD Hist(72,156,54)] or [MACD Hist(72,156,54) < 0.0]
] // end 'b'
] end top level 'or'
You should get a hit for symbols where AT LEAST ONE condition is true. But for any hit, MORE than one condition CAN be true.
Symbols where NONE of the conditions are true should not show up as a hit.
If you want to try again, maybe when it happens, post a chart that shows what you want to get but the scan doesn't pick up.
and [
[ [MACD Hist(60,130,0) > 1 Day ago MACD Hist(60,130,0)] or MACD Hist(72,156,54) > 1 Day ago MACD Hist(72,156,54)] ] // one or both tick up
or
[ [MACD Hist(72,156,54) < 0.0] and [MACD Hist(60,130,0) < 0.0] ] // both below zero
]
or [[MACD Hist(72,156,54) > 1 Day ago MACD Hist(72,156,54)] or [[MACD Hist(72,156,54) < 0.0] and [MACD Hist(60,130,0) < 0.0]]]]
Good luck.