Signal Scripts



Examples of Method

Write frame data to the log window (07/99)

Write frame data to the log window

dumpfrm.zip

The script writes frame information to a log window, a simple demonstration of accessing frame information and output to the log window.

Compare data from two files (06/09)

Compare data from two files

compdata.zip

This script can be used to compare two data files. As it stands, it performs a few simple checks on the two files to determine whether their contents are the same, but it could be modified to allow you to modify the data contained in the two files, instead of simply comparing it.

Design of complex interactive dialog boxes (06/05)

Design of complex interactive dialog boxes

dlgdesignsg.zip

This script allows you to create complex Signal script dialogs without writing code. You can add, delete, move and edit dialog items interactively by pressing toolbar buttons and using keyboard shortcuts. You can create dialogs with up to 20 user-defined buttons, up to 40 items of other types and up to 200 text prompts. When you have finished designing your dialog, the script prints out the required code so that you can copy and paste it into your script.

This script requires Signal v3 or higher.

Print a specified subset of frames (05/10)

Print a specified subset of frames

PrintFrames.zip

This script will print the specified frames and time range selected by the user. When the script is run, it prompts you to open a file and set up the view ready to print. You can then specify which frames should be included.

This script requires Signal v2.16 or higher.

Read Magstim parameters from a data file (05/10)

Read Magstim parameters from a data file

FrameVariables.zip

This script reads back Magstim or other auxiliary device parameters that are stored as frame variables in a data file during sampling. This example prints a list of the variables for each frame to the Log window, but could easily be modified to print specific variable values to a trend plot, for example. A suitable example data file, MEPexample.cfs, is included in the .Zip file.

This script requires Signal v2.16 or higher.

Area over a user-defined baseline (05/10)

Area over a user-defined baseline

AreaOverBaseline.zip

This script is an example of using an idle routine to update measurements based on changes in a cursor position. It allows the user to position a horizontal cursor at a baseline and two vertical cursors around the area to measure. The area over baseline measurement is then displayed in the toolbar and updated whenever the baseline or start and end position cursors are adjusted.

This script requires Signal v2.16 or higher.

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 Tim Bergel. We provide some scripts for Spike2 too.

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

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. ×