Posted on Aug 6, 2020
This task is designed to show a target for a single frame on the subject display. The algorithm should work properly for any refresh rate on the subject display. The model is extensively commented with the details of the algorithm.
The task is compiled for MATLAB 2015a SP1 and Dexterit-E 3.7.
Posted on Aug 6, 2020
This is a task that will demonstrate the use of path targets, new in Dexterit-E 3.7. The task will draw a trail that will follow hand movement.
Compiled in MATLAB 2013a and Dexterit-E 3.7 and will not work on earlier Dexterit-E versions.
Posted on Aug 6, 2020
This demonstration task is intended to show the use of the repeat target type, new in Dexterit-E 3.7, and is based on the ideas presented in:
Britten, Kenneth H., Michael N. Shadlen, William T. Newsome, and J. Anthony Movshon. “The analysis of visual motion: a comparison of neuronal and psychophysical performance.” Journal of Neuroscience 12, no. 12 (1992): 4745-4765.
Pilly, Praveen K., and Aaron R. Seitz. “What a difference a parameter makes: A psychophysical comparison of random dot motion algorithms.” Vision research 49, no. 13 (2009): 1599-1612.
This task was compiled in MATLAB 2013a and Dexterit-E 3.7 and will not work on earlier Dexterit-E versions.
Posted on Aug 6, 2020
New in Dexterit-E 3.7, are three target types: polygon, path, and repeat. Polygons are targets that can specify up to 25 vertices. Paths are lines that connect up to 25 vertices. Repeat targets are targets that specify a circle, ellipse, rectangle, triangle, or line and draw it at up to 25 different locations.
In this task, the “Make VCODES” embedded MATLAB function block creates one example Vcode of each of the above target types to show what the new vcodes in Dexterit-E 3.7 can look like. Details on using the new Vcodes can be found in Section 10.7 VCodes – Programming Visual Stimuli of the Creating Task Programs for Dexterit-E™ 3.7 guide.
The task was compiled in Dexterit-E 3.7 and MATLAB 2013a.
Posted on Aug 6, 2020
This is a task written by Ethan Heming, a Ph.D. canditate in Steve Scott’s lab. Kinarm would like to thank Ethan for allowing us to post his task! This is easily the most sophisticated task program I have seen. This game really stretches what can be done with Simulink, Stateflow and indeed Dexterit-E.
This task requires a bilateral Kinarm End-Point robot with force-torque sensors.
The object of this game is to destroy as many enemies as possible on each level. You control a ship represented by a green bar between your hands. The thickness of this line shows your ship’s health. Any enemies or enemy shots that hit this bar reduce your health and the game ends when ship has no health left. If you get hit there will be a haptic response (i.e. you will feel it)! At each handle you have a “gun” that fire perpendicular to the green health bar. They are fired by ’tilting’ robot handle (applying a pitch or roll torque). The farther apart your hands are, the faster your guns recharge, but the larger a target you present to enemies.
At the start of each level you can buy upgrades to your guns and shields by moving the cursor to the desired selection and torquing on the handle. There are also addition options such as auto-cannon or bombs. During a level you can catch coins to earn money to buy things. You also earn coins by killing enemy ships.
Some extra special features are:
If you have an End-Point robot with force plates then stomping on the plate will release a bomb if you have purchased that upgrade.
I have compiled this task for Dexterit-E 3.5.2 and MATLAB 2013a.
Have fun!
Posted on Aug 6, 2020
This isn’t really a task per se, it’s really just a demonstration of how to dynamically manipulate an image and use forces. When you start the task an image of a spring will be displayed between the hands. As you try to move your hands apart or together you will feel a spring trying to hold you at one distance. The task will work on a Kinarm Exoskeleton or EP robot.
The task was built for Dexterit-E 3.5 and MATLAB 2013a.
Note: This is a much improved version of the task. This has been cleaned up substantially since the first version.
Posted on Aug 6, 2020
This task is provided to demonstrate how to create a visuomotor rotation task.
This task also provides an example of a “persistent” variable in embedded MATLAB (see the Calculate_Desired_Rotation function with /Visual_Rotation/Triggered Subsystem/).
Task was built using MATLAB 2013a and Dex 3.5
Posted on Jul 14, 2020
There is an example of how to create background targets from your target table in the background target example task. That version shows 10 targets at a time. One thing you may have noticed with that example is that the targets show up on the screen in order one at a time and they each take 1/60th of a second to show. This is because your task program needs to wait to ensure each new background target has been accepted. This works reasonably well for up to 60 targets because that will only take ~1s to send all targets.
This example demonstrates several concepts:
Dynamically creating large numbers of VCodes
Sending those VCodes in blocks (in this case 30 at a time)
Adding extra Stateflow charts to you model
Calling Matlab from Stateflow
What this example does specifically is:
Take in one “large” rectangular VCode, one small rectangular “tile” VCode, a number of tiles in the X and Y directions.
Creates X * Y “tile” VCodes that will completely cover the space defined by the “large” VCode
Turns on all of the “tiles” 30 at a time
Waits a specified duration
Turns off all the “tiles” 30 at a time
There is no interaction with the tiles, extending this model to interact with the tiles would not be hard. Limitations of the example are:
Up to 500 targets can be created (read comments in the model for how to make this larger)
Up to 30 targets at a time are sent (read comments in the model for how to make this larger)
All targets are assumed to be rectangular.
You can watch the shapes fill in with tiles. An easy extension to this would be to display a large black target over top of the permanent targets while they are being filled in and remove the black target when the tiling is done.
This was made with MATLAB 2013a and compiled for Dex 3.5.
Posted on Jul 14, 2020
Normally if you would like to show 10 targets on the screen at once you would have to send 10 VCodes at a time each cycle. This is not much of a problem, but now imagine you would like to show 30 targets at a time, this can be a bit cumbersome. The “show target in background” block helps get around this. A background target is one that is always shown in its “current” state until you send a new command that overrides the current state. Background VCodes are the same as normal VCodes except for 2 small things:
The target type is (normal target type + 100). i.e. a circle is 101.
There is an ID with the VCode that can be 1-1500. This is how you interact and change your permanent target states.
This sample task makes use of the “set target in background” block. The example protocol defines 30 targets of which 10 are shown at a time. When a target is touched its color changes. This is meant purely as an example of how to properly use background targets that are defined in your target table.
The example is made with MATLAB 2013a and compiled for Dex 3.5
P.S. For some reason this task can take a very long time to compile (5+ minutes on my machine that normally takes 1-2 minutes to compile a task)
Posted on Jul 14, 2020
This sample task, written for Dexterit-E 3.5 and MATLAB 2013a, grabs size/colour parameters for a circle target, and then moves that target in a circle. The purpose of this demo is to show how to manipulate a target’s location.
