gin commit from nit-ope-de04

New files: 9

neuralynx/broken_data/dsp_compensation_and_ringbuff_errors/CheetahLogFile.txt

@@ -0,0 +1 @@
+/annex/objects/MD5E-s3131182--7b7655b31e2db80bf25032e0b8c5c026.txt

neuralynx/broken_data/dsp_compensation_and_ringbuff_errors/CheetahLostADRecords.txt

@@ -0,0 +1 @@
+/annex/objects/MD5E-s16384--32ae79e7ad80fb09491565ed50292eb4.txt

neuralynx/broken_data/dsp_compensation_and_ringbuff_errors/Events.nev

@@ -0,0 +1 @@
+/annex/objects/MD5E-s1567872--ec399ea515cb5d8695a6f93f1f9a0f90.nev

neuralynx/broken_data/dsp_compensation_and_ringbuff_errors/README.txt

@@ -0,0 +1,16 @@
+In this recording, 'dsp_compensated_buff_errs' had a bandpassfilter (dsp) and it's lag is compensated for by Cheetah:
+-DspDelayCompensation Enabled
+-DspFilterDelay_µs 3984
+
+while the 'no_dsp_buff_errs' had no dsp:
+-DspDelayCompensation Enabled
+-DspFilterDelay_µs 0
+
+The result is that 'dsp_compensated_buff_errs' has slightl more datapoints than 'no_dsp_buff_errs'. This gives a break in current
+neo as it requires the data to have the same length.
+
+The other problem with this data are RingBuffer errors (search the logfile), which are now treated by making different segments
+per gap. Both channels with have different gap times, also causing a break in current io.
+
+Thijs Ruikes
+t.r.ruikes@uva.nl

neuralynx/broken_data/dsp_compensation_and_ringbuff_errors/dsp_compensated_buff_errs.ncs

@@ -0,0 +1 @@
+/annex/objects/MD5E-s352218136--0d4de12b9e565e217b9981f4efdf3a93.ncs

neuralynx/broken_data/dsp_compensation_and_ringbuff_errors/no_dsp_buff_errs.ncs

@@ -0,0 +1 @@
+/annex/objects/MD5E-s351696136--1614a018d9bcb798d3169969c52aa6a6.ncs

neuralynx/broken_data/dsp_no_compensation/README.txt

@@ -0,0 +1,8 @@
+These two channels belong to the same recording session. During the recording, one had a bandpassfilter enabled (DSP) which causes 
+a lag. Neuralynx can compensate for this (DspDelayCompensation Enabled), but this is not the case for this data.
+
+We  processed them without knowing about this, but when clustering we would see duplicate neurons with a lag, the neuron
+would be detected on both leads and not be marked as the same neuron. To prevent this one should compensate for the lag.
+
+Thijs Ruikes
+t.r.ruikes@uva.nl

neuralynx/broken_data/dsp_no_compensation/dsp_comp_disabled_no_lag.ncs

@@ -0,0 +1 @@
+/annex/objects/MD5E-s280066252--af5555a4f84c89ffe56905b1bf864c9f.ncs

neuralynx/broken_data/dsp_no_compensation/dsp_comp_disabled_with_lag.ncs

@@ -0,0 +1 @@
+/annex/objects/MD5E-s280066252--0b7720e559bd43d1a747a4cfa0b84a92.ncs