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 manualHist ZpT( "Z0 pT spectrum", 100, 0., 100.);
ZpT.fill( 22.7, 1.)
Reliability of Monte Carlo event generators for
gamma{ray dark matter searches"
Segue 1"
Outriggers
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
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 StringIOi beleive i have numpy and matplotlib but i need to check for the others
- 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\xA015th\xA0at\xA01:29:21\xA0PM 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\xA015th\xA0at\xA02:13:37\xA0PM 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\xA015th\xA0at\xA02:20:33\xA0PM 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\xA020th\xA0at\xA012:13:01\xA0PM 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\xA020th\xA0at\xA012:16:42\xA0PM 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\xA020th\xA0at\xA012:24:11\xA0PM 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\xA020th\xA0at\xA012:36:55\xA0PM Click to open in archives">12:36 PM]yep
dagherni [<a href="https://hawc.slack.com/archives/D055HFEG7/p1437411228000006" target="new_1438270285625" title="July\xA020th\xA0at\xA012:53:48\xA0PM 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\xA023rd\xA0at\xA02:24:07\xA0PM Click to open in archives">2:24 PM]hello!
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\xA023rd\xA0at\xA02:35:58\xA0PM 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\xA023rd\xA0at\xA03:29:36\xA0PM Click to open in archives">3:29 PM]The actual energy. 10^log10(energy)
----- Yesterday July 29th, 2015 -----
dagherni [<a href="https://hawc.slack.com/archives/D055HFEG7/p1438184481000002" target="new_1438270285625" title="Yesterday\xA0\xA0at\xA011:41:21\xA0AM 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\xA0\xA0at\xA012:05:33\xA0PM 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\xA0\xA0at\xA012:13:56\xA0PM 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\xA0\xA0at\xA012:21:22\xA0PM 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!
I | Attachment | Action | Size | Date | Who | Comment |
---|---|---|---|---|---|---|
![]() |
HAWC_Harding_note.pdf | manage | 176 K | 03 Jun 2015 - 14:35 | NickDagher | "Notes on calculating dark matter fluxes" |
![]() |
HAWC_Pretz_note.pdf | manage | 418 K | 03 Jun 2015 - 14:54 | NickDagher | "WIMP Annihilation Limits from Segue 1 with Early HAWC-30 Data" |
![]() |
MCdiscrepancyDM.pdf | manage | 1 MB | 03 Jun 2015 - 14:56 | NickDagher | "Prepared for submission to JHEP Reliability of Monte Carlo event generators for gamma{ray dark matter searches" |
![]() |
RootClass2014.pdf | manage | 1 MB | 03 Jun 2015 - 19:42 | NickDagher | Root tutorial |
![]() |
Sensitivity_HAWC.pdf | manage | 728 K | 03 Jun 2015 - 14:50 | NickDagher | "Sensitivity of the high altitude water Cherenkov detector to sources of multi-TeV gamma rays" |
![]() |
Veritas_Segue1.pdf | manage | 386 K | 03 Jun 2015 - 14:57 | NickDagher | "VERITAS Deep Observations of the Dwarf Spheroidal Galaxy Segue 1" |