Dear valued customer, 
 
Welcome to pCLAMP 6.0.4! 
 
Please scan through this file in its entirety, as it contains some 
time-saving reminders, tells you where to find descriptions of the 
bug fixes made, and also describes some important enhancements to pCLAMP  
since the version 6.0 release described in the manual.  The information 
gained will more than make up for the time needed to read this file.  
This information is NOT contained anywhere else. 
 
LATE NEWS

At the time that this release was compiled some customers received the first
of the 266 MHz Pentium II generation of computers.  It was discovered that
Clampfit fails to start reliably on many of these computers.  A new version
of Clampfit was prepared to address this problem but there was not sufficient
time to test it adequately.

If when starting Clampfit on a 266 MHz or faster computer you receive a
"Runtime Error 200" message, please contact Axon Technical Support.  Our
Technical Support staff will be able to make arrangements to supply you with
the latest version of Clampfit that will fix this problem.

 
REMINDERS 
 
To navigate the menus... 
(1)  Hold down the <Alt> key while pressing the gray <Arrow> keys (not the 
ones on the numeric keypad), 
or 
(2)  Press the FIRST UPPER CASE letter in the command, 
or 
(3)  Press <TAB> or <SHIFT-TAB>. 
 
Many form-fields have attached lists.  (When highlighted, any such field 
will show a small, vertical, double-headed arrow at the far right of 
the help line.)   Press <PgUp> or <PgDn> to scroll through the available 
choices. 
 
See Help/Basics for more complete information on menus, forms and other 
keyboard shortcuts. 
 
 
CHANGES in VERSION 6.0.4 
 
BUG-FIXES 

Version 6.0.4 differs primarily from version 6.0.3 in that a number of 
minor bugs have been fixed.  For each pCLAMP program, a detailed description 
of the bugs fixed can be found in the associated TXT file (e.g., 
CLAMPFIT.TXT, FETCHAN.TXT). 

 
CHANGES in VERSION 6.0.3 
 
BUG-FIXES 
 
Version 6.0.3 differs primarily from version 6.0.2 in that a number of 
minor bugs have been fixed.  For each pCLAMP program, a detailed description 
of the bugs fixed can be found in the associated TXT file (e.g., 
CLAMPFIT.TXT, FETCHAN.TXT). 
 
 
ENHANCEMENTS! 
 
CLAMPEX  and  FETCHEX  ENHANCEMENTS IN VERSION 6.0.2. . . 
The bus timing on some new computers is so fast that it no longer conforms 
to IBM AT standards.  This occasionally caused version 6.0 of Clampex 
and Fetchex to perform erratically.  A new "Timing Loop Count" field has 
been added to the Configure/Hardware form that enables the bus instructions 
for the timers on the acquisition board to be slowed down (by adding 
wait states).  (Its default value is unity.) 
 
If you have such a computer, you may observe that the clock in the status 
line counts erratically or that the time between episode starts is not 
consistent.  If so, increase the "Timing Loop Count" to a value at which  
this no longer occurs. 
 
FETCHAN  ENHANCEMENTS IN VERSION 6.0.2 . . . 
Fetchan can now track baseline level changes during Events List/Latency 
analysis much more accurately.  Two new fields in Parameters/Special 
help to achieve this:  "Baseline Update strategy" and "Update during 
baseline". 
 
BASELINE UPDATE STRATEGY 
The new default option is to weight short events less.  Unitary weighting 
is given to baseline events that reach a "reliable" length. 
 
Previously, Fetchan gave equal weighting to all baseline events when 
updating the baseline (assuming baseline tracking was enabled).  In some 
cases, the duration of a baseline event was too short to obtain a reliable 
estimate of the baseline current.  The current version of Fetchan allows 
the user to give less weighting to these "unreliable" baseline events. 
 
Let Tau be defined as the number of sampled points needed to have your 
system respond by 63% to a step change in input.  Define N as the larger 
of 50 sample points or 100 * Tau.  Let n be the number of sample points 
within a given baseline event.  The "Weight short events less" option 
linearly weights events less than N in duration by:  n / N.  For example, 
given N = 100, a baseline event lasting 3 sample points would be given 
only 3% of the weighting given to events with durations longer than 
100 sample points. 
 
UPDATE DURING BASELINE 
The new default option is to update the baseline between events, allowing 
Fetchan to track baseline drift between events! 
 
Previously, Fetchan would only update the baseline when it found a baseline 
event.  This strategy worked well for many experiments, but not for 
experiments that had periods of channel activity interspersed with long 
intervals without events.  Fetchan was unable to correct for significant 
baseline drift during one of these long intervals. 
 
When "Update during baseline" is enabled, Fetchan can now accurately track 
the baseline in such cases.  This option is also useful if Fetchan's 
detection levels are thrown off temporarily by an interval of extraneous 
noise or patch breakdown.  Previously, it would be unable to recover as 
Fetchan had to "find" an event before it could correct the baseline. 
 
NOTE:  The default value for the "Baseline update strategy" field is 
"Weight short events less".  The default value for the "Update during 
baseline" field is "Yes".  If the alternate values for these two fields  
are selected ("Weight all events equally" and "No", respectively), 
Fetchan V6.0.2 behaves identically to versions 6.0 and 6.0.1. 
 
OTHER  FETCHAN and pSTAT  ENHANCEMENTS . . . 
A small change was made to Fetchan, pSTAT and to the Events List file 
format (.EVL files) to allow more accurate determination of Popen. 
 
Previously, during latency file analysis, Fetchan did NOT write out the 
last event in an episode to the events list file.  This was to prevent 
pSTAT from erroneously including its duration in dwell-time histograms 
(it is a truncated event).  This prevented some customers from tracking 
Popen accurately though, since Fetchan did not write out events from 
episodes containing only one event (e.g., closed the entire time). 
 
The new version of Fetchan now writes out ALL events from every episode.  
The last event is now marked with a "T" in the Notes section to indicate 
that the event was truncated.  The EVL version number was incremented 
to allow this.  The new version of pSTAT knows to not include truncated 
events in its dwell-time histograms.  To maintain compatibility with 
older versions of the events list, pSTAT knows to include all events, 
as Fetchan did not write out truncated events. 
 
 
AXOTOOLS  ENHANCEMENTS IN VERSION 6.0.2 . . . 
 
DATA2ABF 
Many customers have requested that we provide them with a tool that 
could convert their data files into Axon's ABF format.  DATA2ABF is a 
new utility program that will allow binary integer, floating point or 
double-precision floating point files to be converted into ABF files.  
It will also convert Axon's ATF files into ABF files.  (Users with 
plain ASCII files must first convert these files to ATF files using 
ASC2ATF.) 
 
The ABF file header contains many variables describing (among other 
things) the number of A/D channels, their names, units and scaling 
factors.  Be sure that these values are specified correctly, or pCLAMP's 
programs will not display your data with the correct scaling factors. 
 
Binary integer data files are assumed to represent signals that have 
already been amplified and digitized.  When creating the ABF file, the 
header is created and the data are simply copied across to the new file. 
 
Binary floating point, double-precision floating point and ATF files are 
assumed to represent raw signal values (e.g., Force between 0 and 1 
Newtons).  The header is created as with binary integer files, but the 
scaling factors and the A/D range and resolution values are used to AMPLIFY 
the data and to DIGITIZE them.  The purpose is to scale the data so that 
they use as much of the A/D resolution as possible.  See the DATA2ABF.TXT 
file for more information on these scaling factors. 
 
NOTE:  DATA2ABF only works with gap-free data files.  It cannot create 
Clampex-style fixed-length and variable-length event files or AxoTape-style 
oscilloscope files at this time. 
 
Axon Instruments, Inc. 
September 1997
