Matlab R2006a Free Down Load
Mazie Wingeier
This page shows supported versions of VeriStand with LabVIEW, Windows, target-specific compilation tools, and The MathWorks, Inc. development systems. Reference this information to ensure you install the correct toolkit version when upgrading or updating your system or software. Using incompatible versions may result in errors, or missing palettes or functions.
As of VeriStand 2021, there is a new toolbox to support compiling MathWorks Simulink models. Please refer to the download page for the VeriStand Model Generation Support toolbox to understand compatibility. The toolbox includes documentation covering getting started and known limitations. The 23.8 release of the toolbox does not support the use of buses as parameters.
1 The entries for The MathWorks, Inc. software versions include The MathWorks, Inc. MATLAB software, The MathWorks Inc. Simulink software, and The MathWorks Inc. Real-Time Workshop software.
2 Starting with VeriStand 2019, VeriStand supports PXI Linux RT.
3 For VeriStand 2018 SP1, VeriStand 2018 SP1 Model Framework f1 patch is necessary to compile models in Simulink R2017b.
NOTE: NI is not currently planning on supporting conversion of desktop PCs to NI Linux Real-Time targets. Conversion of desktop PCs to Phar Lap ETS targets is supported. However, NI will remove support for Phar Lap for cRIO in the NI 2020 Software Release and for PXI in the NI 2022 Software Release. For more information, please see the Phar Lap RT OS EOL Road Map.
Like-numbered versions of VeriStand and the Model Interface Toolkit share the same compatibility information. Please refer to LabVIEW Model Interface Toolkit for more information.
Installation order of individual components indicated on this page does matter. See Compiling The Mathworks, Inc. Software Models for PharLap Targets in VeriStand or Model Interface Toolkit for more information.
MATLAB, Real-Time Workshop, and Simulink are registered trademarks of The MathWorks, Inc. Other product and company names mentioned herein are trademarks, registered trademarks, or trade names of their respective companies.
The system used for testing in the first two published methods papers consisted of a computer with a 2GHz Core 2 Duo processor, 512 Mb RAM, a dual-headed video card with 128Mb video RAM, and two National Instruments 6229 PCI DAQ cards with twoBNC 2090 break-out boxes. Considerably improved temporal performance canbe achieved with more modern PCs. For example, our most recent methods paper (J Neurophys, 2013) used a system consisting of a Dell Optiplex 980 computer with a Core i5 processor clocked at 3.60 GHz, with 4GB or RAM and running on Windows 7. The video system in that machine consisted of two Radeon HD 3400 graphics cards with 2GB of video RAM. Unsurpisingly, even faster performance (with typical cycle intervals around 0.3 ms and video refreshes requiring only 1.5 ms) has been observed on a Core i7 system (unpublished).
A typical experimental set-up includes two or three monitors: thedual video card output is divided among two displays, one which showsthe experimental "control screen" and the other for use as thesubject's screen. The subject's display output is often sent to twomonitors using a VGA or DVI signal splitter so that the experimentercan see what the subject sees and simultaneously provide the subjectwith a separate, optimally-positioned display.
The Matlab DataAcquisition Toolbox supports a variety of DAQ devices by severalmanufacturers. In addition to those from NationalInstruments, devices from Measurement Computingare also known to work with MonkeyLogic. A list ofmanufacturers supported by the Data Acquisition Toolbox is availabeon the Mathworks site. Note, however, that boards must allow samplingin the free-running state (i.e., the device has not been "started" fordata logging, yet samples can still be retrieved with "getsample"), inorder to work with MonkeyLogic when two boards are used in parallel(see next section) for more rapid behavioral signal sampling. Devicesfrom Agilent do not havethis capability, and so are not recommended.
While some behavioral tasks may rely upon simple keyboard input,most users employ an eye-tracker, joystick, or button-box. In the Asaad Lab, we use the Penny Giles JC200 joystick for human and nonhuman primates. Eye-tracking is currently performed with SR Research systems in both the Freedman and Asaad labs, and we have also used Iscan systems in the past; any eye-tracker that can output separate X and Y (and optionally pupil) measurements via analog signal should work.
MonkeyLogic has built-in routines for eye- and joystick-calibration and tracking, as well as for reading analog or digital buttons or levers (see the eyejoytrack command for more detailed information on monitoring these inputs). Eye-trackers and joysticks are expected to provide separate X and Y voltages, and these can be calibrated from within MonkeyLogic to correct for differences in offset, scaling, and 2-D skew (see Input Calibration for details).
Create a directory called "monkeylogic" and add it to the MATLABpath, copying the unzipped contents of the downloaded package into it. Also add the directory containing the SVI toolbox functions to the MATLAB path. Next, create directories for each experiment; in each directory, you will place an experiment's conditions file, timing script , stimulus images, andany other needed files (e.g., block-selection routines, etc). Behavioral data files for a thatparticular experiment will be written into this directory as well.These experiment directories do not need to be added to theMATLAB path.
Launch the MonkeyLogic menu by typing "monkeylogic" at the MATLABcommand prompt. Once a conditions fileand timing script(s) have beencreated, clicking on the "Load Conditions File" button at the top ofthe menu will allow you to select that conditions file to import, alongwith any stimuli used by that file and the timing scripts associatedwith it. In addition, once the various parameters on the main menu have been configured, these settingscan be saved by clicking on the "Save Settings" button (note: thesesettings will also be saved whenever an experiment is launched usingthe "Run" button).
A joystick and eye-tracking system are optional (keyboard input isminimally required for an interactive task). Pre-calibrating the inputs(e.g., on the eye-tracker system itself rather than in Matlab throughthe main menu) allows faster task execution, though even whenperforming an on-line calibrated transformation the operating frequencyshould be greater than 1 kHz.
A separate data acquisition system is assumed to be in use to storeneural events (for example single units and LFPs) and other continuousinputs (such as eye position, joystick position, photodiode state,etc). Note: slow analog data (e.g., eye-position) will bestored locally in the BHV file aswell, but splitting these signals into the neural data acquisitionsystem is prudent because it provides exact, sub-millisecond alignmentof these signals in relation to the neural events. Behavioral codes (event-markers)will be stored locally allowing complete analysis of behavior, and canbe exported in real-time to the acquisition system to allow temporalalignment of the behavioral events with those data acquired separately.
If you are running an experiment in which eventmarkers are not frequently sent to a neural data acquisition system (e.g., running an fMRI experiment where MonkeyLogic and the scanner are started simultaneously, but then do not communicate once the task has begun), you will need to rely on the BHV file variable AbsoluteTrialStartTime. Because Windows occasionally updates its clock with respect to a remote server, there can be discontinuties or inaccuracies in the clock over time, making these values inaccurate. Rarely, this may happen during an experiment. To stop clock syncing during an experiment, you should edit the Windows Registry.
For older versions of MonkeyLogic: While most main menu functions work whenMATLAB is running in standard mode (with Java enabled), some functions-- and the behavioral task itself -- will not work reliably so long asJava is enabled, either in the Matlab environment or in anotherapplication (e.g., web browser). If Java is currently running,unexpected and sporadic crashes will occur. To run MATLAB without Java,type:
7fc3f7cf58