<p><strong>---9 July---</strong></p>
<p><strong>11:00</strong></p>
<p>Turned detectors on - all stable see attachment 1 </p>
<p>AIDA started - all okay. See attachment 2 for FEE temps. </p>
<p>All FEEs set to LEC (0x0) and slow comparator threshold set to 300keV (0x1e). See attachment 3. </p>
<p>After some issues tape server and merger all set up, NetVar not working??? have tried to reboot things but still getting issues. See attachment 4 for tape service and attachment 5 for merger. </p>
<p>Currently writing to data to G22-205/R98 (R97 empty), doing background run.</p>
<p><strong>13:30</strong></p>
<p>All checks okay apart from white rabbit, see attachment 6.</p>
<p>Attachment 7 - stats </p>
<p><strong>18:30 CEST</strong></p>
<p>More issues with anydesk - now refuses to connect with error message desk_rt_ipc</p>
<p>May be as simple as the monitor being turned off. Will have to be checked in person</p>
<p>Connected to atppc025 via x2go and from there checked</p>
<p>- Temperatures are fine (attached)</p>
<p>- Detector bias / leakage current is fine (attached)</p>
<p>- Data rate from file size being written is around 500 kB/s (fine)</p>
<p>- A number of interesting features in the online background spectrum. Likely all non-physical (attached)</p>
<p>- Stats OK (attached)</p>
<p><strong>20:50 CEST</strong></p>
<p>All checks good.</p>
<p><strong>22:28 CEST</strong></p>
<p>All checks good.</p>
<p>Features in the XY plot rensemble beam hitting the detectors. Attached.</p>
<p>Leakage currents and rates are good - unlikely to be major detector damage. Attached.</p>
<p>Only beam in the ring between now and end of D+D was stable uranium.</p>
<p>Killed CARMEsort via terminal (still no access to anydesk).</p>
<p>Restarted CARMEsort. No obvious structures appear after a few minutes. Was there beam in the ring today?</p>
<p><strong>23:09 CEST</strong></p>
<p>All checks good</p>
<p>Features in the XY plot and Ey plots disappeared.</p>
<p> </p>
<p> </p>
<p><strong>---10 July---</strong></p>
<p><strong>03:22 CEST</strong></p>
<p>All checks good.</p>
<p>Features gone. Attached.</p>
<p><strong>05:15 CEST</strong></p>
<p>All checks good.</p>
<p><strong>07:34 CEST</strong></p>
<p>All checks good.</p>
<p><strong>10:40 CEST</strong></p>
<p>All checks good. </p>
<p><strong>12:35 CEST</strong></p>
<p>All checks good. Some features in plots again appeared in last 2 hours, attached Ey plot (attachment 15). </p>
<p><strong>14:40 CEST</strong></p>
<p>All checks okay. </p>
<p><strong>16:40 CEST</strong></p>
<p>All checks okay. </p>
<p><strong>18:40 CEST</strong></p>
<p>All checks okay. Attachment 16 leakage current stable. </p>
<p>Attachment 17 Ey plot.</p>
<p><strong>19:35 CEST</strong></p>
<p>All checks OK.</p>
<p>Reset the Root spectra again - highly unlikely to have beam overnight without experiments running.</p>
<p><strong>23:39 CEST</strong></p>
<p>All checks OK.</p>
<p>Still seeing peak at 6 MeV like attachment 17, after resetting the Root spectra. Detector damage? Still seems implausible.</p>
<p>Events are focussed as in attachment 12.</p>
<p>Reset again. No obvious peak or pattern after a few minutes running.</p>
<p> </p>
<p><em><strong>From Claude K</strong></em></p>
<blockquote>
<p><em>"CRYRING was running with the Uranium beam from ESR until Tuesday (8 July) night around 22:00.<br />
<br />
From Wednesday noon we started to inject D+ from the local source and had the D+ beam stored at various energies from 14:30 until 17:40. During the night from Wednesday (9 July) to Thursday (10 July) there was no beam.<br />
<br />
We then continued measurements with stored D+ On Thursday from ca. 11:00 to 21:00. Since then CRYRING is in shutdown."</em></p>
</blockquote>
<p> </p>
<p> </p>
<p><strong>---11 July---</strong></p>
<p><strong>08:07 CEST</strong></p>
<p>All checks OK.</p>
<p>Peak at 6 MeV did not re-appear overnight. Attached x2.</p>
<p><strong>12:00 CEST</strong></p>
<p>All checks good! All plots look good!</p>
<p><strong>16:00 CEST </strong></p>
<p>All checks okay! </p>
<p><strong>19:20 CEST</strong></p>
<p>All checks OK.</p>
<p>Background peaks almost visible.</p>
<p><strong>22:53 CEST</strong></p>
<p>All checks OK.</p>
<p> </p>
<p><strong>---12 July---</strong></p>
<p><strong>07:25 CEST</strong></p>
<p>All checks OK.</p>
<p><strong>10:00 CEST</strong></p>
<p>All checks OK. Temps attached.</p>
<p><strong>11:00 CEST</strong></p>
<p>All checks OK.</p>
<p><strong>19:00 CEST</strong></p>
<p>All checks OK.</p>
<p><strong>23:00 CEST</strong></p>
<p>All checks OK.</p>
<p> </p>
<p><strong>---13 July---</strong></p>
<p><strong>07:42 CEST</strong></p>
<p>All checks OK.</p>
<p><strong>11:00 CEST</strong></p>
<p>All checks OK.</p>
<p> </p>
<p>ELOG down during the afternoon</p>
<p> </p>
<p><strong>--14 July--</strong></p>
<p><strong>11:00 CEST</strong></p>
<p>All checks ok. </p>
<p><strong>14:40 CEST</strong></p>
<p>Tape service and merger now working on atppc025</p>
<p>All checks ok, briefly went no storage at around 14:38 CEST for 1-2 minutes whilst getting tape service and merger up. </p>
<p><strong>17:40 CEST</strong></p>
<p>All checks ok. </p>
<p><strong>21:30 CEST</strong><br />
All checks OK.</p>
<p><strong>23:16 CEST</strong></p>
<p>All checks OK. Several screenshots attached.</p>
<p>Calibration appears to hinders clear alpha peaks.</p>
<p> </p>
<p><strong>---15 July---</strong></p>
<p><strong>07:47 CEST</strong></p>
<p>All checks OK.</p>
<p><strong>11:55 CEST</strong></p>
<p>All checks ok. </p>
<p><strong>14:35 CEST</strong></p>
<p>Issue with atppc025, see attachment 29 for error message (desktop 2, detectors etc)</p>
<p>Got error to go, all checks ok. </p>
<p><strong>17:35 CEST</strong></p>
<p>Same issue with atppc025, otherwise all checks ok. </p>
<p><strong>20:30 CEST</strong><br />
All checks OK.</p>
<p><strong>23:07 CEST</strong></p>
<p>All checks OK</p>
<p> </p>
<p><strong>---16 July---</strong></p>
<p><strong>07:41 CEST</strong></p>
<p>All checks OK</p>
<p><strong>12:00 CEST</strong></p>
<p>All check ok. </p>
<p><strong>15:15 CEST</strong></p>
<p>Some fees have high rates, all other checks ok. </p>
<p><strong>15:32 CEST</strong></p>
<p>The above behaviour appears to be correlated with an increase in leakage current across all four detectors. Most likely light?</p>
<p>The background is not reliable -> No storage.</p>
<p>Unfortunately the leakage current logger crashed a few days ago on the server, and without anydesk we did not realise. Restarted it on atppc025.</p>
<p>Informed ML about issue. If it cannot be solved we could increase the thresholds and keep going, but the background may not be representative.</p>
<p><strong>16:35 CEST</strong></p>
<p>Issue persists. ML and ZA are not aware of any changes, except power-saving mode enabled for cave AC. No effect on FEE temperatures - not the issue.</p>
<p>aida04 rates shows 0. Checkloaded. Fine for a few seconds. Back to 0. Data event rate 100,000 may be too high.</p>
<p>Increased thresholds to 1 MeV. Data rates lowered, but e.g. on aida04 still 40,000. Goes back to zero. Checkloaded. OK for a short while, then back to zero.</p>
<p>Tape server stopped. DAQ stopped - all FEEs respond, good! Merger still going.</p>
<p>DSSDs off. Will retry tomorrow morning.</p>
<p><strong>23:44 CEST</strong></p>
<p>Temps OK.</p> |