E front 2x16-way to 1x34-way IDC cable from the Junction Box to the IDC-Lemo 00 adaptor was found to be inserted upside-down - the 16-way IDC connectors did not have polarisation keys - meaning the E detector p+n junction strip signals collected with 26Al for the first night are not working. Signals from the dE p+n junction strips and E n+n Ohmic strips will be OK. The mistake occurred at the conclusion of the noise tests yesterday - see https://elog.ph.ed.ac.uk/nToF/52

The 2x16-way to 1x34-way IDC cable without polarisation keys has now been replaced.

Run 216417 and onwards have correct cabling. For runs before that, E back and dE are still reliable.

After inserting aluminium target, previously-dead channel 24 on EDET was re-plugged into a 12-bit card SPD02872. It is the only EDET on 12-bit card, the rest are on 14-bit. From pulsers, there appears to be a 90 ns offset from this EDET to others, with EDET24 preceeding the rest. The last channel on 14-bit cards was broken, hence havng to use 12-bit.

Here is a Google spreadsheet for counting protons for the runs:

https://docs.google.com/spreadsheets/d/1INX8G9GAu-M70SdZdz55qXnMZNXKXLW7xfFH-eaLuQw/edit?usp=sharing

To run raw2root on LXPLUS, you will need to add the following line to your .bashrc, performed using

then paste line at the bottome of the file

then save and close the gedit (a linux text editor similar to Windows Notepad). Text file .bashrc is responsible for setting correct paths to various system settings when you log in. The line above sets correct libraries for raw2root from the n_TOF official directories.

The old version of raw2root which I use is stored in a directory on EOS accessible via LXPLUS:

If you examine the contents of the directory using command ls, there will be two folders: ntoflib and prg. The relative location of these folders on your system should always be the same, and you do not need to do anything in the ntoflib directory, so we can explore the next directory

Command cd means change directory and ls is list contents, double-& chains commands in a sequence. Your terminal should now display two more directories: detector and raw2root. detector is a list of codes for various detector types, examine its contents with ls detector. We use MWDdetector.cc and its library header file MWDdetector.h. All the filters are defined and can be changed in MWDdetector.cc, which is a C++ code. You can browse and change its contents with gedit. raw2root codes, however, are run from the raw2root directory, so let's change to it

When you list the contents of this directory there will be many files, none of which you need to edit. There will also be a directory called Traces, which I created as the default location for signal traces to be written, if relevant sections of MWDdetector.cc are uncommented (discussed below). If you are happy with the contents of MWDdetector.cc, you need to re-compile raw2root. Using C++ code, unlike some others, is a two-step process: compilation and execution. Various bits of code in raw2root and its libraries are put together into one executable file called raw2root during compilation stage, and then the code can be run by executing the executable. To compile raw2root, you need to be in its directory, which you can check by typing in

which should then display /eos/home-n/nsosnin/public/raw2root/prg/raw2root and if you it displays something else, use

To compile raw2root in this directory use

The code will start compiling and do so for a while. It will display some warnings associated with other older n_TOF codes. There should, however, be no errors. If there are errors, something went wrong in MWDdetector.cc, so try troubleshooting it by Googling the errors (the line with the error will also display two numbers, something like error: MWDdetector.cc:1211:45, and the the second number is the line where the problem occurred). C++ errors are a dark art though, so feel free to contact me for help.

If the compilation displays no errors (woo!), the code compiled successfully. To test it, two things are needed: UserInput file and .raw.finished file. UserInput file called UserInput_Silicons.h, which I use, is already stored in that directory. If you examine it with gedit, you will see lines with detector names and numbers and the filtering parameters. The parameters are read in at the top of MWDdetector.cc in order, so you can follow the variables they are read into throughout the code to figure out which parameter does what (this is not an easy task!).

.raw.finished files are binary data files with detector signal traces, which raw2root filters and makes into ROOT files. These need to be downloaded from CERN servers (I left two example ones in the directory though). While the experiment is running these are stored, but will eventually be deleted, so if they don't download, contact me on staging data (i.e. writing it onto servers again after deletion). To download such a binary file for this experiment to the directory you are in use

Here, xrdcp command is CERN's own copying command, which takes data from the directory listed in the command. I have highlighted above in yellow the bits you may need to change in the command. The first two are simply run number. The last one is the data segment. n_TOF data within a run are subdivided into 20 proton bunch segments, so one such .raw.finished file that you download contains 20 bunches (which is a very small amount of data, so if you need mass_processing, contact me or Fran (francisco.garcia.infantes@cern.ch) at n_TOF). You can download different segments by changing this number. Bunches 1-20 are in segment 0, bunches 21-40 in segment 1, etc.

Once you have downloaded the file of interest execute raw2root with command

This will run for some time, applying settings from UserInput to filters in MWDdetector.cc, and running the filters over data in the .raw.finished file. This will produce an output file called rootout.root, but feel free to change the name in the command to whatever you like, otherwise you will just keep overwriting the old files. This output file will have the amplitudes, times etc. of all the extracted signals listed, but it will not produce traces, as that is not standard raw2root functionality, and requires my code, which I added to MWDdetector.cc

To print traces, open MWDdetector.cc using

Note, ".." on Linux means "previous directory", so the command above will leave raw2root directory, go to detector directory and open the code. In this code, uncomment (i.e. remove // or /* or */ characters in C++) from lines 310-312, 441, 442, 465 and 529. This will now print trace ROOT files into the Traces directory. Warning: this runs very slowly, as it's a lot of data being written to disk!

The if() statment on line 465 allows you to gate on specific bunches and detectors for producing traces. The contents of histograms inside the output files can be understood in terms of what MWDdetector.cc does by reading the lines 514-522 of that code. This should be everything you need to get started with processing traces and filtering outputs. Good luck!

Detectors currently in the boxes:

2x MSL type W1(SS)-50, 2902-4 (53um), 2940-6 (55um)

1x MSL type W1(SS)-20 2837-33 (20um)

1x MSL type W1(DS?) 1230-10  (500 or 300 um)

1x MSL type W1(DS)-500 1194-9 (494um)

Three aluminium crates contain 26Al(n, alpha) kit from EAR2, and was in the barracks (building 6547) near detector lab by EAR1 entrance. A list is attached and photos can be found on Dropbox:

https://www.dropbox.com/sh/68k1xove2zr1bmj/AADKvN8wR_Ia2EwZMOXZqdMCa?dl=0

We borrowed from n_TOF:

1x O-ring for circular side-flanges on the chamber (the borrowed part has a small green marker cross on it)

10x LIMO-to-BNC connectors (BNC female) from electronics lab outside EAR1

I'm attaching a report for the experimental setup so far.

There is a main problem which haven't been solved yet and I don't know if that can cause problem in the future analysis.

Channels #23, #24, #31 and #32 are not working well. The signal os these channels look attenuated from the pulser, make impossible to see then in the Boron run.

As these channels are in the back side of the detector, it could be possible to run like? Unless we have more ideas about to solve the problem.

The front channels work well all of them, and the rest of the back channels work well as well.

I attach the current for the +15 and -15 volt applied to the PreAmp (low voltage) and the leakage current from the detector is 0.1 uA.

Box 1

1. RC412 Cables

2. Screws and parts for rails

3. Small rails

Box 2

1. Vacuum valves

2. IDC cables

Box 3 (Detectors)

1. WI-20

3186-9

2. WI-150

3458-4

3. WI-150

3458-1

Box 4 (Detector)

1. WI-20

3485-12

*List

**We also have the tube for the long rails

Dear all,

There was an issue with one of the strips of the deltaE detector (DEED 14), for run216644. The gain dropped to almost a factor of 3. Find attached.

Somehow, it was fixed, but still lags, when compared to other strips of deltaE. This was tested for a more recent run, run216651. Find attached.

I also checked a bit older run (run216637) and they look similar.. Find attached. Maybe we should figure out if this will be a problem for the DEED14 strips.

NOTE: The plots have the run number at the top-center.

Emmanuel Odusina

We switched from Aluminium target to Boron Target (number 1) on Tuesday (26th of Sept.). The Aluminium target was placed in the material room by the RP. We will change to LiF (number 3) on Thursday (28th of Sept.)

We switched from 10B target (number 1) to LiF target (number 3). We planned to take this measurement for one day.

An empty frame (on the top) was placed on Friday night.

MWDdetector and UserInput

Attached is the B10 and LiF data with Fast Fourier Transform and varying time constants.

We observed that DEED11 no longer have Gamma flash signals.

Before the drop, it had some weird flunctuations.

Attached are the plots.

We will check with the pulser tomorrow.

We checked DEED 11 with the Pulser and it was still unresponsive (See screenshot).

Next, we will change the LEMO cables and do another Pulser Test.

10 new Adapters for lemo to bnc on my desk