|Enhancements coming soon
1. We will soon re-visit the pricing model that was developed a year ago but put “on ice”. We want to see if it can be developed
into a truly superior model. One goal is to get a better curve fit so that fair values in the Matrix come closer to actual market
prices. Another goal is to develop a model that accurately anticipates changes in the shapes of the skew curves in response to
possible market moves. Don’t worry, the pricing model in the software now will be kept and given a name, perhaps “the golden
oldie”, and users will be allowed to switch between this and the new model. At the same time, we want to improve upon the
current volty skew graphics and add the ability to show IV skews of different dates, current and past.
2. Miscellaneous other improvements per customer input.
|OptionVue version 8.20 started shipping April 21, 2017.
1. BackTrader may now be used on 15 minute intervals when accessing data from January 1st 2017 onward (Prior to January
1st 2017, data is only available on 30 minute intervals.)
2. We switched to a new file format for the local archive storage of BackTrader files, and as a result these files can be read 2.5
x faster. This and other steps were taken to make BackTrader work faster. However, the old archive files that you may have
collected can no longer be used. To build up an inventory again, we recommend that you make use of OptionVue’s facility for
collecting BackTrader data unattended. This can be found in the menu at Data | Collect BackTrader Data. Note: To avoid
confusion, the program automatically renames the “Archive” folder to “Archive2” and creates a new (empty) Archive folder, thus
“shuffling the old files to the side”. Feel free to delete the old files.
3. Related to the changes mentioned in #2 above, the asset file format needed to change significantly and old asset files are
no longer readable by OptionVue. This means that when you open a Matrix for the first time after installing this upgrade, the
program will automatically create a new asset file to go with this Matrix. You may need to go into Define | AutoStrike and adjust
the settings according to your liking, as well as any particular settings in the Models area. Be sure to define any expirations as
necessary to cover your existing positions.
4. For those using OptionVue with IB or TOS for real-time price updates, many have struggled for a long time with keystroke
and mouse click interference problems. That was due to the fact that real-time data, keystrokes, and mouse clicks were all
Windows messages, all arriving through the same channel. We finally have a good solution! A separate new program called
the OVHelper program is automatically launched and this program manages the interfaces with IB and TOS, relieving
OptionVue of that burden. OptionVue and OVHelper communicate with one another through a fast socket connection. When
OVHelper is not needed anymore (i.e. when OptionVue is closed or when entering BackTrader mode), it automatically goes
away. When needed again, it automatically comes back.
5. In Settings | Preferences | Graphic Analysis there is a new checkbox entitled “Calc and show maint reqmts across bottom”.
This determines whether OptionVue calculates and displays the estimated maintenance margin requirements along the bottom
of the chart at the intervals of the horizontal axis. It is off by default. The calculation of estimated margin requirements is CPU
intensive and many users would prefer not to have OptionVue be burdened with that, especially if they have little to no interest in
the numbers anyway.
6. In Settings | Preferences | Folders tab, we made the folder name fields a bit wider.
7. Currency options: Changes were made to both the server and client sides to accommodate the new symbology for currency
futures options. Note that obtaining prices for the June options is a bit of a problem. Those are the only options still using the
old base symbol of ‘6E’, for example. If you need to receive prices for June options, call us for a tip on how to make this work.
8. eSignal users who trade futures and futures options: eSignal has announced that all futures and options symbols will have a
2-digit year code (rather than a single digit) beginning with the Jan 2018 contracts. We have adapted OptionVue to that
change. However, note that we will not copy that symbology change in our system. In OptionVue, the symbols will still have
single-digit year codes. OptionVue makes the symbol adjustments on the fly at it interfaces with eSignal.
9. We incorporated third party software for capturing information on errors in the program such as “range check error”, “access
violation”, “integer overflow”, etc. Whenever one of these happens, a small window will pop up on the screen and ask if you
want to send a bug report. Please answer “yes” and type a few words telling us what you were doing within OptionVue at the
time the error happened. Thanks. This should help us track down problems very quickly.
10. VXX Trading System: We were able to back-fill a history of the $YVI from Feb 20, 2009 until June 9, 2016. (We had
already collected a history from June 10, 2016 to the present.) Note that the back-filled data is closing prices only.
1. When using TOS or IB for real-time price updates and a Matrix was open with the legends on, while typing input in one of the
cells of the Matrix, the characters typed so far could be lost if the user did not complete the entry quickly enough. While this
may seem like a keyboard interference problem, it actually had a different root cause, and we were able to solve it.
2. Regarding quotes reception from IB, we have had customers report that when they pay IB for an increased symbol count limit
– say to 200 – then they tell OptionVue to get more than 100 symbols per batch, OptionVue receives quotes for a short time
and then quotes completely stop coming in. We were able to confirm this. Investigating, we do not believe there is any
problem on our side. We put a request in to their engineering department for information about this, and they came back
saying that it is a known problem, even when using TWS. They did not indicate when it might be fixed.
3. In the Matrix, when multiple positions exist, encoded with two or more different Trade ID’s, the Gain/Loss displayed in the
summary section of the Matrix could be wrong when the Trade ID Selector was set to “(ALL)”. This was corrected.
4. In the Matrix, in rare cases, clicking the position finder buttons could cause an access violation. This was corrected.
|You're The Options Expert