Embedded Files
HONR269L
02/13/2020
- So far we have had two meetings with Prof. Bhatti, one on 02/05 and one on 02/12
- meeting 02/05:
1) understand the goal of the project:
2) get an account on the CMS Tier-3 cluster
3) begin running ROOT for data analysis
4) read through the LZ paper and begin to understand the theory and the function of the detector
-meeting 02/12:
1) talk about the detector in greater depth, while going into detail on the physics of WIMP detection
2) discuss files for ROOT analysis and what is contained in the files
3) task assigned - go through the files and work on understanding what is in the code
02/19/2020
- New task assigned - make plots with the data from given files
This week has been mainly dedicated to accomplishing that task - so far we have run into a roadblock as there are thousands of files in the directory and we are unclear as to which files are most useful/which ones should be used to plot.
02/26/2020
This week has been mostly spent trying to re-create this graph from the LZ paper.
the graph shows the behavior of H3 decaying through electron recoil (ER) in blue and potential WIMP interactions through nuclear recoil (NR) in red. Our goal this week was to take the ER and NR data that we already had and create this graph using the code given to us as a model.
We had more difficulty with this than we expected - the code was beyond our familiarity and we kept getting hung up on variable names - I was concerned with understanding the physics behind them and missing the more obvious solution (running the code blindly).
After the meeting today, we were able to create a graph closer to the one above, but are still falling short - we are able to plot the scattering of the simulated WIMP interactions, but we have not yet figured out how to overlay the gaussian/quantiles and change them from NR to ER.
This week our goal is to figure that out and continue from there.
03/01/2020
The past few days have been dedicated to A) correcting mistakes in the code caused from our first attempts at graphing, B) getting the same graphs on everyone's computers, and C) producing the graph from last week.
work Sunday 03/01/2020
- attempting to read the WIMP data instead of the H3 data
- changed the path name in the V2.cc file to /WIMP/20200204 (two lines)
- changed the path name in the V2.cc file to /WIMP/ in a line above that
- changed some data around line 641 to logs2Area (the original lines should be commented next to it)
- changed the axes in the make plots file for C25 (y axis, original lines are commented next to it)
- ran the .C file, then ran the make plots file but there's now no data appearing at all - something isn't reading the WIMP data
- root throws an error when running the .C file that says H3_DataRQ() function not found - why?
-changed three path names to data2 instead of data -> data appeared
^ above: the graph we currently have, with nuclear recoil simulated scattering data. The quantile lines are being calculated incorrectly- whether they're carrying over from the electron recoil data or if they're on the wrong scale, not entirely clear. Also, I need to add axis titles
NEXT STEP -
a) fix the quantile lines
- so far, we've found where they are created, but they reference some variables that we may not be able to understand - looking further into it but i suspect we'll have to ask about those
b) (should be more doable) put the data from the nuclear and electron recoil on the same graph
- i'm running into a roadblock with C++ and ROOT syntax - I need to spend more time familiarizing myself with the syntax
- so far I've gone through the plotting block and commented the code
- ideas for how to move forward:
- we have three relevant files - 1) a .C file that runs a specified number of events (so far i've run 100,000) and compiles 2) a DataRQ_V2.cc file that performs the data analysis and creates a .root file of histograms, and 3) a make plots .cc file that reads the .root file and creates the plots we're working with
- so far the way to run a new set of plots is to change the file path from one set of data to the other
- one idea of creating new graphs is to run two parallel sets of data (create two separate root files, one with each set of data) and then have the make plots file reference both of them when creating the graph - I am working with this approach but I need to understand some of the variables in the graphing code, and I would need to change all of the variable names in the second set of data to avoid the two sets being saved to the same names, which is tedious and could be very prone to mistakes
- from my experience with python each graph, after being created, saves the xy data to a variable that can be accessed (if you set it that way), and so you should in theory be able to access the xy data from that graph without accessing the file that created it. I feel like it would be easier to work with the graphs this way, but this would involve me A) finding the way to access that data, which seems convoluted, potentially impossible, and probably ridiculous if I have the original files and B) writing my own code to create a graph, which would be mediocre at best and likely incorrect. I have each of the graphs created and saved, it's only a matter of putting one on top of the other (although the ER graph is currently set on the wrong scale).
MORE WORK:
- changed the variable names in the WIMP RQ.cc file to have a w in fron t if they're going to reference the variables needed for C25 (i feel like we might need C24 and 23 too but we'll start here)
- the variable names in the .cc file all have an h_ in front - they're referenced again in the .hh file, so I have to copy a new one (now called WIMP_DataRQ_V2.hh) and change the names there (assuming this works at all)
-added w's to the variables in lines ~71-78 of the .hh file (WIMP)
- added w's to the variables (two per line) in line 257-262 of the .hh file (WIMP)
-need to find where the make plots file references the .hh file
- added line 1541 and 1543 to the make WIMP plots (under C23)
-added lines in the C25 block (where the comments are)
attempting to run:
-need to make a new .C file, then run the .C file for both, then run the new plotting file (I'll make a new directory for the graphs but they should save to my home directory because the others are in other directories
**need to label the axes
checklist:
copy the .C file and change the name
run both .C files
run the make plots file
- something is wrong with the "new_H3" file - it's saying that i'm using an undeclared identifier (but i thought i got them all - i'll go back and look)
- found the error - changed the "include" line in line 132 of the new_H3_file.cc, now the events are running
- error in running the WIMP plots - "cannot find function "make_WIMP_plot()" (same error as before - look for the analog in the old data)
- found it - changed line 157 in the make_WIMP_plot.cc
- consider commenting out the graphs you don't need - will make things much easier and take less time....
-something went wrong with the C25 graph - says "null passed to a callee that requires a non-null argument in line 1654 of the make WIMP plot file
- deleted the space between 0 and 200?
-same error - come back to it later
03/04/2020
-Eli figured it out - his code seems very similar to mine at first glance, I'm reading through to figure out what he did differently than mine
-Eli's code takes out all of the files that don't directly apply to C25 - I made a new file called "WIMP_plots" that will take the code I modified in "make_WIMP_plot" and change it to match Eli's - the "make_WIMP_plot" file will stay the same in case we need it later, and the "make_H3_plots" file is unchanged from how it was given to us
- only things I need to physically change in the make_WIMP_plot file:
1) change npoints = RecoS2Area_phdOverS1AreaVec.size() to int npoints = ... so that it's defined (but I don't need to do that if I don't delete everything else)
2) change the last part of the Draw() argumet (line begins with ix=0) to Draw("box same") instead of Draw("colz") (commented that as well)
3) change the void function to WIMP_plots()
Graph has been produced successfully:
this is based on 10000 events of each type - I want to run it with 100,000 or more, but I'll wait until after the meeting today so I don't waste time on running data through an incorrect program.
Also, need to add axis titles!
notes on 03/04/2020 meeting
- plot the means of each dataset (not all of the quantile lines)
- the paper has cuts - reconstructed variables x, y, and time - make a cut on R (the detector walls are radioactive - one of the programmed histograms makes a cut but on much wider parameters than we need)
- look in the paper for the cut boundaries - the boundaries are inside the background (see drawing) , background = cosmic rays, radon, radioactive materials, muons, neutrinos (muon itself doesn't give you background but interactions with the rock can produce neutrons/photons that can go in) (at this time we are not simulating background)
- also - overlay the H3 and WIMP data on the #events v S1 and #events V S2 data - that will help us determine the boundaries for the cuts/how much background to expect/what the trends are - we have the finished project but now working backwards from there
next steps:
1) get the quantile lines on BOTH sets of data and ony plot the means for easy comparison
2) plot the S1 S2 data for both H3 and WIMP
3) make the cuts as determined by the paper
03/08/2020
-next goal: overlay the S1 and S2 graphs
- same procedure: rawS1S2.png (C4) is the signals: I've copied over the C4 block of code (from around line 345 of make_WIMP_plots.cc), starting to follow the same procedure as graphing the overlay from lsat week
- going into the .hh file and changing variable names by adding w's in front
- running into the same issue as last time - "warning - null apassed to calle that requires non-null argument" I can't tell how Eli got around this last time because the code looks identical and nothing needs to be changed in other files
- Eli says its a typo - added a w in front of the hname in line 242 of the .hh file
- trying to find the typo
03/09/2020
- continuing work on trying to find the typo in my overlay code, check in with the group tomorrow to figure out where everyone's at
- typo issue: it's a problem where the program can't find the name of the histogram in the .root file and is throwing a null pointer. I thought I changed the names in the .root file, but checking again::
- the .cc file draws from two different root files, so I shouldn't have a problem with the same variable - what if i remove the w's from the variables in the .hh file?
-forgot to add w's in the DataRQ_V2.cc file - if trying an overlay, need to change variables in EVERY SINGLE FILE
for future reference, change variables in:
1) DataRQ_V2.cc file
2) make plots .cc file
3) .hh file
4) shortened make plots file
- adding w's to lines: 444 and 445, 483-484, 496-7, 512, 514, 527-8, 544-5, 653, 658-60, 693-702,
- attempting the run again...throwing errors: 1) no member named "wrawS1Photons[ivtx]" in RQ::RQMCTruthVertices (or wrawS2Photons), 2) use of undeclared identifier 'rawS2Photons', 3) use of undeclared identifier 'WIMP_DataRQ'
-trying another option- REMOVING all of the w's, just defining the w's in the WIMP_plots.cc file so it recognizes the difference between the H3 and the WIMP histograms (basically: i can't find the disconnect between the .hh file and the .root file [it refuses to save the histograms with the w's in the name] but since the files the code references are completely separate until the end, it should be okay as long as I import the data with different variable names)
-something isn't being defined properly- is there a file i need to run before running the .C file? It keeps throwing errors that things aren't declared
-found the problem - forgot to remove a w from the .cc file, .C file is now running as needed (23:35)
-.C ran successfully (and then the pipe broke so may have to re-run) - attempting to run the WIMP_plots.cc file next
-23:37 - re-running the .C file because of broken pipe
- look into why the pipe keeps breaking maybe? is it because I have too many files open at once?
-23:39 - improvement - new error! in WIMP_plots.cc line 177, "invalid memory pointer passed to a callee: RawS1Photons_ss -> SetMarkerColor(2)" . Maybe because of the w's?
- after two hours i have run into the same exact problem I started with.
- invalid memory pointer could be bc the H3 file wasn't run - the .root file for the H3 data was empty, so I'd assume it needs to run first (running now 00:04)
- that was the problem - GOT THE OVERLAY!
FOR FUTURE REFERENCE IF I NEED FUTURE OVERLAYS:
1) don't add w's in each file, that's time consuming and not helpful and causes 10000 problems. just change the variable name for the histogram loaded through g and deal with it that way. make sure to put "same" in the Draw() function so it plots on the same graph.
2) make sure to run BOTH .C files or the .root files won't be created
***still needs axis titles and a legend (not sure which is which)
STEPS FOR TOMORROW:
1) add axis titles and a legend so we know what we're looking at
2) start looking at the cuts
3) ask Eli for the code that only plots the mean quantile line
03/10/2020
12:00 - added axis titles for both graphs, still need a legend. Read through John's summary of notes on the paper, reading through the paper to figure out how to implement cuts next.
03/29/2020
getting back on track:
- currently have 2/3 original goals completed, still working on understanding cuts on the data
- in the .cc file, lines 65-66 reference Z-boundaries and R-boundaries. WE think these refer to the cuts in R and in Z = time, but we're not sure - the values defined in those statements don't look familiar and both lines are commented out
- line 401 references the Z and R values but that is the only line that does
- RMAX is 735mm or .735m which is the width of the detector (line 54) - if we just change the value that should make the cuts we need (same with ZMAX)
- changed 735 to 335 to see if there is a noticeable difference - reality need to take off 40mm not 400, just a test run
- tried to run but root isn't working - can't find GLIBC... libraries (restarting connection doesn't work, source setup_root.sh DOES work)
- eli ran the edited values and it does have an effect - directly from the paper: "The FV is cylindrical with boundaries defined to be 4 cm from the TPC walls, 2 cm above the cathode grid (with 14.8 cm of LXe below the cathode providing further shielding) and 13 cm below the gate grid." Eli and John are attempting that run now (17:36), I am editing my files to reflect those cuts (lines 54, 61-2)
04/01/2020
- working on video presentations and uploads
- submitted progress to Prof. Bhatti on Sunday, waiting on comments before continuing
04/08/2020
Received comments from prof. Bhatti along with instructions for next week:
" You plots look good. Are you using reconstructed values of x, y ? For z, you should use cut on time. Time is the time electrons take to reach the top of the TPC. Given electron drift time, one can calculate z position but one can use time instead.
I would like you to make a plot. It will tell us how well we can discriminate between DM signal and other backgrounds. Most backgrounds come from electron scattering and look like the response of tritium data.
You make a plot which shows the fraction of tritium data with response less than median value of WIMP response vs S1 signal. In this plot, horizontal axis is S1 counts and vertical axis is fraction.
You have S2 vs S1 plots.
From WIMP plot, you can calculate the median value for each bin.
From tritium plot, calculate fraction of events where response is LESS than median value calculated from WIMP plot.
Make plot of tritium fraction vs S1.
One may decide to define “signal region” to be the events below median of WIMP response. This by definition accepts 50% of the signal. Above plot will tell has how much of background event one will reject by this cut."
- set of lines (around line 120) that defines a set of doubles: true X Y Z and reconstructed X Y Z. We're supposed to be using the reconstructed values, which means that we probably did the cuts wrong
- line 554 - double recoX, recoY, recoZ, R2, R, drift_time defined as -88888 - not sure why they have that definition but that looks like the variables we would need for the time cut
- electron drift speed 1.8mm/microsecond (from paper)
**note - when running graphs, need to run WIMP_DataRQ.C~
04/11/2020
-Eli has the graph we were making from the presentation, but unclear whether or not it's correct
- running the BACCARAT analysis (copied files from John's directory after he copied them from the actual directory)
- getting weird warnings after running the BACCARAT.C file - something about "___ may be uninitialized in this function" but the next step (BaccRootAnalysis("BG");) is running fine
- baccarat analysis has run successfully - creates multiple .root files that all contain RZ2Position plots, unsure which one we're supposed to be looking at and what they mean
STEPS FOR BACCARAT ANALYSIS:
I copied the code to
~honr_bhatti/BACCARAT_Analysis/
to run:
source setup_baccarat.sh 4.11.0
root.exe BACCARAT.C
BaccRootAnalysis("BG");
It will produce a *.root file with histograms.
We are in particular interested in R2ZPosition plot.
-going to send an email tonight with these graphs
moving on to fixing the median plot:
conceptual explanation: the most likely source of background comes from electron scattering, which will mimic the tritium data (also electron scattering). thinking of the ER NR overlay plot - if we make a cut at the WIMP median, that will eliminate most of the tritium data and therefore most of the electron scattering background. We're making a plot to determine how much of the tritium data we would NOT be eliminating with the median cut.
- progress:
working with Eli on making the ratio plot: supposed to take the sum of the x bin and then the sum of values less than the WIMP median and make a ratio plot of those values. The plot itself/data we are working from is a 2D-histogram, but (if we understand correctly) the ratios will save as a 1D-array, which then needs to be plotted against the S1 counts. The only S1 variable that is a 1D-array is the Raw S1, which actually should be a 1D-array - not entirely sure if that is the goal though
04/13/2020
- made a google doc for group questions
- there's an IFPRINT statement that seems to be able to print certain variables (including drift time), but when the code is run it doesn't print out that statement, it prints the entire code into the browser. Not sure why or how to fix that.
- there is a drift time histogram under data->Lz....->scatters->ss, shows that the mean drift time is .000111 seconds (which seems reasonable). Unfortunately that's a mean, so it doesn't tell us where to cut - we're compiling questions to get more answers on that front.
WHERE WE'RE AT:
- drift time - working on it, we need to ask some questions (john)
- H3 vs S1 ratio plot - just received some feedback, need to implement that with Eli
- summarize table 3 - john = completed, eli, ben, me = need to do (next priority for me)
- examine the BG RZ2 position plots from the BACCARAT and determine where background is coming from (everyone)
- make Fig. 2 plots (everyone?)
- we should have all the data toward that in the .cc file (2D histograms)
04/14/2020
NOTES ON SECTION IV OF PAPER:
(fiducial - assumed as a fixed basis of comparison)
- Table III - background ER and NR counts before and after ER discrimination cuts
- 40 GeV/c^2 WIMP spectrum
- 1.5-6.5 keV for ER
- 6-30 keV for NR
- expected background total from all ER & NR = 1131 ER and 1.03 NR
- w/ 99.5% discrimination against ER and 50% acceptance of NR = 5.66 ER and 0.52 NR = total = 6.18 counts
(^^Table III)
- Radon = largest contributor to total # of events
- atmospheric neutrinos = largest contributor to NR counts
Trace Radioactivity:
-most prevalent isotopes = gamma emitting: K-40, Cs-132, Co-60, U-238, U-235, Th-232
**not expected to be leading cause of background (shielding)
Surface contaminants -
-Rn-222-daughters from assembly (plate-out)
- (alpha, n) processes emit neutrons into Xe
- ions in Pb-210 can be misreconstructed as NR
-target for plate-out in Pb-210 and Po-210 < 0.5 mBq/m^2 on TPC walls, <10 mBq/m^2 everywhere else
- naturally-occurring radioactive materials (NORMs) from dust lead to gamma ray and neutron emission
- limit dust <500ng/cm^2 (cleaning protocols)
Dispersed xenon contaminants:
-radioisotopes - background not blocked by self-shielding
- radon = largest contribution b/c "naked beta emission" (beta emission without gamma rays)
- emanation can depend strongly on temperature of the material
- 1.53 microBq/kg of LXe Rn-220 activity
-from dust: 0.28 microBq/kg
-projected total: 1.8 microBq/kg
(0.09 microBq/kg of Rn-220 included in estimates)
- natural Xe contains Kr-85 and Ar-39 which are both beta emitters - contribute to ER events
- Kr reduced to expected 0.015 ppt g/g
- Ar reduced to < .45 ppb g/g
Laboratory/cosmogenic backgrounds
- neutrinos from muon-induced electromagnetic/hadronic cascades - reduced by shielding to negligible contribution
- 27 +/- 0.5 mBq/kg decay rate
- largest contribution to activation in detector materials: Sc-46, 4.8mBq/kg Ti after 6 months
Physics backgrounds (biggest contribution):
- neutrino-electron scattering (ER), 2v-beta-beta Xe-136 decay (ER), neutrino-nucleus scattering (NR) - all single-scatter events with no veto signal
- solar neutrino background = pp neutrinos
- NR: B-8 and hep solar neutrinos, supernova neutrinos, and atmospheric neutrinos
- B-8 and hep events = low recoil energy, impact depends strongly on NR efficiency
- not included in table III but included in WIMP sensitivity calculations
- atmospheric and supernova neutrinos = higher energies = largest contribution to NR background
Non-standard backgrounds (unlikely but possible events):
- multiple-scattering gamma rays = NR-like background
-lower S2/S1 ration than ER, leaks into NR band
- <0.1 events expected
- PMT dark counts lead to fake S1-only signals, which can pair with S2-only signals and create plausible S1-S2 pairs, contributes to NR counts
- <0.2 events expected
- S1-like signals from Cherenkov light - easily identified basked on timing and PMT hit patterns
- <0.2 events expected
04/17/2020
- new thing to do: make plots with reconstructed events
- need to copy over files from new directory (taking a long time [15:56], look into this if it's an issue?)
- use the same files as the tritium and WIMP data
TO RUN RECONSTRUCTED BACKGROUND EVENTS:
-used WIMP DataRQ file
-changed file path in lines 217-18, 145 to /data2/users/bhatti/lz/BG/20200407 from /data2/users/bhatti/lz/BG/20200204
- running using same procedure as WIMP data ... changing output file to make it different from WIMP? (changed basename to BG)
- copied and made "new" .cc and .C files labelled BG (easier)
-first attempt at running the .C file didn't make an output file?
- need to run the "make plots" file and change the name of the function in the .hh file, then it runs
the plots of interest are C1, C1A, and C6, though those have R2 vs. Z not R2 vs. drift time. I have to change that...
-had to change the .root file, it was still calling or naming the H3 file
-have to change what it's plotting - check the .hh file and import the histograms (and maybe delete irrelevant graphs especially because 9 and 10 take so long to run)
-error = saying that the file BG_DataRQ_plots.root doesn't exist and it should exist...
04/18/2020
-fixed the files? maybe? changed the basename to BG, changed the function to BG_DataRQ()
- created .root file!
- there is a block of commented-out code around line 580 of the .cc file which (above in uncommented code) defines the variables singleScatter->driftTime_ns
-**Note: the .root file will only be created if you run the make plots file (but you don't have to run the whole file)
- uncommenting those blocks (plus the line of code John added to try and combine the histograms) results in the h_drift_time_0 and the h_ that John added as undeclared
- getting an error when trying to run the histograms: "C++ requires a type specifier for all declarations", but I defined the histogram in the .hh file in the block of code at the beginning of the file and I can't find ANY differences between the way that the new uncommented code is defined and the way that the original code is defined, so I'm VERY lost.
04/19/2020
- problem - the histogram was defined outside of the BookHistogram() function in the .hh file
- the histogram still isn't plotting - not sure why, all code looks the same as it does with other histograms, is it a parameter issue?
- email for answers
email:
- might be a parameter issue, change those values
- 2D histograms are ("name", "title", #bins, start, end)
04/26/2020
- working on paper/finishing graphs
- john is working on the ratio plot
-i'm writing, working on making the graph with the "lines"
04/30/2020
- [11:41] working on abstract - sending for feedback to submit with poster
- [21:52] working on poster - hoping to get a rough outline to be continued tomorrow w/ group
- will hopefully finish plots tomorrow
- finished outline of poster: still need two plots and some descriptions
- submitted poster proposal for the showcase
05/01/2020
- received comments on abstract, made edits (abstract completed)
- continued work on poster - added descriptions and Ben added conclusion, now only need the two plots and edits
05/02/2020
- more work on poster:
-from what i understand, I actually made the plot without cuts and the plot with cuts already, so I've been thinking about it wrong. I can add lines to the old plot and work on doing that, but I don't know if that's essential
- except for fixing that, I can't do any more work on the poster without input from the rest of the group - i need the ratio plot from Eli and I need edits from everyone else
- finished poster and sent draft to bhatti
- group didn't get anywhere with ratio plot - sent back questions
05/03/2020
- received edits on poster: pasting here to make a checklist/keep track of edits to the plots
__You should include picture below instead of the picture you have. Then you can talk about S1 and S2 when giving presentation.
__ For figures with S1 and S2, H3/WIMP data in both figure should have the same colors. --> me
__ If possible make a colored version of background distributions --> me (i have this already)
__ For S1Area_phd_logS2Area_phd, you should only plot the median of the distribution. Do have a plot with both ER and NR overlaid?
A plot with both ER and NR overlaid with medians of two distributions will be better. --> Eli has this code
__Fig. 2:
I do not see redline in the plot. I see cyan and magenta lines which is above the data thus cannot be median of WIMP data. --> Eli
It is hard to see two sets of points. May be you should divide it in two pads and plot them separately.
__Fig.3 Use simulated quantities like the ones used in Fig. 2. Can you normalize these plots so that H3 and WIMP data have same area? --> me
Here is the code. h is the same of histogram which you want to normalize.
Double_t scale = 1/h->Integral();
h->Scale(scale);
__“which can only interact with baryonic matter through gravitation.”
It is not correct. It has some other interactions also which are very weak.
“which can in addition to gravitation, interact with baryonic matter very weakly through some other yet-to discovered force.”
__“Ideally” delete.
__“(S 2 signal)” move a line above after “ionization electrons”
__There are PMTS which are at the bottom also which are also used to record both S1 and S2 signals. As light is produced it travels in all directions.
__"These interaction with the Xe can either occur with the outer electrons (ER) or with the
nucleus (NR) which is the projected interaction type for dark matter.”
What do you mean by “These interaction” ? You should rephrase this sentence.
__WIMP interacts with nucleus only. Other particles (like electrons, photons) interact with electrons which are background events in this analysis. Purpose of this study is whether we can distinguish between NR (mostly WIMP) and ER (mostly electrons) by cutting on
S1/S2 signals.
__“… background comes from radiation from the walls of the detector.”
… background events come from the radioactive material in the walls of the detector.
__“…removing much of the wall introduced from the radiation from the walls.”
“… removing most of the wall induced events.”
__ Some place you need to add drift time measures the z position of the interaction.
__Caption Fig 4 .
Delete “evenly”
__Once you get ratio plot, you should refer to Fig 6 and provide a number for
“a significant portion of the ER background”
xx% of the ER background.
(If I look at Fig3 S2 plot, I see that a 30 10^3, will remove more than 90% of the ER events.)
__You do not refer to Table 1.
“Most of the anticipated sources of background are expected to exhibit ER behavior”
è As shown in Table 1 cite[], most of the anticipated sources of background are expected to exhibit ER behavior.
05/04/2020:
- corrected all edits on the poster except for the ratio plot (need to send a table of values)
- normalized areas of S1 and S2 overlay
- changed fig 2 to two plots and plotted the WIMP median
Page updated
Report abuse