[Halld-tracking-hw] [New Logentry] Follow-up Re: Follow-up Re: FDC occupancy from rootspy

[davidl at jlab.org]

Logentry Text:
--
There appears to be two separate problems here. One with FDC wires and another with FDC Cathode strips.

Using plot browser, I took a look at this run (40654) for two views of the FDC occupancy. The first two figures below were produced for runs 40654 and 40659 respectively by RootSpy online. It is in agreement with Lubomir's findings that there are no large holes in the FDC Cathode occupancy like those seen e.g. in run 40659 (second figure).

[figure:1][figure:2]

The plot for run 40654 above shows inefficiencies in some of the FDC wires, consistent with Lubomir's findings. (n.b., theses inefficiencies disappear in run 40659). A plot of the "FDC Package 3 Occupancy" (not available in RootSpy online, but from the incoming data version in plot browser) is shown below also for run 40654. Those plots are made using the DFDCPseudo objects which require coincidence between the wire and both cathode planes. The dead regions correspond to the "inefficient" regions for the wires in Lubomir's analysis. (See below)

[figure:3]

Below is a copy of the FDC wire occupancy for package 3, cells 4-6 from Lubomir's analysis of run 40654. These should be compared directly to the bottom three plots of the above figure. Note that sections where the central peak is below 30k in Lubomir's plots correspond to holes in the DFDCPseudo plots above. For example, in package 3 cell 6 , both halves peak at about 23k and both show up as inefficient in the above plot. It would be easy to mistake the wire occupancy for this cell as OK since visually it looks similar to other cells that actually are OK.

[figure:4]


The configuration parameters for the FDC were compared between runs 40654 and 40660 (similar to 40659). The following observations were made:

1. The CODA configuration was different. Run 40654 used "hd_all.tsg" while run 40660 used run "hd_all.tsg_2ER_8DC". The latter was a configuration used for DAQ testing. It turns out that this or similar DAQ testing configurations were used for runs 40649-40651, 40653-40655 and runs 40688-40693. All of these showed no issues with the FDC cathode hit occupancy.   All cases where holes in the FDC occupancy were observed used the "hd_all.tsg" configuration.

2. The issue with FDC cathode holes did not depend on whether long mode or short mode data was being read out.  Both runs with long mode and runs with short mode were taken for both types of CODA configurations and the issue always followed the CODA configuration only.

3. The f125 configuration parameters themselves do not appear to have changed. Below is an edited list of the files archived to tape along with the raw EVIO data for run 40654. A recursive diff on the entire directory tree (which includes file contents) showed no differences in any of the parameters used to set the thresholds or pedestal offsets for the FDC.

Run040654/RunLog040654
|-- current_run.log
|-- FCAL_BCAL_PS_m10.conf
|-- FDC
|   `-- COM
|       |-- roccdc1_fadc125_fall2017B.cnf
|       |-- roccdc2_fadc125_fall2017B.cnf
|       |-- roccdc3_fadc125_fall2017B.cnf
|       |-- roccdc4_fadc125_fall2017B.cnf
|       |-- rocfdc10_fadc125_fall2017B.cnf
|       |-- rocfdc11_fadc125_fall2017B.cnf
|       |-- rocfdc12_fadc125_fall2017B.cnf
|       |-- rocfdc2_fadc125_fall2017B.cnf
|       |-- rocfdc3_fadc125_fall2017B.cnf
|       |-- rocfdc5_fadc125_fall2017B.cnf
|       |-- rocfdc6_fadc125_fall2017B.cnf
|       |-- rocfdc7_fadc125_fall2017B.cnf
|       |-- rocfdc8_fadc125_fall2017B.cnf
|       `-- rocfdc9_fadc125_fall2017B.cnf
|-- hd_all.tsg_2ER_8DC.log
|-- hosts
|-- rcm_run.conf
|-- run_040654_comments.txt
|-- run_040654_info.txt
|-- run_conditions040654.dat


On a side note, it appears only the f250 module parameters are making it into the RCDB archive. We are working to address this issue for future runs.



---

This is a plain text email for clients that cannot display HTML.  The full logentry can be found online at https://logbooks.jlab.org/entry/3508178
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-tracking-hw/attachments/20171222/93b1a54e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FDC_occupancy_rootspy40654.png
Type: image/png
Size: 23561 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/halld-tracking-hw/attachments/20171222/93b1a54e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FDC_pseudo_incomingdata40654.png
Type: image/png
Size: 51148 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/halld-tracking-hw/attachments/20171222/93b1a54e/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FDC_occupancy_rootspy40659.png
Type: image/png
Size: 22577 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/halld-tracking-hw/attachments/20171222/93b1a54e/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: FDC3_cell4_6_40654.png
Type: image/png
Size: 10469 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/halld-tracking-hw/attachments/20171222/93b1a54e/attachment-0007.png>