Redmine: Issueshttps://redmine.jlab.org/https://redmine.jlab.org/favicon.ico?16338348402024-03-25T15:18:27ZRedmine
Redmine SBS-DAQ-GEn-RP - Bug #984 (New): Scalers not workinghttps://redmine.jlab.org/issues/9842024-03-25T15:18:27ZAlexandre Camsonnecamsonne@jlab.org
<p>Might be missing scaler not found</p> SBS-DAQ-GEn-RP - Bug #973 (New): BBCAL noisy channelshttps://redmine.jlab.org/issues/9732024-03-15T13:14:06ZAlexandre Camsonnecamsonne@jlab.orgSBS-DAQ-GEn-RP - Bug #965 (New): Hodoscope channel issuehttps://redmine.jlab.org/issues/9652024-03-04T16:13:23ZAlexandre Camsonnecamsonne@jlab.org
<p>One channel need HV spare channel</p>
<p>Room to add one card - need to check if we can find additionnal <br />-89 out of 96 - <br />spares</p>
<p>Can bring bad modules to Karen ? To see if that can be fixed<br />Room 122 in EEL building</p> SBS-DAQ-GEn-RP - Bug #949 (In Progress): Ship 1190 for active analyzerhttps://redmine.jlab.org/issues/9492024-02-19T13:08:54ZAlexandre Camsonnecamsonne@jlab.orgNPS - Bug #929 (In Progress): FADC channel with always same signal 952https://redmine.jlab.org/issues/9292024-02-01T15:28:05ZAlexandre Camsonnecamsonne@jlab.orgNPS - Bug #926 (New): HMS electron trigger efficiencyhttps://redmine.jlab.org/issues/9262024-02-01T14:56:56ZAlexandre Camsonnecamsonne@jlab.orgNPS - Bug #922 (New): Some calorimeter blocks at different temperature in displayhttps://redmine.jlab.org/issues/9222024-01-29T15:15:16ZAlexandre Camsonnecamsonne@jlab.org
<p>Some calorimeter blocks at different temperature in display</p>
<p>Maybe issue with multiplexer</p> NPS - Bug #875 (New): Need apply HMS momentum correctionhttps://redmine.jlab.org/issues/8752023-10-30T14:46:19ZAlexandre Camsonnecamsonne@jlab.orgNPS Calorimeter - Bug #820 (New): Interference HMS SHMShttps://redmine.jlab.org/issues/8202023-09-18T07:00:06ZAlexandre Camsonnecamsonne@jlab.orgNPS Calorimeter - Bug #815 (New): PMT with low gainshttps://redmine.jlab.org/issues/8152023-09-18T06:57:02ZAlexandre Camsonnecamsonne@jlab.orgBB-GRINCH - Bug #721 (New): GRINCH TDC data is 1ns integers. Is that the resolution we expect? https://redmine.jlab.org/issues/7212023-03-14T20:39:43ZMaria Satnik
<p>I realized that the root tree output for the TDC data for the grinch is in 1ns integers, and that might be odd if I'm being told to hunt for intrinsic resolutions under and around 1ns. I went through and double checked that everything is doubles in my macro, but they seem to be integer values when I cout them. I'm wondering if I'm doing something wrong or if maybe there's a flag or something that needs to be given in the replay.C?</p> BBCal_calibration - Bug #708 (Feedback): Look at the correlation of BBCal signal ADC time with BB...https://redmine.jlab.org/issues/7082023-03-07T19:46:52ZProvakar Dattapdbforce@jlab.org
<p>We looked at the correlation of BBCal signal ADC time with BBCal trigger time which get readout by a 1190 module situated in the TH crate. Here also we can clearly see a shift of about 12ns in the BBCal trigger trigger time. We take a copy of the BBCal trigger slightly before it goes to the TS to put that into a 1190 module. Then the TI of that module gets signal from the TS before opening the look-back window. So, seeing the same shift in 1190 output almost certainly indicate that the delay is coming from the TS itself.</p>
<p>After this finding, we tried to access the time sent out by the TI for each crate through replay to compare that with the time we get form TS and confirm the above mentioned inference. But accessing the time from TI didn't seem straight forward using the existing replay machinery. We'll reach out to the DAQ group to get help in this matter.</p> BBCal_calibration - Bug #707 (Feedback): Look at the ADC time distributions of BBCal trigger sumshttps://redmine.jlab.org/issues/7072023-03-07T19:27:16ZProvakar Dattapdbforce@jlab.org
<p>All 25 BBCal trigger sums are read out by two FADC modules which are situated in a different crate than the one used by BBCal PMT signals. Mark suggested me to look at the ADC time correlation between the highest energy block of BBCal cluster and the corresponding trigger sum. The events at the secondary peak were correlated in the same way as the ones in the primary peak. This would suggest that both the crates experienced the shift in time (~12ns) for same events, which would make sense if the delay is coming from the Trigger Supervisor itself.</p> BBCal_calibration - Bug #706 (In Progress): Double peaking in ADC time (SH + PS)https://redmine.jlab.org/issues/7062023-03-07T15:33:46ZProvakar Dattapdbforce@jlab.org
<p>ADC time distributions of SH and PS have two peaks roughly 12 ns apart. There is a main peak around 0 and a secondary peak with significantly less number of events around -12 ns. The secondary peak doesn't disappear with elastic cuts.</p> SoLID-muons - Bug #705 (In Progress): Pythia background and BB GENhttps://redmine.jlab.org/issues/7052023-02-21T16:01:07ZAlexandre Camsonnecamsonne@jlab.org