UMN CDMS Wiki archive
start › cdms › k100 › run_diary › 20190207

2019/02/07 (Thursday)

Previous Day

1115 One more DCRC test. Plug in DCRC1, disable all others in MIDAS ODB. Test signal still connected to all channels. Start triggering on DCRC1PA. Adjust driver offsets so that the 4 channels span different and separate amplitude ranges. This will help us identify where glitch bins are originating.
1118 Start 20 min test data series with DCRC1 phonon trigger =(25/-/-/-). DCRC1 phonons connected to 5kHz test signals at the preamp(DCRC1) and driver offsets arranged to center the signals at PA/PB/PC/PD = (0.75/0.25/-0.25/-0.75)V with ~0.05 V signal amplitude.
1150 Casually noticed 2 cases when one channel (PB,PD) seemed to pick up glitch bins that were from another channel(PA,PC). Using pulse viewer, change to triggering on PB with a threshold just above the test signal amplitude. This way, we can trigger on such glitches if they occur before the trigger logic is applied.
1409 Came back and looked at pulse viewer, but it still has not triggered. I think this means these mid-trace glitches must occur after the trigger logic is applied. So data is leaking from one channel into another between the trigger logic and the pulse viewer. Stop MIDAS run and turn off DCRC.

A quick analysis of this dataset was done. As before, we can find glitches by comparing individual events to the average. The plot below shows the ADC values of mid-trace glitches in each channel as points. The horizontal lines show the approximate range of test signal values in each channel. So if a point falls between lines of the same color, those glitchy bins seem to have come from the same trace, but when they appear in a different band, it may be an indication that the glitchy bins were originally in a different channel. This seems to show that PA and PC each only draw glitches from themselves. In contrast, PB and PD draw glitchy bins from both themselves and PA and PC respectively. Though not shown below, the first-8 bin glitches are generally drawn from the channel itself, though there are rare exceptions.

CALL WITH STEN on 2019 Feb 12:

we will send him a board *and the minibob*

we should ask CA people if they can send us spare minibobs

we'll ship one now, and Nick will consider whether to travel to FNAL, maybe next week

Sten asked if he could change to simpler test signal firmware - if so we'd need to change our MIDAS daq. (would it work for C.0 and c.1?)

ship to something like:

Attn Sten Hansen receiving site 38 kirk and pine MS222 batavia 60510

630-840-4027