WFs that recorded from A3 string 4 show ADC counts duplication from run 12866 (December 2018)
-> The same time when the dead bit issue happened)
Every ADC in the 1st & 3rd quarter of blocks (16 samples) are duplicated (overwriting) in the 2nd & 4th quarter of blocks
Whether half WF (after removing duplication) is useful or not is on the test by reconstruction
But in order to avoid confusion in the future, I believe 'exclude duplicated samples from WF' needs to be the default configuration.
Duplication only appears in the 2nd and 4th quarters of the block on string 4. I decided to add a new timing table that excludes the duplicated regions as bad samples. araAtriStation3SampleTimingNew_2019DataSet.txt is basically identical with araAtriStation3SampleTimingNew.txt except string 4 channels. The number of useful samples will be half like below table
Related talk: DB2535
WFs that recorded from A3 string 4 show ADC counts duplication from run 12866 (December 2018) -> The same time when the dead bit issue happened) Every ADC in the 1st & 3rd quarter of blocks (16 samples) are duplicated (overwriting) in the 2nd & 4th quarter of blocks
Whether half WF (after removing duplication) is useful or not is on the test by reconstruction But in order to avoid confusion in the future, I believe 'exclude duplicated samples from WF' needs to be the default configuration.
Duplication only appears in the 2nd and 4th quarters of the block on string 4. I decided to add a new timing table that excludes the duplicated regions as bad samples. araAtriStation3SampleTimingNew_2019DataSet.txt is basically identical with araAtriStation3SampleTimingNew.txt except string 4 channels. The number of useful samples will be half like below table
Any opinions are welcome!:)