You are here: Foswiki>HAWC Web>NickDagher (17 Sep 2015, NickDagher)EditAttach

Weekly goals

  • Week of June 1st
    • have pats plots of Pythia 6 working
    • how pythia8 and root work together
    • read "Reliability of Monte Carlo event generators for gamma-ray dark matter searches"
    • get mary cluster and start aerie homework
  • Week of june 8th
    • Do aerie hw 1
    • how does pythia 8 work
    • how do you make plot the dark matter in pythia 8
  • To Do
    • Since pythia 6 wont work on the umd cluster or this macbook i need to put it on a computer in the office
    • Do decied what large event runs for pythia 6 and pythia 8 to do
    • learn to use plot digitizer for article plots
    • add the data points gotten from plot difitizer to completed code for plotting article and flux.

Getting Acquainted

Dual booting Linux with windows 8

  • In order to use pythia I am going to dual boot ubuntu on to my computer. I have followed the instructions from this website
  • In order to do this you need 2 usbs, (I used 16 gb to make sure i had enough space) and an external hard drive (you really just need anything that will back up your personal files)
  • The main steps that I took were
    • create a recovery drive with one of the usbs
    • back up all personal files onto an external hard drive
    • Install ubuntu from their website
    • Install the driver that will put ubuntu on too the 2nd usb
    • turn off fast boot option
    • turn off secure boot, for help see https://neosmart.net/wiki/disabling-secure-boot/

Running and compiling fortran code

To do with pat

  • go over thought proccess of replicating the dark matter collision
  • go over the pythia 6 code in order to connect the thought proccess and code
  • what parts of the code are specific to dark matter

Pythia 6

code structure
  • The code calls for 100000 events, and a mass of 1 TeV
  • "Basically, this means that there are three ways by which you c

    ommunicate with the

    programs. First, by setting common-block variables, you sp

    ecify the details of how the pro-

    grams should perform specific tasks, e.g. which subprocesse

    s should be generated, which

    particle masses should be assumed, which coupling constant

    s used, which fragmentation

    scenarios, and so on with hundreds of options and parameters

    . Second, by calling subrou-

    tines you tell the programs to generate events according to t

    he rules established above.

    Normally there are few subroutine arguments, and those are u

    sually related to details of

    the physical situation, such as what c.m. energy to assume fo

    r events. Third, you can

    either look at the common block

    PYJETS

    to extract information on the generated event, or

    you can call on various functions and subroutines to analyse

    the event further for you" -Pythia 6.4 manual
  • Appendix B is an index to all subprogrograms and common-block variables
  • the key points of the file are:
    • a positron and electron annihalate into a z, z' and a gamma. We only want the proccess that goes to z'
    • turn off inital-state radiation,photonic part of pdf for e+ e- interactions.
    • Allow muons,pions,kaons, and k_long to decay. (try and add nutron decay to pythia 8)
    • in muon decay:mu -> nu_ebar + e- + nu_mu + gamma is 1.4% and mu -> nu_ebar + e- + nu_mu is 98.6%. Need to set these decays to there per centage and creat a decay channel to store the rare decay.
    • turn off all pre-existing Z' decay channels
    • give z' parameters of mass=com, no mass width, no broadening, and no lifetime
    • creat a new decay channel to go to 100% of the time for the z' to go to either bbbar,ttbat,ww,zz
    • Initialize collidpor and run 10000 events and colect energy of photons after every event

Pythia 8

Readings

Aerie

to configure : export CONFIG_HAWC=./config-hawc
Homework

Root


Tutorial
Browser
  • TBrowser b to open a browser
  • TFile myfile("filename")

Installing root

    • went to the root website and went to downloads tab and clicked patches v5-34-00. Downloaded the source link* after downloading the source link and extracting the files run "./configure" and install any needed required packages, use the website for assistance
    • After you run configure after installing necessary packages. run "make" in the terminal and then run "make install"
Plotting functions
  • TF2 f1("func1",thefunction,xmin,xmax,ymin,ymax)
  • then next line type f2.Draw() use "surf1" for a surface plot
Plotting Histograms
  • TH1D h1("rootname",title,#ofbins,binmin,binmax)
    • This creats an empty histogram, we must fill it
    • h1 is the c++ name and hist1 is the root name
    • use h1.FillRandom("gauss",10000) to fill it with 10000 points of data fraom the functions "guass"
  • TF1 myfunc("myfunc",
  • hist1 is the root name of this histogram
  • h1.GetBinWidth(0) to get the bin width
  • TF1 myfunc("myfunc","gaus",0,3)
    • myfunc.SetParameters(10.,1.0,0.5) to set P0,P1,P2 the parameters of the gaussian function "Constant" "Mean and "sigma"
pointers
  • TH1D *hist1 = new TH1D ("h1","a histogram",100,-3,3)
  • this creates a pointer
Analyze
  • setup:define the histogram
  • loop section: fill the histogram with values
  • wrapupsection: draw the histogram
Plotting N-tuples/trees
  • tree1->Scan() runs like 25 events
  • tree1->Print() it displays the names of the variables and the size of the tree
  • tree1->Draw("variableyouwant") makes a histogram for a variable in the tree

Outriggers

  • Need to make plots of radius vs #triggered showeres/#totalshowers (Where triggered showeres are showeres that hit ~30pmts on the HAWC300 array) for different energys. In order to find the max radius our experiment can detect for different energy.

  • Need to see the most optimal method of arranging the outriggers, Going to use the sunflower sprial to start but may mask tanks off to create a denser array near HAWC300 and lesser dense array farther away from it.

  • use files that dirk sent : NoBadChannels.xml HAWC300_v1.0.xml and plot-detector.cc to create a file that is titled what ever you choose when you compiled plot detector.

  • Now i am trying to use a file titled create_spiral_outriggers.py but i am getting the following thing appears

    • nick@nick-Satellite-P755:~/workspace/dagherni/outriggers$ python create_spiral_outriggers.py
      This script requires: numpy, matplotlib, argparse, xml and StringIO

    • i beleive i have numpy and matplotlib but i need to check for the others

So the basic order in running the simulations is corsika recreates an airshower on hawc, hawcsim then uses the corsika file to simulate how the hawc detector would see this air shower. Then we put that ouput throgh the reconstruction to see where we think the showere came from and compare it to the corsika file to see how our guess was

  • I want to run the corsika file through hawc sim in order to see how far i can throw the core and still trigger on the array

Breaking Homer

  • HW scalers tab
    • If you click anywhere on the color changing key on the right or one of the 4 example circles labeled 0,20,40,60 then you need to refresh the page in order to click on anything else.
    • If you click on the tank and not the dots in the tank then you need to refresh in order to click on anything else
    • when hovering over a tank it displays the last time updated but not the range in time the graph displays. maybe add the range and make the graph bigger if your hovering over, it is hard to read unless i click it to go to the expanded page
    • Once you click on a dot and the graph displays it is kind of small so a zoom option would be usefull
  • GTC Status tab
    • <del>scrolling the graph from left to right is a little glitchy</del>
    • it seems like the y range is too high, all the points look like a line at the bottom, so maybe a zoom option or an ability to adjust the range
    • being able to select the range in time that is displayed may be helpfull as well
  • EMS Monitoring tab
    • when hovering over the graphs the bubble of information doesnt always display what the crusor is on, sometimes it is off by ~inch
    • I tried to scroll left and right like i did for the GTC tab but it actually zoomed me in
    • If you click plot with out a start date, an end state or either then no plots appear
    • if you make the start and end date the same then a plot still appears but there is nothing on the plot
    • I think it would be useful to seperate the zoom and scroll so you could zoom in multiple times and still be able to scroll left and right
  • Lighting Monitoring tab
    • The start date and end date have the same problems as before.
    • im trying to drag the image to my desktop to save it but i keep zooming/scrolling on the graph
  • Computer Status tab
    • MY comments for this page are the same for the previous tabs regarding the start/end date and the scroll/zoom feature. Also still trouble trying to drag it instead of zooming/scrolling
    • For the bottom graph i clicked on a colored square in the key and instead of highlighting that color in the graph it removed that color.
  • Network Monitoring
    • same comments on zoom/scroll and draging to save
    • while i was clicking around on the bottom 2 graphs, i was able to drag each of them too the side and delete them from the page. I was only able to do it twice and i cant figure out how i did it haha.
    • if you right click the bottom graph it dissapears
  • HV monitoring
    • Draging the image off the screen does not save or do anything.
  • LV monitoring
    • the graphs on the right are getting cut off the screen unless you make the page large
    • right clicking the graph changes the the y axis
    • zooming in changes the y axis but when you zoom back out the axis doesnt change back
  • VAC monitoring tab
    • the hovering information bubble is not showing the point the cursor is pointing at, it is off by inches
  • UPS Monitoring tab
    • nothing that i havn't mentioned earlier regarding the control of the plot
  • Reconstruction Monitoring tab
    • Can not access, still waiting for hawc wiki account
  • Residuals monitoring tab
    • Can not access, still waiting for hawc wiki account
  • Webcams tab
    • Can not access, still waiting for hawc wiki account

Convos

dagherni
[<a href="https://hawc.slack.com/archives/D055HFEG7/p1436981361000002" target="new_1438270285625" title="July 15th at 1:29:21 PM Click to open in archives">1:29 PM]Hey! After each event when you loop through the particle list in order to fill the histogram with the energy, you ask if each particle has 1) fragmented or decayed and 2) if it is a gamma. Can i get away with only asking if it is a gamma or is it necessary to ask if the gamma has fragmented or decayed?


harding [<a href="https://hawc.slack.com/archives/D055HFEG7/p1436984017000003" target="new_1438270285625" title="July 15th at 2:13:37 PM Click to open in archives">2:13 PM]For those specific particles, you can probably get away with not checking if they've decayed, etc


harding[2:14 PM]Though you still need to check that they aren't the initial electron+positron that annihilated, for instance


harding[2:16 PM]The nice thing about how I did it is that if an electron spits off a gamma, for instance, it wouldn't double-count them


dagherni [<a href="https://hawc.slack.com/archives/D055HFEG7/p1436984433000006" target="new_1438270285625" title="July 15th at 2:20:33 PM Click to open in archives">2:20 PM]alrighty!


dagherni[2:20 PM]thank youu


-----

July 20th, 2015 -----

dagherni [<a href="https://hawc.slack.com/archives/D055HFEG7/p1437408781000002" target="new_1438270285625" title="July 20th at 12:13:01 PM Click to open in archives">12:13 PM]hello, I was wondering how you calculated dN - avg in your out put file. Is it the number of hits for that energy?


harding [<a href="https://hawc.slack.com/archives/D055HFEG7/p1437409002000003" target="new_1438270285625" title="July 20th at 12:16:42 PM Click to open in archives">12:16 PM]Yes, it is the average number of gamma rays in that energy bin.


dagherni [<a href="https://hawc.slack.com/archives/D055HFEG7/p1437409451000004" target="new_1438270285625" title="July 20th at 12:24:11 PM Click to open in archives">12:24 PM]so you fill the histogram with the energy of every photon after every event and then after all the events i divide the total number of hits in each bin by the number of events


harding [<a href="https://hawc.slack.com/archives/D055HFEG7/p1437410215000005" target="new_1438270285625" title="July 20th at 12:36:55 PM Click to open in archives">12:36 PM]yep


dagherni [<a href="https://hawc.slack.com/archives/D055HFEG7/p1437411228000006" target="new_1438270285625" title="July 20th at 12:53:48 PM Click to open in archives">12:53 PM]awesome! thank you


-----

July 23rd, 2015 -----

dagherni [<a href="https://hawc.slack.com/archives/D055HFEG7/p1437675847000002" target="new_1438270285625" title="July 23rd at 2:24:07 PM Click to open in archives">2:24 PM]hello!


dagherni[2:24 PM]CALL PYBOOK(1, 'log of photon energy',
& 100,-2.d0,log10(ECM/2.d0))


dagherni[2:25 PM]does this mean the minimum bin is -2 because when i look at the data that gets printed out the lowest bin is like .01, not -2


harding [<a href="https://hawc.slack.com/archives/D055HFEG7/p1437676558000005" target="new_1438270285625" title="July 23rd at 2:35:58 PM Click to open in archives">2:35 PM]The value being filled is the log10 of the energy. But when I print it out, I print out the actual energy 10**-2


dagherni [<a data-original-title="July 23rd at 2:54:05 PM Click to open in archives" href="https://hawc.slack.com/archives/D055HFEG7/p1437677645000006" target="new_1438270285625" title="">2:54 PM]so when you print the energy and dn, you print the actual energy times 10^-2 not the log of the energy


harding [<a href="https://hawc.slack.com/archives/D055HFEG7/p1437679776000007" target="new_1438270285625" title="July 23rd at 3:29:36 PM Click to open in archives">3:29 PM]The actual energy. 10^log10(energy)


harding[3:30 PM]It's in GeV and goes down to 10 MeV


-----

Yesterday July 29th, 2015 -----

dagherni [<a href="https://hawc.slack.com/archives/D055HFEG7/p1438184481000002" target="new_1438270285625" title="Yesterday  at 11:41:21 AM Click to open in archives">11:41 AM]Sorry just for clarification, am i printing (10^-2)*(10^log10(energy)) or just 10^log10(energy).


harding [<a href="https://hawc.slack.com/archives/D055HFEG7/p1438185933000003" target="new_1438270285625" title="Yesterday  at 12:05:33 PM Click to open in archives">12:05 PM]just 10^log10(energy)


harding[12:05 PM]The lowest value when you do that will be 10^-2


dagherni [<a href="https://hawc.slack.com/archives/D055HFEG7/p1438186436000005" target="new_1438270285625" title="Yesterday  at 12:13:56 PM Click to open in archives">12:13 PM]ahh i see


harding [<a href="https://hawc.slack.com/archives/D055HFEG7/p1438186882000006" target="new_1438270285625" title="Yesterday  at 12:21:22 PM Click to open in archives">12:21 PM]Sorry for the confusion


dagherni [<a data-original-title="Yesterday at 4:06:38 PM Click to open in archives" href="https://hawc.slack.com/archives/D055HFEG7/p1438200398000002" target="new_1438270285625" title="">4:06 PM] no problem!
Topic attachments
I Attachment Action Size Date Who Comment
HAWC_Harding_note.pdfpdf HAWC_Harding_note.pdf manage 176.4 K 03 Jun 2015 - 14:35 NickDagher "Notes on calculating dark matter fluxes"
HAWC_Pretz_note.pdfpdf HAWC_Pretz_note.pdf manage 418.2 K 03 Jun 2015 - 14:54 NickDagher "WIMP Annihilation Limits from Segue 1 with Early HAWC-30 Data"
MCdiscrepancyDM.pdfpdf MCdiscrepancyDM.pdf manage 1591.1 K 03 Jun 2015 - 14:56 NickDagher "Prepared for submission to JHEP Reliability of Monte Carlo event generators for gamma{ray dark matter searches"
RootClass2014.pdfpdf RootClass2014.pdf manage 1431.9 K 03 Jun 2015 - 19:42 NickDagher Root tutorial
Sensitivity_HAWC.pdfpdf Sensitivity_HAWC.pdf manage 728.6 K 03 Jun 2015 - 14:50 NickDagher "Sensitivity of the high altitude water Cherenkov detector to sources of multi-TeV gamma rays"
Veritas_Segue1.pdfpdf Veritas_Segue1.pdf manage 386.4 K 03 Jun 2015 - 14:57 NickDagher "VERITAS Deep Observations of the Dwarf Spheroidal Galaxy Segue 1"
Topic revision: r40 - 17 Sep 2015, NickDagher
 

This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback