| ♥ 0 |
I called TOS and I can’t believe TOS doesn’t have a time column in the scans. This voids most any scan or makes it very hard to use. Example, I have a scan called price spike with 50 results, obviously I don’t want to see the stock that spiked and hour ago, I want to see the stock that just spiked and just showed up on the list, preferably at top. Otherwise I have to look through all 50 results and guess at what just spiked, also I may not even be seeing the latest results at all if there are more than 50 results and are not sorted by time. The 1st problem is when you build a scan in TOS you must sort by something, it should just alow the results to flow from most recent. The next problem is they have no time column like most if not all other scanners, like Trade Ideas. I made a custom column with get time but it does not work, all results show the same time, IDK why. I tried using the no sort option in the watch list menu but that just allows the scan to sort by the method that was selected on the scan build screen. any ideas?
Marked as spam
|
Posted by 
Only option I think of at the moment is to create a counter. That counts how many bars have elapsed since whatever signal you are using has triggered. It sounds like your scan is set to pickup a condition and not the precise bar in which that condition first appeared. So when you run the scan you are getting a list of stocks for which the condition has occurred at any time in the previous, who knows how many bars.
A counter would basically take your existing condition, identify when that condition first appears, then set the counter to 1. For every subsequent bar you increment the counter by 1 until the condition is no longer true. Here is an extremely basic example of how to write a counter variable:
rec counter = if firstOccurance then 1 else counter[1] + 1;
There are examples of this posted in the Q&A forum: https://www.hahn-tech.com/ans/count-ttm-histogram-trend-length/
There are others but this is the first one I found. If you need further assistance, we are going to have to see your code.