WinLTP
Version 2.30
Leading-Edge Features
Special Features
Special Analysis Features
Ordinary Features
Additional Features

What's new in WinLTP 2.30

Fully Compliant with Windows 10

WinLTP 2.30 is primarily a major compiler upgrade to make WinLTP completely compatible with Windows 10.  For example, the file system will now work perfectly on Windows 10. However, most of the changes are internal, "under the hood" and are not apparent to the user.

WinLTP 2.30 will run on Windows 10, 8, 7 and Vista, but unfortunately will no longer run on the obsolete Windows XP. While it makes sense for a data acquisition program like WinLTP to run on a Windows XP computer NOT connected to the Internet, most computers must be connected to the Internet. Because Microsoft no longer supports Windows XP, Windows XP computers cannot be connected to the Internet. It therefore makes sense that our latest Embarcadero/Borland C++ compiler no longer supports Windows XP.

Therefore in addition to providing WinLTP 2.30 that runs on Windows 10, 8, 7 and Vista, we will continue to provide Windows 2.20 to run on Windows 8, 7, Vista and XP.

NOTE: For Windows 10 and the M/X-series boards, you should use NI-DAQmx version of 15.5 or later.

 

Population Spike Area

In the WinLTP 2.30 Reanalysis program we have added Population Spike Area to Population Spike Amplitude and Latency analysis.

Both WinLTP Acquisition and Reanalysis can analyze Population Spikes.

For the WinLTP 2.30 M/X-series online acquisition there are two programs:

1) For "WinLTP 2.30 M/X-series", there is online PopSpike Area analysis, but you will have to rewrite your protocol files from WinLTP 2.10 or 2.20.

2) For "WinLTP 2.30 M/X-series NoPSarea", there is no online PopSpike Area analysis, but you will not have to rewrite your protocol files from WinLTP 2.10 or 2.20.  This is for WinLTP users that just want to upgrade to Windows 10 but do not want to rewrite their protocol files.   This is for WinLTP users who just want to upgrade to Windows 10 but do not want to rewrite their protocol files.

There are several analysis programs that can measure Population Spike Area, Amplitude and Latency. However, to our knowledge, WinLTP is the only data acquisition program (working with non-proprietary, generally available bio-amplifiers, ie not MEA systems) that can do ONLINE Population Spike Area, Amplitude and Latency analysis.

The PopSpike Amplitude is calculated as the amplitude from the PopSpike peak to the intersection with an interpolated tangent dotted line drawn between the pre-PopSpike peak to the post-PopSpike peak (shown be the solid vertical line in the figure below). PopSpike Latency is calculated as the time between the occurrence of stimulus pulse and the PopSpike peak. PopSpike Area, PopSpike Amplitude and PopSpike Latency do not depend upon DC baseline or Peak Amplitude.

For more information see Section 4.11.9 in the on-line WinLTP Manual.

Detection of Population Spike Amplitude, Latency and Area. Detection occurs between the left and right brackets on the waveform. The solid vertical line is the Population Spike Amplitude, and the time between the stimulus pulse and the solid vertical line is the Population Spike Latency.

 

Reanalysis of Multi-Sweep Binary Axon ABF, IgorPro IBW, and WinWCP WCP Files

Thanks to a program written by Alen Eapen, bin2txtswps.exe will convert multi-sweep Axon ABF files, Igor Pro IBW files and WinWCP WCP binary files to single sweep ASCII ATF (Axon Text Files).  WinLTP can then easily reanalyse these ATF files.

Special WinLTP reanalyses include: PopSpike Area, Amplitude and Latency, Coastline, three types of Slope measurement, stimulus artefact blanking, analysis of all EPSPs in a sweep, and special analyses of trains.

Bin2txtswps.exe is an open source Python program that uses th e BDS Licensed Neo package to perform the binary to ASCII ATF file conversions. It is a separate program from WinLTP and can be run independently from the command line. The source code is freely available on github at: https://github.com/aleneapen/bin2txtswps, and the actual bin2txtswps.exe executable program is freely available in this WinLTP 2.30 download.

bin2txtswps can be run from within the WinLTP Reanalysis program by clicking on the menu (red arrow, Fig. A):
      SweepFile -> Convert ABF, IBW or WCP Binary Files to Axon ATF Text Sweep Files...
Then, within bin2txtswps.exe, click the 'Choose Folder' button (red arrow, Fig. B) to choose the folder containing the ABF, IBW and/or WCP files.  Then click on the chosen folder and click on the 'Select Folder' button (red arrow, Fig. C).  And finally click the 'Start Conversion' button (red arrow, Fig. D) to convert the sweeps in the ABF, IBW and/or WCP binary files to single sweep ASCII Axon ATF Text Files (lower part of Fig. D).

Back in the WinLTP Reanalysis program, click the 'Start Reanalysis' button to bring up the 'Select Files to Reanalyze' dialog box, move to the folder containing the single sweep ASCII Axon ATF Text Files, select the files you want to reanalyze and click OK. WinLTP will automatically detect that the single sweep files are ATF files and proceed to automatically reanalyze them.

ABF and WCP files seem to convert with little or no problems.  However, IBW files can be problematic.  The ATF files of some IBW files may have no units (DataType) or  ScaleFactor (ie mVperUnit or gain).  If that is the case, then analyze the ATF files as 'General ASCII files' and supply reasonable units ("mV" or "pA") and reasonable ScaleFactors (say 100 mV/mV for "mV" units, or 10mV/pA for "pA" units).  Then increase the gain if the signal is too "bitty", or decrease the gain if the signal is truncated.

 

A
  
 
 
                                                            
  B   
                                                                          
      C   
                                                                                   
                D