update to sn triggering - indico-fnal (indico)• the easiest way is to start a screen / tmux/...
TRANSCRIPT
UPDATE TO SN TRIGGERING
Karl Warburton
Iowa State University
8th January 2018
1
NEW SAMPLES!
• Everyone should have received an email from myself on Christmas day / seen a Slack
message about new samples.
• 3 set of 1 million events – an event is a 2.5 ms (5000 tick) long continuous set of
detector readout. If the sample contains a MARLEY neutrino, it was generated at T=0 in
this window, though obviously hits produced at all times in the window.
• Has both TPC and PD readout.
• There are 3 samples (all with electronics noise “turned on”);
• Radiologicals only
• SN only
• Radiologicals + SN
2
HOW TO ACCESS THE FILES
• The samples are all uploaded to tape, so that we can access them forever.
• They are further defined collectively into a “dataset” containing ~10k files;
• snb_radio_dune10kt_1x2x6_snb_timedep_bkg_reco
• snb_timedep_dune10kt_1x2x6_snb_timedep_bkg_reco
• snb_timedep_radio_dune10kt_1x2x6_snb_timedep_bkg_reco
• Currently the files are still in the /pnfs/scratch/ locations which they were generated in;
• /pnfs/dune/scratch/dunepro/MCC10-Production/SuperNovaSamples/v06_60_00/reco/*/files.list to get the
locations of all of the files – feed this into a job to run over all files.
• Eventually these files will get deleted and then we will have to pull the files off tape.
• DO NOT RUN OVER THE DATASET WITHOUT FIRST PULLING FILES OFF TAPE. I CANNOT STRESS
THIS ENOUGH. You WILL get angry emails from many SCD people about wasting resources.
• We will have to pull files off tape after we don’t use the ones in scratch for ~1 month.
3
HOW TO PULL FILES OFF TAPE
• The easiest way is to start a screen / tmux / whatever session on a terminal and simply type either one
of the following;
• samweb run-project –defname=<defname> --parallel 4
• samweb prestage-dataset --defname=<defname> --parallel 4
• The top is what I use in NOvA, the bottom is something I was told by Tingjun. They are functionally equivalent.
• If you really want to run on a single file locally;
• samweb list-definition-files $dataset # (show the files in a dataset)
• samweb get-file-access-url $filename # (Get a SAM URL for a file)
• ifdh cp -D $url $directory # (Copy that file back)
• There is no reason why you can’t just prestage a single file though, especially because I’ve made
defintions for you;
• `<def>_1k_events` # First 10 files
• `<def>_10k_events` # First 100 files
• `<def>_100kevents` # First 1000 files
4
RUNNING OVER THE DATASET
• Continuing on previous work I’ve shown I ran over the whole dataset to improve stats.
• Also added some histograms to see the properties of the “primary electron” assumed to
be the first electron in the MCParticle cascade from the interaction.
• I’m about 99% sure this will be true for all SN interactions.
• It is the longest electron in ~95% of the SN interactions (from very unsceintific flipping through
of output).
• In the samples produced there are hits calculated using “FastHit” at thresholds of 10, 15,
20, 25, 30.
• Have worked out the spread in time, spread in channels, number of hits, summed ADC for
both all MARLEY hits, and only the primary electron.
5
HIT THRESH OF 10 ADC – ALL MARLEY HITS
6
HIT THRESH OF 10 ADC – PRIM E HITS ONLY
• Can see that all distributions are much
more localised (Time vs Chan) and
linear (Nhit vs Chan).
7
HIT THRESH OF 30 ADC – ALL MARLEY HITS
8
HIT THRESH OF 30 ADC – PRIM E HITS ONLY
• Again, highly localised.
• Can see that there isn’t a tremendous
difference between the 10 and 30 ADC
threshold, so hopefully don’t lose too
much efficiency in having a high threshold,
but will reduce background.
9
SUMMARY
• Obviously have the analogous plots for
thresholds of 15, 20, 25 ADC.
• Have span up a small run where I tried to
see the whether the MARLEY hits would
fall into some clustering windows.
• Will have this ready – plus a plotting
macro so that I can “plot dump” better
soon.
10
• In the image, the first number is the time range, and the second number
is the channel range – 0 represents all channels/time.
• These are hand-selected from trying to contain a majority of the Prim
El points – will see how well they work next week…
BACKUPS
11
WHAT IS THE FAST HIT FINDER?
• Developed for the 35 ton – thanks to T. Blackburn, A. Booth, M. Stancari!
• Was initially designed for quickly looking at collection plane signals, but proved very helpful in
calculating signal/noise ratios.
• For collection planes it looks for two hits above a threshold. Calls this the time of the hit, and moves on.
Doesn’t work out hit width / hit integral.
• For induction planes it looks for the “crossing point” (where ADC is 0) and calls that the time of the hit.
Again, doesn’t work out hit width / hit integral.
• At the collaboration meeting there was feedback about ways to improve this to make it more
of a rolling sum from 0 in an effort to increase the sensitivity to some of the low charge hits.
• I still haven’t look at this, though Michelle is thinking of doing this so I will act as a minor partner in this.
• Tyler has made some improvements, but yet to make it into develop I believe.
12