Jim Dean Elite   Posts: 1059 Joined: 10/11/2012 Location: L'ville, GA  User Profile | Hi Buffalo: I’m hoping that I quoted Ed correctly - I can’t recall if those comments were recorded or not. My guess is that they have “rough draft” plans which will be gradually refined. I do know that the ET interface took a couple of years longer than was originally anticipated (for several reasons) - so it’s possible that they are trying to avoid a potentially messy upgrade to the engine. Again, just guesses. As to your main point and questions - I think that “ATM-ing” OV will essentially be adding another layer to the top of it, rather than rearranging its current architecture in some big way. Since OV already has equity analysis thoroughly integrated (moreso than OT did), that might speed it up. The main thing (my guess) they need to do is add an “ATS” engine to gather information to “rank” things. Re current portfolios being usable - that’s likely a maybe / maybe not thing, depending on how those portfolios were constructed. I think that OV likely will do it’s “ranking” on portfolios rather than strategies (aka OV Systems), since the existing pro tools already exist To build portfolios from strategies. So - my guess is that *if* you’ve been working away at constructing portfolios that are intended for different Market States, then they won’t need much tweaking if any. The OV “ATS” capability will simply enhance how Signals within a given portfolio (the one for whatever the active Market State is) are prioritized. Also, since ATM includes segmentation of trade size allocations by market state, and since that would overlap with the OV “general settings” rules, I would expect that part of OV to be the main thing needing revamping - so that different settings can track with different portfolios, as Market states change. The most important missing ingredient in the OT implementation of ATM is that different lists cannot be used for different Market States, and that (from what I’ve been told) no one has as yet tested OT Dynamic Scan lists with OT ATM. I very much hope that missing piece will be integrated, first in OT so we can do appropriate devel work, and later in OV when the likely changes are made to provide different account setting to different Market States. That is - ability for user to specify different Focus Lists (Dynamic or Static) for each discretion Market State. To be clear - I strongly believe that Dynamic Scans offer a huge benefit which has only been partially realized thus far. Equally as important as ATS ranking. You may recall my Bash presentation 3-4 years ago about this - the analogy of fly-fishing vs a fish-farm. So, I have tried to strongly recommend that Dynamic Scans be made an integral part, in both OT and OV, of the Market-State segmentation. Lots of guesswork here. But maybe it will give folks some useful ideas. [Edited by Jim Dean on 2/4/2018 5:12 PM] | |
