Spike2 Scripts


Control

Control a Telemetry Research interface (05/10)

Control a Telemetry Research interface

TR Control.zip

This script and associated sequence is an example of interacting with a Telemetry Research interface. The script creates a toolbar which allows the user to control sampling and set the duration of recording periods and gaps.

Digital output 0 of the 1401 should be connected to the trigger input of the Telemetry Research transmitter and DAC 0 connected to the external channel select input to select a channel between 1 and 12. The signal you want to sample should then be connected to ADC 0.

This script requires Spike2 v5.17 or higher.

Control a Digitimer DS5 Stimulator Improved! (01/17)

Control a Digitimer DS5 Stimulator

DS5Control.zip

This script and associated sequence is an example of using a DAC output from the 1401 to control a Digitimer DS5 Isolated Bipolar Constant Current stimulator and update the settings during sampling.

This script requires Spike2 v6.14 or higher.

Calibrate waveform capture Improved! (01/17)

Calibrate waveform capture

calib.zip

This script allows the user to calibrate the scale and offset of waveform channels in a sampling configuration. First create a sampling configuration (or load in a previous one) and then run the script. You can sample data into a temporary data file. When sampling this data, you should make the waveform that you wish to calibrate stay at two distinct known levels for a short period of time.

You can then press the "Calibrate" button. This enables you to select the two level sections of waveform data in a channel and to specify what values they SHOULD be. The script will then alter the channel scale and offset in the sampling configuration to achieve those values.

Generate paired pulses and analyse the results
Improved! (01/17)

Generate paired pulses and analyse the results

ppulse.zip

The PPulse script sends paired pulses out through Digital Outputs 0 and 1. The time between the pulses (the inter-stimulus time) is chosen at random from a list of possible values held in a stipulated text file.

To run this script, make sure you have the sequencer files PPulse1, PPulse2 and PPulse3 in the same directory as the PPulse script. You must also have in this directory a text file containing the ISI's to use (an example text file called ISITimes is supplied).

Finally, connect Digital Outputs 0 and 1 to Event Inputs 0 and 1 on a micro 1401 (or if you are using a standard 1401 or 1401plus, connect Digital Outputs 0 and 1 to Digital Inputs 0 and 1).

The PPulseAn script is a standard analysis script which indicates how the analysis of data collected using the PPulse script might be automated.

Extended documentation (in Word format) is given for both scripts.

Some of these scripts have come from users rather than the CED team. If you have a script that you would like to offer to fellow users via this page, please tell Simon Gray. We provide some scripts for Signal too.

These scripts are stored as WinZip files, myscript.zip, except where they are shown as spike\scripts\myscript.s2s. Those latter files were installed with Spike2 and spike stands for the directory in which you installed Spike2. See the summaries by clicking on the description in the side menu. Then you can down-load them by clicking on the filename.

×

Mains ‘hum’ is often complex and composed of odd harmonics of the mains frequency, making it very difficult to remove or suppress using simple high pass or notch filters. HumRemoveExpress.s2s is a Spike2 version 7 script that you can use offline to strip out much of this residual mains interference, making your data much more presentable and easier to analyse. This video tutorial shows how to use the script to remove mains hum.

  • Alpha MED Sciences
  • Alpha Omega Engineering
  • Axon Instruments
  • Binary data
  • Bionic/Cyberkinetics
  • Biopac
  • CED CFS
  • CED SON (Macintosh)
  • CONSAM (D. Colquhuon)
  • DATAQ Instruments (Codas)
  • DataWave
  • DATAPAC
  • Data Sciences International
  • Delsys Files
  • European Data Format(+)
  • Grass-Telefactor (PolyView)
  • HLR Data Format
  • Heka Data Format
  • Multi Channel System (Mc_Rack)
  • MindSet (16/24) data Files
  • MindWare data files
  • Motion Labs Systems Files .c3d
  • NeuroScan
  • Neuralynx
  • Plexon
  • RC Electronics
  • Text files
  • TMS International
  • Tucker-Davis Technologies
  • WAV (Microsoft)
  • WaveMetrics Igor Pro (PC/Mac)
  • Xltek Neuroworks
×

Cambridge Electronic Design Limited

Registered in England: 972132

Registered office:

  • Cambridge Electronic Design Limited,
  • Technical Centre,
  • 139 Cambridge Road,
  • Milton,
  • Cambridge CB24 6AZ
  • ENGLAND.

VAT: GB 214 2617 96

Producer Registration number: WEE/BD0050TZ

Terms and Conditions of Sale

For our US customers, we can provide tax form W-8BEN, that identifies us as a UK company.

DUNS: 219151016
CAGE/NCAGE: KB797
NAICS: 423490
Commodity codes
Hardware: 84716070
Software: 85234945
×

By email:

info@ced.co.uk

By post:
  • Cambridge Electronic Design Limited,
  • Technical Centre,
  • 139 Cambridge Road,
  • Milton,
  • Cambridge CB24 6AZ
  • ENGLAND.
By telephone:

(Int.+44) (0)1223 420186

From North America (Toll Free):

1 800 345 7794

×

Privacy policy

CED, through this site, does two things that relate to privacy. We would like to explain them.

Emails from down-loads

We offer free down-loads of many files on our site, from test programs to complete install files for updated versions of major packages like Spike2 and Signal.

When customers wish to take a down-load of a major package, we ask a few questions, including their name, email address, the serial number of the software for which they seek an upgrade and whether they would like an automatic email whenever we update the product. This information is emailed back to CED when they access the final down-load screen. Within this email, your browser transmits the type and version of browser you are using, and the screen resolution you are running.

The reasons why we take and keep this information are that it is useful for our software development team to know who has taken the latest versions, and it is useful for our web site development team to know which browsers people are using to view our site, and what resolution they have their screens set to.

Cookies

When people down-load a major package, we try to write a cookie, a small file in your computer, that records your name, serial number of the software package, and the version you are down-loading. These files have a lifetime of one year.

The reasons for storing this information are firstly that if you ask for another down-load some other time, your details are read from the cookie and are pre-written into the form, to save you looking them up again. The other reason is that next time you access our site, your browser looks through your CED cookies and compares the versions down-loaded with the latest version numbers read from our site. If there is a later version of a product you have already down-loaded, we tell you on the home page screen, so you know that it is worth going to the down-load page again.

None of this information is ever given to anyone outside CED. ×