Daily Reports¶

run plan document on [[https://docs.google.com/document/d/1Bmag_YPrl1szxLhYyA4eLUP2PV_pM0x51pHbeCj2hL4/edit?usp=sharing]]

daily report 1/16/2021 -- by Jixie

daily report 1/16/2021 -- by Jixie

daily report 1/16/2021 -- by Jixie

daily report 1/16/2021 -- by Jixie

1. Beam energy scan was finished, HV
2. Took 1 GeV data using 8GeV HV setting. Since detector is not saturated, do not bother to change it. #

daily report 1/15/2021 -- by Xiaochao from far away

1. good gracious, we keep getting 24 hours a day
2. we should keep our dialy work hours below 16 and stretch shifts to 8 hours
3. rate scan is done up to 12 GeV energy. And we are now taking 1 GeV data
4. the trigger is from FTBF's 3 scintillator paddles coincidence with the spill signal. FTBF's 2-chamber Cherenkov signals are not in the trigger but are in our FADCs.
5. MWPC has problems: 1 was fixed today (hardware) and both are working and online, daq is working and synced with our daq. But the software is missing a library so we can't decode the data.
6. According to David's post on Slack:

David Flay 2:20 PM
ok, using the rates above, I find for our remaining 11 days:
2:20
E = 12.0 GeV, numShifts = 1.3, totEvt = 16356343
E = 10.0 GeV, numShifts = 0.8, totEvt = 16356343
E = 8.0 GeV, numShifts = 0.7, totEvt = 16356343
E = 6.0 GeV, numShifts = 0.8, totEvt = 16356343
E = 1.0 GeV, numShifts = 14.7, totEvt = 16356343
E = 2.0 GeV, numShifts = 2.5, totEvt = 16356343
E = 4.0 GeV, numShifts = 1.2, totEvt = 16356343
2:21
clearly that 14.7 shifts doesn’t make sense.
David Flay 2:27 PM
I think it checks out;
2:27
Total time: 264.0 hrs
E = 12.0 GeV, weight = 0.061, time = 16.1 hrs, numShifts = 1.3, totEvt = 16356343
E = 10.0 GeV, weight = 0.038, time = 10.0 hrs, numShifts = 0.8, totEvt = 16356343
E = 8.0 GeV, weight = 0.032, time = 8.5 hrs, numShifts = 0.7, totEvt = 16356343
E = 6.0 GeV, weight = 0.038, time = 9.9 hrs, numShifts = 0.8, totEvt = 16356343
E = 1.0 GeV, weight = 0.666, time = 175.9 hrs, numShifts = 14.7, totEvt = 16356343
E = 2.0 GeV, weight = 0.112, time = 29.5 hrs, numShifts = 2.5, totEvt = 16356343
E = 4.0 GeV, weight = 0.053, time = 14.0 hrs, numShifts = 1.2, totEvt = 16356343
Totals:
Time = 264.0 hrs
Shifts = 22.0

daily report 1/14/2021 -- by Xiaochao from far away

1. beam started sometime in the evening.
2. we got the night time beam as a bonus - the other group does not need it - causing us to scramble the shift schedule. Paul Reimer came in for the night shift, until 3am - thanks!
3. by midnight, we are sending beam to center of each block, trying to adjust HV/gain-match;
4. Jixie adjusted Cherenkov pressure around 10pm. Previously the two chambers were set at 4.0 and 0.2 psia, respectively. I think Jixie lowered one of them from 4.0 to ???

To do:

1. complete gain/HV-matching of the 3 shashlyk modules
2. center beam at the middle of the 3-block (a little off-center may be ideal, better than at the exact center) and do energy scan over night to figure out rates
3. David will rework the runplan during the day
4. One of the MWPC is broken, will be installed during the day

Jixie 9:04 PM
daily report 1/13/2021
A busy and tired day! At least our DAQ is ready to take beam with our own trigger!

1. Start installation from 7AM. Finished installing detectors and cabling by 1PM
2. Put the rack in the control room so no access needed for daq work. Our daq machines are also in the control room.
3. David came to site. Help a lot in setting up computers. Xinzhan and I are working on detectors and daq cabling. Both desktops are online. CODA runs well.
4. Operational Readiness Clearance (ORC) meeting started from 1 PM. Detectors are all good. However, JLab made VME cards were suggested to change fuse at the beginning...... After some long negotiation, we were requested to put kapton tape to cover the power interface. We also received some suggestions to run the experiment safely. We might get all signature by tomorrow
5. We connected HV and signal cables to the patch panel. All PMT signals have been checked using an oscilloscope. All detectors work well. We do not have enough time to modify daq to take the FTBF trigger. FTBF has 3 channels for Cherenkov, none of them add into our FADC yet. (Need to find cable and do fan in fan out...) MWPC daq does not have a veto input, it can not take our busy status immediately. We have to form a new trigger then feed it. We will do this in the morning of Thursday.
6. Accelerator is down. One magnet is not functioning. They are waiting for the radiation to cool down so they can fix it tomorrow morning. Beam might be available in the afternoon.

To do:

1. Do FTBF controlled access leader training in Thursday morning 9AM
2. MWPC daq is a well integrated machine (looks like a laptop). It does not provide L1A signal. We need to learn deep about this system to find out a possible way to take thrit L1A. We will then veto it using out busy status. Need to spend time here Thursday.
3. connect cherenkov into our FADC.

Pictures under useful pictures with prefix 20200113_xx

Jixie 8:02 PM daily update 1/12/2021

1. Took radiation practical training, both of Jixie and Xinzhan
2. Met Lorenzo, have a long and deep conversation with him. He helped us setting up the gateway machine, which is soliddaq. Right now solidaq has 2 network interfaces, one of them is borrowed from FTBF. soliddaq can access the public network, it also serves as the gateway of the private network. Because IP forward function is not enabled, right now private network members can not access public networks yet. (I need help from an expert to enable this.)
3. If you want to access to clrlpc, you have to access to solidaq using fermilab linux account, then ssh from soliddaq into clrlpc using a-compton account. If you want to do that, send me your fermilab username. I can add your username into the name lists that allows you to login soliddaq using a-compton account.
4. David brought the hard drive and pcie to usb3.1 convert card here. Two 5T hard drive (2.5") were installed into the usb hub provided by Alex. Tested the data transfer speed. It can reach 130MB/s when the CPU is idle. Data transfer speed changes a lot when coda is running.
5. JLab experts are working on DSC issues. The Fan-In-Fan-out module degrades the input signal too much, which is part of the reason that DSC lost signal. We borrowed one from FTBF. JLab experts are also checking and fixing the software. Right now we can see TDC in the output file. Alex is still working on it to make sure it does not lose data.
6. David is working on ORC form.

Here is how we transfer data back to jlab:

1. make a copy of data into soliddaq, this copy will also be our backup of all raw data
2. sent data from soliddaq to jlab

To Do:

1. The beam will be off by 6AM Wednesday. We will start installation from 7 AM. We aim to finish cabling and installation by 1 PM.
2. ROC inspection is scheduled at 1 PM Wednesday. I will show in person. David will join remotely.
3. The beam is scheduled to be delivered by 5:30 PM. Look forward to taking beam! (edited)

Jixie 9:03 PM daily report, 1/11/2021

1. Put all our computers into a private network switch, use ip 192.168.1.x, reserve IP 192.168.1.1 for the gateway. All computers can talk to each other. Still waiting for FTBF to provide a gateway. Talked to Evan and Lorenzo. They understanded our request and will set up one tomorrow.
2. Rebooted vme crate.. The hostname 'intelvmeha8' came back. Start and stop coda smoothly, no need to manually start ROC2.
3. DSC did not write data to the output file. Experts at Jlab are working on this.
4. Talked to Evan about MWPC daq. Learned that we can easily take their trigger, which is SC1&SC2 (both stay at FTBF beam line). We decided to take the L1A signal from MWPC daq to be our trigger. In this way the events from our daq are already synchronized with MWPC daq. We will also put our SCs into the FADC, they just do not serve as triggers anymore. We will also plug Cherenkov signal into our FADC. We will also put a copy of MWPC daq's L1A into our TDC.
5. David is preparing the ORC document
6. Had a meeting with Lorenzo, we agreed to start shift at 8 AM|PM.
7. install kerberos kit in clrlpc. We will not use it during data taking but can use it if needed. Only people with a Fermilab linux account can access it.
8. taped the lead block.

_ To Do:_

1. get a gateway
2. solve DSC
3. look at raw data file of MWPC daq, try to understand their daq

Jixie 10:15 PM daily report 1/10/2021

1. pause daq data taking to test 3 preshowers. They are all good
2. continued testing TDC configuration. Looked at TDC signal in raw data file. improving/updating coda and decode program under the guidance of Alex.
3. taking cosmic data. right now daq machine clrlpc is offline

To Do:

1. finish setting up private network
2. tape the lead block
3. practice sending data back to jlab
4. take training on Tuesday

Jixie 6:59 PM daily report 1/9/2021

1. Finished installing kerberos kit into soliddaq desktop (the backup one)
2. zoom meeting with Alex, we are now able to run coda only if we do not follow Fermilab kerberos ssh requirements. A trick is that we used jlab configuration to start coda and all rocs, when coda runs we switch to fermilab configuration. This is not a solution! We have to put daq into a private network.
3. Found a 1000Mbps switch and several cat5e cables. Cat5e cable's speed can reach 1000 Mbps, while cat6's is 10Gbps. Will be better if there are enough cat6 cables. Plug 2 laptops into the switch, manually specify IP and gateway, 2 laptops can talk to each other. I tried to set up my laptop (windows10) as the gateway and using WIFI to connect to the fermilab public network. Failed!

Our solution will be: soliddaq, clrlpc, intelvmeha8 will be in a private network.

• Ask Fermilab to provide a gateway. (The backup daq machine must be identical to the main daq machine.
• To transfer data to JLab, I will send data using the backup daq to Jlab work disk.
• Alex, please help me to find out which disk I can write raw data to, total space no more than 14T.

To Do:

1. Request FTBF to provide a gateway, finish setting up the private network
2. CODA roc2 need to be start manually, need to fix that
3. work out a script to transfer data
4. waiting for HA approval then tape the lead
5. test preshowers when a 2nd HV module is available. (edited)

Jixie 10:22 PM daily update 1/8/2021

1. both desktops got blocked because password authority is not allowed. Solved it after reconfigured sshd_config file.
2. applied host principles for both desktops. Got password in the afternoon but have typed a wrong host name for the main daq machine. Reapplied and now waiting for supervisor's approval. The backup machine (soliddaq) is ready to install kerberos kit but do not have time to do it.
3. connected daq system. hooked SCs and Ecals into daq. viewed trigger signals. ready to take cosmic data. Preshowers are not connected yet.
4. hooked vme directly to clrlpc, configured them to talk to each other. 2 machines can talk now.
5. Alex helped thought zoom meeting. After some modifications, Alex can run coda to take events. But I could not run it by myself because some configuration changes that Alex did might not be saved.
6. Paul came to help. We are trying to solve the network issue. Desktop clrlpc has a puppet service to overwrite sshd_config frequently. Therefore all my modifications is gone. We have to solve it ASAP otherwise this machine will be blocked again once the Fermilab robot catches it.
   Service puppet was temporary disabled.
7. Rearranged detectors such that 2 SCs and Ecals are in the same line.
8. My laptop got blocked due to use X11 service......

To Do:

1. Install kerberos kit
2. configure coda
3. test preshowers
4. tape the lead plate (edited)

Jixie 8:42 PM daily report 1/7/2021

1. installed both the nim and the vme crates onto a movable rack
2. learned how to use FTBF's HV module. This module can only supply HV in range from the set point subtract 580V to the set point. For example, If a set point is 2500V, the HV range is 1920-2500. In our case, we need to set ecal at 900V, SC at 1300V, and preshowers at 2100V. We have to use two HV module.
3. We look at the signals for all 3 ecal and 2 SC. We didn't damage them during the bumpy driving. The signals looks good.
4. We installed 3 ecal modules into the tray. Carefully addjust their positions to make sure them attach to each other tightly.
5. registered both desktops, clrlpc and soliddaq, to Fermilab public network. The latter is a back up for daq machine. Both of them are now online. If you have a computer account of Fermilab, you can ssh to it using account a-compton.

To do:

1. test preshower detectors
2. applying a computer account so I can access daq machine from apartment
3. connect daq system to detectors
4. tape the lead plate after HA got approved (edited)