MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Reading_LUND_files",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "15733": {
                "pageid": 15733,
                "ns": 0,
                "title": "Reading",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "==Current quark==\n[http://en.wikipedia.org/wiki/Current_quark]\n\n==Radiative corrections==\n\n[http://www.scholarpedia.org/article/Nucleon_Form_factors#History]\n\n\n\nThe electron efficiency of individual scintillator detectors using the 4.2 GeV data for ND3 and NH3 targets is described below. In the final state, only electron detection was required(inclusive case). The contamination in the electron sample was removed by applying cuts described in the first chapter.  The electron paddle number 10 (B<0)  and 5 (B>0) were chosen  respectively because they contained the most electron events in a first pass semi-inclusive pion analysis of the data set. The electron kinematics(Momentum, scattering angle and invariant mass) for these scintillators is shown on Fig. 3.1. \n\n{| border=\"1\"  |cellpadding=\"20\" cellspacing=\"0 \n|-\n|[[File:EmomInclusiveoverlay4-2GeV.gif|300px]] ||[[File:EthetaInclusiveoverlay4-2GeV.gif|300px]] || [[File:WInclusiveoverlay4-2GeV.gif|300px]]\n|-\n| Electron Momentum((NH3,B>0),  (NH3,B<0), (ND3,B>0) && (ND3,B<0))|| Electron Scattering Angle <math>\\theta</math>((NH3,B>0),  (NH3,B<0), (ND3,B>0) && (ND3,B<0))|| W Invariant mass((NH3,B>0),  (NH3,B<0), (ND3,B>0) && (ND3,B<0))\n|}\n\n'''Figure 3.1. Electron Kinematics.'''\n\n\nThe goal of this thesis is to measure the semi-inclusive asymmetry when an electron and one pion are detected in the final state.  This asymmetry may be written in terms of ratios of charged pion production cross sections from proton and neutron targets sorted according to the orientation of the incident electron helicity with respect to the target's polarization.  Pions of opposite charge will be observed using the same scintillator by flipping the CLAS Torus magnetic field direction. Although the pions will be detected by the same detector elements, the electrons will intersect different detector elements.  As a result, the electron efficiency will need to be evaluated in terms of the electron rate observed in two different scintillators detecting the same electron kinematics.   The two scintillators are defined according to the polarity of the CLAS torus.  \n\n\nThe ratio of the number of electrons weighted by the faraday cup for two different cases are following:\n\n<math>\\frac{ND3,B>0, E_{PaddleNumber}=5}{NH3,B<0,E_{PaddleNumber}=10}=1.55 \\pm 0.15</math>\n\n<math>\\frac{ND3,B<0,E_{PaddleNumber}=10}{NH3,B>0,E_{PaddleNumber}=5}=0.55 \\pm 0.06</math>\n\nThe ratios were taken for different types of target, so that we could compare the results to MAID 2007 Model. In order to make detector efficiency the same for two different cases (ND3,B>0 && NH3,B<0) and (ND3,B<0 && NH3,B>0), the ratios have been adjusted so that it equals to one.  Each of the two cases are multiplied by so called, \"correction coefficient\". The coefficient for the case <math>\\frac{ND3,B>0,E_{PaddleNumber}=5}{NH3,B<0,E_{PaddleNumber}=10}</math> is <math>0.645</math> and for the <math>\\frac{ND3,B<0,E_{PaddleNumber}=10}{NH3,B>0,E_{PaddleNumber}=5}</math> it is <math>1.82</math>.\n\n\n\nIn this chapter we discuss the pion efficiency in semi-inclusive case. The ratio of the pions detected in the scintillator paddles, located between the Cherenkov counter and electromagnetic calorimeter, is shown on Fig. 4.1. The ratios were taken for four different cases. Assuming that, for the inbending case positive pions and for the outbending case have the same trajectories(the same kinematics) and vice versa((the inbending,negative pion) and (the outbending, positive pions)).<br>\n\n[[File:paddenumbvsratio.jpg|500px]]<br>\n'''Figure 4.1. Pion paddle number vs Ratio.'''\n\nWe used MAID 2007 model to compare our results. Total cross section was calculated for the following invariant mass and four momentum transferred square: <math>1.7< W<1.8</math> and <math>Q^2=1.1 GeV^2</math>. <ref name=\"MAID2007\" > http://wwwkph.kph.uni-mainz.de/MAID//maid2007/maid2007.html</ref>. After applying correction coefficients from inclusive cases, the ratios have been compared to the results from MAID2007.\n\n::<math>\\sigma = \\sigma_{T} + \\epsilon \\sigma_{L} + \\sqrt{2\\epsilon(1 + \\epsilon)}\\sigma_{LT} cos{\\phi_{\\pi}}^{CM} + \\epsilon \\sigma{TT} cos2{\\phi_{\\pi}}^{CM} + h \\sqrt{2\\epsilon (1-\\epsilon)}\\sigma_{LT^{\\prime}}sin{\\phi_{\\pi}}^{CM} </math>\n\nAfter applying correction coefficients from inclusive cases, the ratios have been compared to the results from MAID2007.\n\n[[File:black_red_maid_inclusiveerror.png|350px]] [[File:green_blue_inclusiveerror.png|350px]]\n\n'''Figure 4.2.  Pion paddle number vs Ratio after correction.'''\n\nApplied corrections are following:\n\n<math>\\frac{N(\\pi^+,ND_3,B<0)}{N(\\pi^-,NH_3,B>0)} \\times 1.82</math>\n\n<math>\\frac{N(\\pi^+,ND_3,B>0)}{N(\\pi^-,NH_3,B<0)} \\times 0.645</math>\n\n<math>\\frac{N(\\pi^-,ND_3,B>0)}{N(\\pi^+,NH_3,B<0)} \\times 0.645</math>\n\n<math>\\frac{N(\\pi^-,ND_3,B<0)}{N(\\pi^+,NH_3,B>0)} \\times 1.82</math>\n[http://wiki.iac.isu.edu/index.php/Delta_D_over_D Go Back]"
                    }
                ]
            },
            "15152": {
                "pageid": 15152,
                "ns": 0,
                "title": "Reading CODA data",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "=xcefdump=\n;xcefdump: This is a program distributed with CODA to read CODA data files.  It will allow you to look at the contents of headers and ROC banks but it doesn't decode the ROC bank.  You can find it under $CODA/bin\n\n= Event Stucture=\nThe CODA event structure is to write \"Banks\" which are in the form headers containing 2 long words (32 x 2 = 64 bits)\n\nBelow is an example of a hex dump of a CODA file\n\n\n\n==hex dump==\n\nUsing the unix command \"od -h filename\"  on a coda data file I saw the following table of hexadecimal shorts\n\n 0000000 2000 0000 0000 0000 0008 0000 0008 0000\n 0000020 01a3 0000 0002 0000 0027 0000 0100 c0da\n 0000040 0004 0000 01cc 0011 e7ff 4730 0078 0000\n 0000060 0001 0000 0004 0000 01cc 0012 e804 4730\n 0000100 0000 0000 0000 0000 000a 0000 10cc 0001\n 0000120 0004 0000 0100 c000 0001 0000 0001 0000\n 0000140 0000 0000 0003 0000 0101 0002 4c52 5343\n 0000160 0000 0000 000a 0000 10cc 0001 0004 0000\n 0000200 0100 c000 0002 0000 0001 0000 0000 0000\n 0000220 0003 0000 0102 0002 4c52 5343 0000 0000\n 0000240 000a 0000 10cc 0001 0004 0000 0100 c000\n 0000260 0003 0000 0001 0000 0000 0000 0003 0000\n 0000300 0103 0002 4c52 5343 0000 0000 000a 0000\n 0000320 10cc 0001 0004 0000 0100 c000 0004 0000\n 0000340 0001 0000 0000 0000 0003 0000 0104 0002\n 0000360 4c52 5343 0000 0000 000a 0000 10cc 0001\n\nPerhaps the most obvious hex is the value \"c0da\" at the end of line 20.\n\n\nThe first two lines contain file information \n0000000 2000 0000 0000 0000 0008 0000 0008 0000\n0000020 01a3 0000 0002 0000 0027 0000 0100 c0da\n\n\nThe next line\n\n0000040 0004 0000 01cc 0011 e7ff 4730 0078 0000\n \ntells you that the bank length is \"0x0004 = 0d4 \" (Like 0x: Hex,  0d: Decimal *not* 13 x 16) which is saying there are 4 long words (NOT including this one) in the bank.\n\nthe next hex words \n \n\"01cc 0011 \"  represent the next 32 bit long word where \"0xcc\" is the least significant bit 0 to bit 7 (first 8 bits = 1101100 b).  The hex constant \"0xcc\" is used as the \"number\" in the header word.   The next hex snipet \"0x01\"  is used for the data type in the header.  The tag is aliased as the event type \"0x0011 = 17 d = 10001 b is the highest 16 bits of the 32 bit long word which tells you that this event is #17 which corresponds to a prestart event.\n\n== Generic Bank Header== \n\nThe above illustrates the Bank Header format which is used for all banks.  The table below identifies the format we observed in the data file using OD and agrees with Figure 4 in appendic E.1 on pg 98 the documentation listed in the CODA 1.4 manual referenced below.\n\n{| border=\"3\"  cellpadding=\"20\" cellspacing=\"0\"\n|colspan=\"3\"|\nlength\n|-\n|tag(bits 16 <math>\\rightarrow</math> 31)\n|data type(bits 8 <math>\\rightarrow</math> 15)\n|number (bits 0 <math>\\rightarrow</math> 7)\n|}\n\n\n\n== The prestart event==\n\n 0000040 0004 0000 01cc 0011 e7ff 4730 0078 0000\n\nThe remain three 32 bit , \"0xe7ff 4730\",  \"0078 0000\" and \"0001 0000\", tell you the time, run number, and run type respectively.\n\n\"e7ff 4730\" = \"\n\"0078 0000\" = 0x78 = 120 d = run number 120.  Notice how you swap the hex; 0x00780000 <math>\\Rightarrow</math> 0x00000078\n\"0001 0000\" = 0x1 = 1 d = run type =1 \n\n\nBased on the above output from OD we can define Prestart Event Bank as \n\n\n{| border=\"3\"  cellpadding=\"20\" cellspacing=\"0\"\n|0004 0000\n|colspan=\"4\"| 0x00000004 = 4 d = length= 4\n|-\n|01cc 0011\n|0x0011 = 17 d = tag=Event type(bits 16 <math>\\rightarrow</math> 31)\n|0x01 = data type(bits 8 <math>\\rightarrow</math> 15)\n|0xcc= number (bits 0 <math>\\rightarrow</math> 7)\n|-\n|e7ff 4730\n|colspan=\"3\"| = 0x4730e7ff = 1194387455 d = unix time = seconds from Jan 1, 1970 GMT = Tue, 06 Nov 2007 22:17:35 GMT \n|-\n|0078 0000\n|colspan=\"3\"|\n0x 00000078 = 120 d = run number\n|-\n|0001 0000\n|colspan=\"3\"|\n0x 0000 0001 = 1d =Runtype= 1\n|-\n|}\n\nwhich agrees with the table in Appendix F.6 on pg 106 of the manual.\n\n== Go Event==\n\nThe next entry in the data file start with the third entry in the line below.\n\n 0000060 0001 0000 0004 0000 01cc 0012 e804 4730\n 0000100 0000 0000 0000 0000 000a 0000 10cc 0001\n 0000120 0004 0000 0100 c000 0001 0000 0001 0000\n\n\"0004 0000\" = 0x00000004 = 4 d <math>\\Rightarrow</math> you have another header of length 4 long words.\n\n\"01cc 0012\" is the next 32 bit word which \\Rightarrow the number = 0xcc, the data type = 1 and the tag / event type 0x0012 = 18 d \\Rightarrow \"Go Event\"\n\nAccording to the Go Event format defined in Appendix F.7 of the manual referenced below, you can expect 3 long words.  The first word is the unix time, the next is for \"reserved\" and the last one is the number of events in the run so far. \n\n\n\n\n{| border=\"3\"  cellpadding=\"20\" cellspacing=\"0\"\n| 0004 0000\n|colspan=\"3\"|\nlength= 4\n|-\n|01cc 0012\n|tag=Event type =18(bits 16 <math>\\rightarrow</math> 31)\n|data type=1(bits 8 <math>\\rightarrow</math> 15)\n|number= 0xCC (bits 0 <math>\\rightarrow</math> 7)\n|-\n|e804 4730\n|colspan=\"3\"|\n0x4730e804 = 1194387460 d = unix time = Tue, 06 Nov 2007 22:17:40 GMT\n|-\n|0000 0000\n|colspan=\"3\"|\nreserved\n|-\n|0000 0000\n|colspan=\"3\"|\nEvent Number\n|-\n|}\n\n== Physics Event Bank==\n 0000100 0000 0000 0000 0000 000a 0000 10cc 0001\n 0000120 0004 0000 0100 c000 0001 0000 0001 0000\n 0000140 0000 0000 0003 0000 0101 0002 4c52 5343\n 0000160 0000 0000 000a 0000 10cc 0001 0004 0000\n\n{| border=\"3\"  cellpadding=\"20\" cellspacing=\"0\"\n| 000a 0000\n|colspan=\"3\"|length= 10\n|-\n|10cc 0001\n|tag=ROC # =0x0001 = 1 d (bits 16 <math>\\rightarrow</math> 31)\n|data type=10(bits 8 <math>\\rightarrow</math> 15)\n|number= 0xCC (bits 0 <math>\\rightarrow</math> 7)\n|}\n\nConsistent with appendix entry F.1\n\n== Event ID bank ==\n{| border=\"3\"  cellpadding=\"20\" cellspacing=\"0\"\n|0004 0000\n|colspan=\"3\"| 0x00000004 = 4 d = event length\n|-\n|0100 c000\n|colspan=\"3\"| 0x00 = num, 0x01 = dtype , 0xc000 =tag\n|-\n|0001 0000\n|colspan=\"3\"| =0x00000001 = 1 d = Event number\n|-\n|0000 0000\n|colspan=\"3\"| Event Classification = 0\n|-\n|0001 0000\n|colspan=\"3\"| 0x00000001 = 1 d = status summary \n|}\n\n== ROC data bank == \n{| border=\"3\"  cellpadding=\"20\" cellspacing=\"0\"\n|0003 0000\n|colspan=\"3\"| 0x00000003 = 3 d = record length\n|-\n|0101 0002\n|colspan=\"3\"| 0x01 = counter, 0x01 = 1d, 0x0002 = ROC number\n|-\n|4c52 5343\n|colspan=\"3\"| = Bank name =SCLR: 0x53 = 83 d = S , 0x43 = 67 d= C, 0x4c = 76 d = L, 0x52 = 82 d = R \n|}\n\n\n\n=Bank Names=\n\n\nIn the CODA readout list (gen_int_list.crl)  I will write a 4 letter string with the name of the bank via the command\n\n    *rol->dabufp++ = *((unsigned long*)\"SCLR\"); \n\nYou can see it (PRINTED Backwards) in the raw CODA data file at the end of line 140 using \n\n od -c v260_sclr.dat | less\n 0000000  \\0      \\0  \\0  \\0  \\0  \\0  \\0  \\b  \\0  \\0  \\0  \\b  \\0  \\0  \\0\n 0000020 243 001  \\0  \\0 002  \\0  \\0  \\0   '  \\0  \\0  \\0  \\0 001 332 300\n 0000040 004  \\0  \\0  \\0 314 001 021  \\0 377 347   0   G   x  \\0  \\0  \\0\n 0000060 001  \\0  \\0  \\0 004  \\0  \\0  \\0 314 001 022  \\0 004 350   0   G\n 0000100  \\0  \\0  \\0  \\0  \\0  \\0  \\0  \\0  \\n  \\0  \\0  \\0 314 020 001  \\0\n 0000120 004  \\0  \\0  \\0  \\0 001  \\0 300 001  \\0  \\0  \\0 001  \\0  \\0  \\0\n 0000140  \\0  \\0  \\0  \\0 003  \\0  \\0  \\0 001 001 002  \\0   R   L   C   S\n 0000160  \\0  \\0  \\0  \\0  \\n  \\0  \\0  \\0 314 020 001  \\0 004  \\0  \\0  \\0\n\n\nIt appears in reverse order at the end of line 140.\n\n=References=\n\n[[Image:Coda_1.4_manual.pdf]]\n\n[http://www.iac.isu.edu/mediawiki/index.php/Data_Acquisition Return to DAQ]"
                    }
                ]
            }
        }
    }
}