Alert/Filter/Alert Feature Request #2
This probably would be a massively difficult one to try to implement but let me outline my thoughts just the same.
In the faqs you (TI) elucite(s) the following:
"..in general it is not meaningful to combine two or more alert types with an and. Alert types, unlike filters, are events which _occur instantaneously_. "
Well, I agree, to a point. But wouldn't it be immensely useful if we acknowledge that what the user is trying to do is detect a unique event that follows another special event for a given stock? What I want is analgeous to a progressive sort algorithm . I don't want alert#1 and #2 simultaneously, but, _sequentially_. Like, trying to sort name and date simultaneously is generally not useful, but sorting name _and then_ date is.
In a typical scenerio for one scheme I sometimes try, I look for stocks that surge at the open then fall off before resuming a climb. For example, today, this morning at 9:30 I detected a new 1 day high for CRZO, CVNS, AHM, ESIO . From the charts one can see that those are not ideal entry points (to say the least). What I want from that point is a trailing stop to try to get near the bottom of the potential mid-morning dip.
But the trailing stop alerts are triggering like crazy for stocks I'm no longer interested in at the moment. I have to try to remember which ones just hit the opening high.
Now, the "running up", "x-min high", and "trailing stop" alerts are theoretically useful for catching this, but, here agin, if I set counts too low to restrict the deluge, I might miss the one I want.
I improved my situation by "taking my eyes off the road", to hastily type in a symbol list with just those, then select that list on the filter page, reset some new alert types, up the count filter, check history in case I missed something...
I would like to be able to automatically cascade alerts and filters to produce a progressively smaller list of stocks that "fall out" over time. Ie.
1. Filter initial criteria
2. First tier alerts provide filter list output out to second tier alerts.
3. Second tier alerts operate only on list updated from #2.
Theoretically, the refining process could continue with more tiers, but just a second alert/filter tier would be quite a useful improvement and automate what I am attempting to do by hand ( & mentally).
2a. Being able to set individual count limit criteria for each alert type might help toward this end as well. Not quite the same thing but perhaps easier to add initially. (hmm why not both)
