The input file I use is at /work/hallb/hps/holly/debug/egsv3-triv2-g4v1_s2d6_1.slcio
If I run the steering, I observe several things:1. The number of pairs being looked at is significantly small (on the order of 2/100k events). Does this make sense? The number of singles being considered was around 7k. So is everything else just background?
2. In the terminal screen shot below, I commented out the other FADC trigger drivers and only ran singles0. The output file is at : /work/hallb/hps/holly/debug/out.singles0.slcioThe corresponding log file is out.triggers.singles0
It only outputs two events that have passed trigger cuts despite my specifying a singles only cut. I am not sure why only 2 events were passed to the pairs trigger cut. I would think there should be more pairs considered. Is there a bug in the FADCPrimaryTriggerDriver? The defaults for pairs looks wide enough for singles, but it somehow only sees a few for consideration. Somehow, specifying a singles cut is still losing out when it is considered for pairs.
3. For events that don't pass cuts, empty slcio files are produced. Basically if I run the steering over the input file as it is, I get one good output file that is from pairs0.
I guess I would like some input from those who produce the monte carlo that this makes sense as well as those who wrote the trigger drivers. I don't understand these results.
Thanks,Holly
Use REPLY-ALL to reply to list
To unsubscribe from the HPS-SOFTWARE list, click the following link:
<Screen Shot 2015-03-27 at 5.32.49 PM.png>
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
Use REPLY-ALL to reply to list
To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1