NP04 Photon Detection System

Overview of NP04 hardware and software

Thanks to Chris, a nice summary is in pDUNE_PD_System_Integration_Info_Nov2018.pdf

SSP Basic Info Twiki Page: Click HERE

DAQ-PD_Runs-ProtoDUNE: Click HERE

Lists of good beam runs and reconstructed events

A list of good beam runs can be found here: https://docs.google.com/spreadsheets/d/1hD2hb_haSmXRfChmfsfnnAcnhFJMeZdrMydWdRMLVGI/edit#gid=1802640520

Some of them have been fully reconstructed for what concerns the TPC data.

A list can be found from

http://dune-data.fnal.gov/data/protodune-sp/index.html first row in the table refers to fully reconstructed events.

There exists also a LArSoft display that shows reconstructed tracks in human readable coordinates. Instructions can be found in this nice tutorial

Protodune-SP Run Summaries

Leon Ran larsoft jobs analyzing over 200 runs and produced N-tuples https://home.fnal.gov/~mualem/protodunesp/runsummaries/

Description in 2019_01_10_Protodune_Summaries.pdf

After Beam runs and calibrations

A list of after-beam runs is maintained here: https://docs.google.com/spreadsheets/d/1gPqQbPFoOZjDLPfPVHBfCrZz9g0IQoqWUUhFnKVx6aQ/edit#gid=0

DCS calibrations are regularly (more or less regularly) performed. The lists of runs are in ListOfCalibrations

PD System Future Run Request

Link can be found here: https://docs.google.com/spreadsheets/d/1Wrbo0-DLiKRtKgW4N8wxsgImX2qjeN4P9b_VQLijeJw/edit?usp=sharing

The requests presented at the DUNE collab meeting Jan 2019 are here. Expected run time from March 18th to April 7th

Telescope runs

Description of setup in these slides List of runs in the second sheet of sheet 2

Taking Data at NP04

Taking DCM Data

Make sure to EXCLUDE CRT and trigger components in the Run Control, but KEEP the timing component

Current configuration file being used: calib_DCM_XenonDoping_00001 - This has ONLY SSP external trigger


Controlling the DCM configurations

Go to server np04daq@np04-srv-012

source /nfs/sw/work_dirs/sspQuery/setup.sh

cd /nfs/sw/work_dirs/sspQuery/

There is a new easy-function to run DCM configruations -> runDCM_Num_Pos_PH_Width

Please enter: dcm (1/2/both), position (UL/UR/LL/LR/Cen/ALL), Peak Height (FFF/3D2/etc..), Bin Width (9/F/20), using a space as the delimiter.

For Example, to run DCM1, with upper-left diffuser, FFF peak height, and a bin width of 9, type:

runDCM_Num_Pos_PH_Width 1 UL FFF 9

For an Xenon Run Example, run both DCMs, with ALL LEDs, 577 peak height, and a bin width of 9:

runDCM_Num_Pos_PH_Width both ALL 577 9

Every time you use this function, it will first turn Both DCMs off, wait 10 seconds, and set the specified DCM configurations.

Note: You can also run both DCMs with the function by typing both, instead of 1 & 2.

When doing SiPM bias scan, use the script run_dcms_pulse_range.sh . This automatically changes DCM intensity during a run

Comments: These are functions that were made with pre-set configuration files, therefore not all configurations may work. However, it will notify you if there is no configuration file available and ask you to seek an expert for help.


Taking CRT Data

Make sure to include CRT and trigger components in the Run Control

For "normal" CRT trigger runs, use config np04_CRT_noprescale_00005 - This has SSP internal & external triggers.

For ONLY SSP external trigger, use configuration PD_CRTnTelescope_trigger_00001


Taking Telescope Data

Make sure to EXCLUDE CRT components in the Run Control, but keep the trigger component included

For "normal" telescope runs, use configuration np04_PM_noprescale_00001 This has SSP internal & external triggers.

For ONLY SSP external trigger, use configuration PD_telescope_00001


Modifying SSP parameters

Need to make a new DAQ configuration file- follow instructions here: Click HERE
Setting SSP triggering

Trigger on SSP External + Internal triggers.

Set ALL_channel_control: 0x00000401 in the ssp_standard.fcl file.

This results in a 1:1 Global trigger to SSP 2000 sample output + 1:(0-N) 2000 sample outputs, depending each channel's threshold. This is used for when you'd like to trigger before and after the global trigger. An example where we use this is for a main physics run, where we care about the light yield - 0.5ms before a physics event and +2.5ms after said event.

Trigger on ONLY SSP External triggers

Set ALL_channel_control: 0x1 in the ssp_standard.fcl file.

This results in a 1:1 Global trigger to SSP 2000 sample output- NO threshold set. This is used for runs where you only need to look at SSP information for the first 13us of the global trigger. An example where we use this is for a Calibration run.


Setting Individual SSP thresholds

First, go to the individual SSP fcl file. Example: ssp504_hw_cfg.fcl

Set all 12 SSP channels using daq.fragment_receiver.HardwareConfig.ARR_led_threshold:

One example is daq.fragment_receiver.HardwareConfig.ARR_led_threshold: [300, 300, 300, 300, 300, 300, 300, 300, 200, 200, 200, 200]

================================================

-Updated by Chris Macias 2019-03-28

-- PaolaSala - 2018-12-12

Topic attachments
I Attachment History Action Size Date Who Comment
PDFpdf MarchApril2019_PD-PDUNE_update_Macias.pdf r1 manage 3895.1 K 2019-05-08 - 17:26 PaolaSala  
PDFpdf lhw_CERNLArSoft.pdf r1 manage 5998.7 K 2018-12-14 - 15:01 PaolaSala Short LArSoft reco tutorial
Edit | Attach | Watch | Print version | History: r20 < r19 < r18 < r17 < r16 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r20 - 2020-02-11 - ChristopherThomasMacias
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CENF All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback