User manual

215
CHAPTER 11 – Experimental Log
11.1 Capabilities of the Experimental Log
The primary purpose of the Experimental Log is to show and record when important events occur in the
experiment. These events can include automatically generated information such as when a titanic
stimulation was delivered or when Low Frequency Stimulation was run, and will include the time and
name of which stimulation/acquisition ADsweep files delivered the particular stimulation. The events can
include manually input information such as when solutions were changed. The Experimental Log will also
automatically record important values such as the patch pipette series resistance (Rs) from the SealTest
protocol.
Each time WinLTP is run, the Experimental Log is saved to a single *.log file in the current DataFolder.
However, this ability to save the log is only available in the Advanced Version or during the
Demotrial Period.
The Experimental Log should substantially decrease the amount of information having to be manually
entered into your lab book, and it can serve as a check that the information manually entered into your lab
book is correct.
Specifically the Experimental Log shows:
1) When WinLTP was started and exited.
2) When the SealTest protocol was entered and returned, and it will print the PulseAmp, Rpipette,
Rseal, Rs, Rm and Idc values from the SealTest.
3) When
a) the Spreadsheet was cleared
b) an AmpFile was saved
c) a Protocol file was either opened or saved.
4) When a Continuous Acquisition protocol was started and stopped.
5) When the Main Protocol was started and stopped.
6) When particular stimulation/acquisition ADsweeps have occurred (P0sweeps, P1sweeps,
T0sweeps, T1sweeps, AP0sweeps and AP1sweeps). For example, if the titanic LTP induction
stimulation was in a T0sweep, then the Experimental Log will record when that stimulation was
delivered.
7) When there was a change in protocol flow, such as the starting and stopping of Loops, AvgLoops,
Runs, Run of Run/Else, Else of Run/Else.
8) When Evoked Single Events (i.e. single ADsweeps) are delivered, and Repeat Events (i.e. multiple
ADsweeps) delivered.
9) When a Perfusion solution was changed for Automated Perfusion
10) And finally, to be able to manually enter and record the time and solution change by keyboard
input.
Fig. 11.1.1 shows an example of an Experimental Log output from an ersatz short protocol. The Log
specifically shows when WinLTP was started, when the Main Protocol was started and stopped, when
there was a change in protocol flow for starting and stopping Loops and Runs, when Evoked Repeat
Sweeps and Evoked Single Sweeps were delivered, and the time when a solution change was manually
entered by keyboard input (“0:30 100uM AP5” entered at the Add Event line).