Add ability to use BSR, MTI, etc in unisearch
Every week we have a strategy of the week that often uses the Buy/sell ratio (BSR), color guard values, or MTI in order to determine when to buy or sell stocks in general. Why not allow the unisearch tool to access that data, to make it's own decisions as to WHEN to be in or out of the market, and when to go long and short on individual stocks the search finds? For example, I'd love to be able to reference the current BSR, and turn on a "bottom fishing " search when it hits a low value like .30, or experiment with buying or selling on various colorguard settings.. Seems silly that these relatively simple market data values are created by VV, yet we can't use them in our searches! They might be really useful in improving search results in our backtests!
Michael Roscoe commented
This would be a very useful way to help people gauge position sizes - especially when back-testing a strategy.
Putting on smaller positions during more overbaught , and larger positions during underbought conditions would also help teach discipline for risk management
It would be simple enough to add a condition to "use market timing" relating to a MTI value and not a kicker/dew/etc....
Emad Nakhnoukh commented
As a Data Warehousing Specialist, I don't see that this improvement should take that much time. You already have a table containing VVC data(Price, BSR, RT, MTI). and that is already displayed in the home page in the color guard window. We only need to have these fields available within Vector Vest Fields. Only one table and probably one link to the rest of the data model tables. I'm really surprised that there are only 90 votes for this improvement. It will be helpful also if we can add an oversold/overbought oscillator like RSI or stochastic to make the uni search and back testing more efficient. I really doubt that robotic trader will be useful without this improvement. Similarly , the derby automation. If we are planning to automate this process, we would need to have such a powerful tool to automate the whole process. We eventually have to trade a basket of stocks to minimize the risk. I spoke to Steve Chapel about in on February 5th during the two days seminar in Commerce city, Los Angeles , California.
Pieter Albertyn commented
As a new user this has been my first drawback to Vector Vest
Harbans Lal commented
good suggestion. i vote for ir
Howard Beckett commented
Please see my IR to "Add Market Data to Unisearch" I say that when you click an open box under "Parameter" in the Unisearch tool, a list would appear like it does now, except that the list would say "Stocks' Industry Groups, Sectors, and MARKET". When you pick "Market" you get access to the "color Guard" data and to the VVC averages for the day or time in question. this would allow you to set up searches that only work when the MTI is above 0.9 or when the BSR is below .3 but trending up for 3 days. It would also allow you to choose stocks with "Lower-than-average" P/E ratios by finding the P/E (or whatever) of the VVC and comparing your findings to that number - AUTOMATICALLY!
William Devonshire commented
This is part of the credo of Vectorvest, so I am not certain why MTI and BSR isn't useable inside the Unisearch. Being able to filter some of my searches with the value or trend of the MTI and BSR would allow me to make sure I am buying when I should be buying.
Greg Veres commented
Yes please do. I want to only buy stocks on the days that the MTI is increasing from the previous day. This allows you to avoid the end of the confirmed up period when the VVC is dropping and indicated by the MTI.
Bill Rohlfs commented
See 'Have the functionality to select stocks based on the value of the MTI (also RT,BSR and VVC' Same thing
Arthur Crapsey commented
This functionality would also offer interesting possiblities when creating stops in Prographics from the Simulator.
Matthew McLaughlin commented
Agree, add BSR, MTI, and VVC to custom field builder.
Kevin Williams commented
I totally agree. I could really use BSR and MTI in the Custom Field Builder.