Release Notes

MOOSES™ was developed by the Vanderbilt Kennedy Center.  Jon Tapp, the author of MOOSES™, currently works at Vanderbilt University's Kennedy Center as the the Director of Computer Services, webmaster, and lead software developer.

You may download a complimentary copy of the current MOOSES™ User Guide and Documentation in PDF format via the link below, which contains detailed instructions and many helpful tips on how to get the most out of MOOSES™.

We will post helpful answers to customer inquiries in this section on an ongoing basis in order to provide all of our customers with an effective and a productive experience while using the MOOSES™ tool.

If you do not find the answers you need, please feel free to visit our Contact page and tell us about your issue.


moosesmanual.pdf253.21 KB

MOOSES™ New Features by Version

Following is a chronological log of MOOSES™ feature enhancements, modifications, and fixes of interest to all MOOSES™ users.

To request a feature or report a bug, please email Jon Tapp at Vanderbilt University Kennedy Center. 


Version 3.4.11

Added the setting to make the IOA primary dependent if so desired. A few other minor bug fixes.

Version 3.4.4

Fixed a bug causing it to bail on SALT format lists

Version 3.4.3

Fixed a couple of bugs related to the SALT format, one cause the last time of a procoder translated salt file to be uncounted, the other caused the SALT code translation file to be read incorrectly if it had first line actor codes in it.

Version 3.4.2

Fixed bugs related to ODF files. First code is a give group in a code file is not used as the initial code in an ODF file (see settings).

Added settings to allow for merging in of continuous data (like heart rate or noise level) and recoding that into a code in MOOSES data stream (see options).

Version 3.3.9

Fixed bugs related to reading the comment field incorrectly in procoderdv files.

Version 3.3.8

Changed frequency and duration spreadsheet output so that it does not output duration zeros for level 0 (frequency only) codes. Also fixed a bug that caused a bomb under certain conditions when the code file editor was closed.

Version 3.3.7

Many bug fixes since the last web post, mainly related to ProcoderDV files and SALT file changes.

Bug fixed in the individual Kappas where one of the cells was zero in the 2 by 2 matrix, effected individual code level kappas.

Bug fixed in the counting for event lags bigger than one that caused it to count wrong at lag 2 or greater lags (event based only).

The Windows collector can now run as a separate program. This eliminates the need for more licenses just to collect on a laptop.

Version 3.1.0

ProcoderDV options have been vastly improved. You can now ignore and combine columns and pick your start and end times.

Version 3.0.2

The list manager now supports data paths from windows and "drag and drop list making" from windows folders (A great time/hassle saver).

ProcoderDV files are now directly readable by MOOSES without exporting from ProcoderDV in most cases.

IOA to spreadsheet output and other output formats have undergone needed improvements.

Data paths have been dropped, toggles and interval files have been dropped. These features are no longer needed by the current collection programs. They were also confusing to most windows users not familiar with DOS concepts.

Errors are now printed to the output file instead of the screen so the processing of lists is not stopped by errors.

The code file structure has been changed to be the same as the ProcoderDV code file. (older code files will need to be re-made)

Process of obtaining new versions for current licensees

If you are an existing licensee, you may download the new version from the “Premium Content” section ( of VUe-Innovations website after logging in with the user name and password for the website. If you have forgotten your user id and password, you may reset it here:

I am interested to install new version of INCA. Will this new version be compatible with the old MATLAB R2014b? Would it be possible to open my old models on the new version?

Yes, INCA 1.6 should still be compatible with older versions of Matlab going back to 2012, and you should be able to open model files created with previous versions of INCA