Note: Some of the notes below are out of date !!
- Every first Thursday of the month - presentations (except for May Day, meeting moved to May 8) - Every third Thursday of the month - coordination group
1. TWiki:Luminosity Working Group - used for - general project description - plans - to do list 2. Hypernews - used to answer questions of general interest to the collaboration. 3. Luminosity Group email list in Samba (with archiving) for more technical details discussed among the Luminosity Group members and other experts.
What machine parameters are available ? How is it structured ? How are 'machine parameters' stored by the LHC ? Are all parameters relevant to ATLAS ? with uncertainties ? What tools are available to obtain/transfer this information for ATLAS? How does the temporal structure of the machine parameters map onto ATLAS IOV (in time and/or Run-lumi block) Jim Cook has put DCS information into COOL. can similar mechanisms be used to put LHC machine parameters into COOL? COOL must store some combination of duration, deadtime, instantaneous luminosity delivered luminosity by Run/Lumiblock in COOL. For now, put into TRIGGER/LUMI/LBLEST/ OnlineLumi_del - OnlineLumi_inst - LiveFraction - fraction of duration when L1 accept not inhibited. The Lumi task force specifies triggers may be split into a high priority and a low priority set. It is logical that this flag come from Trigger DB -- is it implemented? Where would it appear in the trigger configuration xml file ? Bunch to bunch information will also be required - the level at which it might be needed/used in general physics analysis is unknown (analysis dependent, depends on variation in bunch density make sure the BCID of recorded events are distributed as expected, proportional to the bunch population (?) - Look for stream, trigger, priority, prescale dependence. Run Coordination issues. run_type = physics - current data is but is not number of simultaneous physics runs There's nothing in Monte Carlo about luminosity. Event header has BCID, but nothing else. A quick and dirty instantaneous luminosity might be useful.
overcounting and undercounting:
Chain of command:
Goal: Develop the method, the detector and the trigger system designs to achieve O(1%) absolute normalisation precision, and O(0.1% ) precision of the relative normalisation of event samples taken at various energies and/or using different beam species?
final state is hadrons separated by a rapidity gap containing a lepton pair. cs varies from 10^-3 to 10 nb with 1(GeV/c)/p_t^thr from .2 to 3. detector is TRT-C-wheels space. Lepton identification efficiencies and acceptances must be determined, (time variation must be controlled ) directly from the experimental data! use: Dalitz pairs, and hadronic resonances
mu = cs(inel) * L(BCID) / f(BCID) = # interactions per BCID Measure the fraction of crossings with pp interactions * P(0) = e ^ -mu = prob of no interaction (zero Counting method) * P(1) = mu * e ^ -mu = prob of one interaction (One Counting method) Direct counting # of pp interactions * Counting particles * Counting hits Use LUMAT Simulation Conclusions: * Method sensitive to bunch luminosity and not integrated luminosity * very high bunch-luminosity is likely to spoil linearity
Provenance (Noun) Where something originated or was nurtured in its early existence; Scalar - (adj) directionless magnitude; (noun) variable quantity that cannot be resolved into components. Scaler - electronic pulse counter used to count pulses that occur too rapidly to be recorded individually. Verses - plural of verse: piece of poetry, metrical text, literacture in metrical form. Versus - Against; as, John Doe versus Richard Roe; abbreviated to v. or vs.
If you get this message, TWiki you may have just lost everything you wrote.
Powered by TWiki Attention Incorrect parameters to the save script If you received a link to this topic in an e-mail or just want to look at the topic, cancel save to go to LuminosityOnlineSummary. If you were editing a topic and your login session has expired, you can get back to your edit session by pressing quickly a few times on the back button of your browser. (You need to go back several times, as there is a Shibboleth session lookup to the login server in between.) Please note that you should save edit sessions frequently from TWiki, as the session expires after one hour. This site is powered by the TWiki collaboration platform Copyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
I am entering data into the following TWiki pages (link to local latest copy):