Organize Iceberg configuration
I am reorganizing the Iceberg reconstruction code.
#1 Updated by David Adams about 2 months ago
Most changes will be in fcl but I have modified the pedestal finder (tool AdcPedestalFitter) to make the removal of sticky codes optional and the width of the fit range a fcl parameter. The old hardwired value for the latter was 100 channels. These changes are made because the tool is occaissionally failing for Iceberg run 4 with COTS ADCs that have less response (fewer ADC counts per electron) and do not have sticky codes.
I have modified the tool configurations for PDSP to include the new parameters with values to reproduce the old values.
I have just committed these changes. Christoph, pls let me know if we see any change in the PDSP CI tests.
#2 Updated by David Adams about 2 months ago
The last commit includes many changes in the Iceberg configuration. Some are listed below.
A calibration for Iceberg 4b is added. We have (very) different calibrations for each of three run periods: 3 is Feb/March running with the PDSP ADCs, 4a and 4b are July/August withe COTS ADCs before and after a major DAQ update. More run periods are anticipated.
The dataprep Iceberg configuration code is modified so there are two sets of dataprep tool sequences, one for run period 3 and on for period 4. The calibration in the latter is selected by defining the tool areaGain_ib4. The period 4 dataprep does not remove sticky codes. I am now tuning the pedestal fits for these sequences.
I have removed some duplicate or obsolete files from the Iceberg directory. There are now three full-reco configurations: icebergX_decode_reco.fcl with X = 3, 4a and 4b. The goal of this ticket is to get these three working reasonably for runs in the corresponding period.
#4 Updated by Thomas Junk about 2 months ago
Here's the most recent boundary -- turning on the LArASIC buffer. From the e-log:
Entry 1348 07/30/2020 08:30:39
Entry Subject: Runs after the COTS-ADC Fixed
We have taken the following runs overnight after the COTS-ADC ODD/EVEN problem resolved.
Run number 6055-6090
#5 Updated by Thomas Junk about 2 months ago
And here's another run number from the warm COTS ADC running, run 5369. So runs after that are COTS-ADC runs.
Entry Subject: Run 5369 of COTS-ADC 7-34 (Room Temperature)
We installed COTS-ADC 7-34 on the test WIB004.
After getting the BUTools configured for COTS-ADC we were able to pass the FEMBs through initial test.
Configured the TLU for the pulser trigger. The rate had to be adjusted to get good data. 12 Hz works.
The data can be found at
#7 Updated by David Adams about 2 months ago
Thanks Tom. With your hint, I looked at am metadata and 5359 is also the last copied run taken in March.
6055-6090 still have the low noise (and so presumably low gain) of the preceding days. Further intervention was made after that and 6103 looks like the first pulser run for period 4a.
So we have
Run period Runs Noise [ADC count] 3 - 5359 2.5 4a 5360 - 6090 0.7 4b 6103 - 1.3
Tom, can you add Shekhar to our developer list so he can be added to this ticket? Thanks.
#10 Updated by Thomas Junk about 2 months ago
C. Mishra is listed in the dunetpc overview page. It does take a while to propagate the credential so git pushes are allowed due to cron jobs waking up. I added C. Mishra to the watchlist just now as part of this edit. The phonebook didn't have any other C. Mishras in it so I hope I got the right one.