Tuda logbooks General E1104 ISACII E1195 E1103 E1147 S1287 S1203 S1233 S1284 S1447 23Na(a,p) S1540 S1381  S1847 Catania

S1287

Fields marked with * are required Entry time: Thu Nov 14 22:29:52 2024 Author*: Type: - please select - Routine Other Category: - please select - General Other Subject: <p>Handover from last shift was...</p> <p>1. Running at 4.11 MeV/u at about 15enA (5+)</p> <p>2. Would like to take more beam but already at situation where deadtime about 50%.&nbsp; They have been raising thresholds on the inner strips of S2-1 to try and cure that, but it doesn't appear to have helped.</p> <p>3. There is a sort of the past runs ongoing to use the counts in spectrum 4200 (coincidences) to estimate when there is enough data at this energy to move to the next.</p> <p>&nbsp;</p> <p>Analysis:</p> <p>Firstly, the locus being looked at in the S2-1 vs S2-2 to make this judgement cant be right.&nbsp; There are already thousands of counts in this in a replay of a one hour run&nbsp; Jamie's estimates in the run proposal were for 1,000 in 12 hours at 10**8/s.&nbsp; We are currently at 20% of that beam intensity and the deadlime is about 50%, so should be seeing 10 counts in one hour.&nbsp; The data must be somewhere else in the plot.&nbsp; My guess is that the intense locus is elastic/inelastic scattering coincidences.&nbsp; If this is the case then it maybe we have an issue in that these may be what is dominating the rate and it will not be possible to get rid of them from the trigger.</p> <p>Looking at the S2-1 energy spectra, it looks like the raised threshold is cutting into potential data (maybe Alex who knows from the MC what energy the data extends down to should look at this and check).&nbsp; The high trigger ratemust be from another channel.</p> <p>&nbsp;</p> <p>Actions for this shift</p> <p>1. With two people on shift and a requirement that we need two down in the area at all times, I don't think chasing thresholds is viable.&nbsp; This will have to be left to the day shift.</p> <p>2. Should continue the sorts so that we have the spectra available to make rate estimates once we know what we are looking for.</p> <p>3. Should look at the sort code to see what calibrations are being used and so determine where on the coincidence spectrum the data should lie.</p> Encoding: HTML   ELCode   plain   Suppress Email notification Attachment 1:

ELOG V2.9.2-2455