, view all tags
-- BrendanKiburg - 12 Oct 2006 -- BrendanKiburg - 12 Oct 2006

Data Selection

Used the following sql query : {mysql -h twiki -u mucap -p -e "use mucap; select run from runs10 where quality=\"Y\" and target=\"protium\" and condition=\"mu-\" and run>##### and run<#####" > ds_2##.txt}

After selecting the data, I found the following "statistics"
kiburg@zero:~/mucap/database/datasets/muminus$ wc *.txt

7435 7435 44610 total

To calculate the observed statistics, I will use the ds_101/ds_102 sets as a reference.

Total mu-e pairs in 120mm impact cut from 0.1-20 microseconds = 2.63*10^8

This dataset consisted of 313 files.

Scaling up to 7435 files gives (7435/313) * 2.63e8 = 6.25*10^9 good mu-e, a good chunk lower than what we "saw online" (should be about 8-9*10^10)


The following command was used in the mysql database to generate a list of runs within a range that were good. As the datasets are analyzed, I will refine the lists according to the analysis results.

mysql -h twiki -u mucap -p -e "use mucap; select run from runs10 where run>38535 and run<38921 and quality=\"Y\" and tpc_hv=5450 and epc1_hv=2630 and epc2_hv=2790 and mupc1_hv=2500 and condition=\"mu-\" and kicker=\"LESS\" and kicker_hv_top=12.5 and kicker_hv_bottom=12.5 and target=\"protium\" " > query.txt

From here, I simply remove the first line and the result is a list of runs that should be "good"

Topic attachments
I Attachment History Action Size Date Who Comment
Unknown file formatEXT ds_233 r1 manage 2.1 K 2007-02-06 - 22:59 BrendanKiburg data set 233 text file
Edit | Attach | Watch | Print version | History: r6 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r2 - 2007-02-06 - BrendanKiburg
  • Edit
  • Attach
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback