TestPage: Difference between revisions

From Mu2eWiki
Jump to navigation Jump to search
(Replaced content with "This page has been moved to Glossary.")
Tag: Replaced
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
This page has been moved to [[Glossary]].
This page is a prototype of a glossary for Mu2e. The style of this page is taken from [https://www.mediawiki.org/wiki/Manual:Glossary https://www.mediawiki.org/wiki/Manual:Glossary].
<p>
 
 
Some questions:
 
# Do we need a glossary.  I say yes because too many simple things are, otherwise, never properly defined.
# Who needs to be part of this discussion?
# What is the scope of this document?
## Just computing terms and put the physics and detector terms elsewhere?
## Computing terms plus physics and detector terms that are encountered in day to day computing work?  The prototype is written like this.
## Do we make it more inclusive?
## Remember that what we choose must be maintainable; I think that a lot of content will unchanged for the duration of the experiment - so that reduces the burden.
# Is this the right style?  If not, what is.
# Does a link to this page belong on: [[Main_Page]]? From [[Computing]]? Other?
# For references within this page, should we encourage [[#Event]] or [[#Event|Event]]?
# We should recommend a periodic review schedule?  How often, who will do it?  It can be an offical service job.
# What process should we establish for vetting new material? This too can be a service job.
</div>
<p>
<hr>
<p>
 
This page is a glossary and acronym dictionary that covers the terms and acronyms that one will encounter when working with the Mu2e software.
For acronyms specific to the Mu2e Construction Project, see [https://mu2e.fnal.gov/atwork/workgroups/Accelerator/Acronyms.shtml MAD: The Mu2e Acronym Dictionary ].
 
 
<p>
 
 
 
 
<p>
 
== 0–9 ==
 
==A==
 
==B==
;{{Anchor|Badge}} Badge
: The plastic card issued by Fermilab with your picture and Fermilab ID number on it.  Contrast with [[#Fermilab ID|Fermilab ID]].
 
==C==
;{{Anchor|Calorimeter|CAL|Cal|ECAL|EMCAL}} Calorimeter
: The Mu2e Electromagnetic Calorimeter; one of the subsystems of the Mu2e detector.  It measures the energy of photons and electrons in the energy range of interest to Mu2e.  {{Fixme|link to more cal information}}.
;{{Anchor|CCD}}CCD
: Core Computing Division at Fermilab.  An organization with the Fermilab [[#Computing Sector|Computing Sector (CS)]].
;{{Anchor|CERN}}CERN
: A High Energy Physics lab in Geneva, Switzerland.  See the [https://home.cern CERN home page].
;{{Anchor|CLHEP}}CLHEP
: [https://proj-clhep.web.cern.ch/proj-clhep/ CLHEP: A Class Library for High Energy Physics] is a 20+ year old class library that contains classes for 3-vectors, 4-vectors, Lorentz transformations, linear algebra, Random Number engines and Random Distributions.  The GEANT4 simulation library makes extensive use of CLHEP.  Early version of Mu2e reconstruction software also used CLHEP but this is being phased out in favor of the [[#ROOT | ROOT]]  [[SMatrix | SMatrix]] package.
;{{Anchor|COMET}} COMET
: A competitor experiment, also building an experiment to look for Muon to Electron Conversion.  Located at [[JPARC]].  See also the [https://comet.kek.jp COMET Home Page].
;{{Anchor|CRV|Cosmic Ray Veto}} CRV
: The Mu2e Cosmic Ray Veto system. It is possible for a cosmic ray to interact with the Mu2e apparatus and the surrounding materials to produce a track that is indistinguishable from a conversion electron.  The purpose of the CRV is to record when cosmic rays enter the detector.  The CRV system tags events in which a cosmic ray has entered the Mu2e detector.  During data analysis Mu2e will exclude exclude tagged events.  {{Fixme|link to more CRV info}}.
;{{Anchor|CS|Computing Sector}} CS
: The Fermilab Computing Sector; has two divisions, [[#CCD | CCD ]] and [[SCD]].  See [https://computing.fnal.gov https://computing.fnal.gov]
 
==D==
;{{Anchor|Data Product|data product|data products|DataProduct}}Data Product
: The unit of data that can be read from an [[art]] format [[event-data file]].
;{{Anchor|Digi|digi|digis|DIGI}} Digi
: A software object that represents smallest unit of [[raw data]] that is read from the experiment.  Typically it contains an identifier of an electronics channel, one or two [[TDC]] values and a set of [[ADC]] values that represent a waveform.  These objects are found in [[#data product|data products]] that are collections of many digi objects; examples include CaloDigiCollection, CrvDigiCollection and StrawDigiCollection.  Digi objects can also be produced by the Mu2e [[simulation]] code.  {{Fixme| do we want links to code; better would be to drop the examples and link to a more extensive writeup}}.
 
==E==
;{{Anchor|Event|event}} Event
: When Mu2e is taking [[on-spill]] data, an event is all of the data associated with one [[proton pulse]] aimed at the [[production target]].  When Mu2e is taking [[off-spill]] data, an event is all of the data associated with the a fixed time period.  As of March 2022, the fixed time period is 100 micro-seconds.  In both cases it includes all of the [[raw data]] plus any data that is produced by processing the raw data.  Events are collected into files that reside either on disk or tape.
 
==F==
;{{Anchor|Fermilab ID}} Fermilab ID
: The number that uniquely identifies you to Fermilab.  Contrast this with the piece of plastic with your picture on it: that is your [[#Badge|Badge]].
;{{Anchor|FNAL}}FNAL
: Fermi National Accelerator Lab; the full name of Fermilab.  The lab has a [http://www.fnal.gov public home page] and a separate [https://news.fnal.gov/fermilab-at-work/ home page for employees, Users and Affliates].
 
==G==
 
==H==
;{{Anchor|Hit|hit}} Hit
: A software object that represents the calibrated form of a [[#digi|digi]].  Typically it contains a software channel id, the calibrated time at which the hit began and a calibrated waveform describing the shape of the pulse.  It may also contain other information that is useful to the algorithms that process hits. {{Fixme|add a reference to more information and/or to code}}.
 
==I==
 
==J==
 
==K==
;{{Anchor|Kerberos}} Kerberos
: A secure single sign on system that is used to access many resources at Fermilab.  Some other resources are accessed using the [[SSO]] system and others using [[certificates]].
;{{Anchor|Kerberos Principal|kerberos principal}} Kerberos Principal
: Your username within the [[Kerberos]] system.  You use it to [[ComputingLogin |log into the Mu2e interactive computers]].
 
==L==
;{{Anchor|Luminoisity|lunminosity|lumi}} Luminosity
: This is an ill-defined term that has been used in the past to refer to the number of muons stopped in the stopping target, either per event or integrated over many events.  The preferred word is now [[#Intensity| Intensity]] but some older documents use luminosity. The reason for the change is that the word luminosity has a well defined meaning in the collider community, which is quite different than the meaning in Mu2e.
 
==M==
;{{Anchor|muon-upstream}} muon-upstream
: In the Mu2e coordinate system this is in the +z direction, which is the direction of the muon beam when it is in the [[#PS|PS]] and the [[#DS|DS]]. Contrast with [[#proton-upstream | proton-upstream]].  {{Fixme|Link to coordinate system.}}.
;{{Anchor|micro bunch|micro-bunch|micronbunch}} Micro bunch
: This term is now obsolete and has been replaced by [[#proton pulse|proton pulse]]. Some older documents use the obsolete name.
 
==N==
 
==O==
 
==P==
;{{Anchor|Product}}Product
:  Either a [[#UPS Product| UPS Product]] or a [[#Data Product| Data Product]]; hopefully the meaning will be clear from the context.
;{{Anchor|proton-upstream}} proton-upstream
: In the Mu2e coordinate system this is in the -z direction, which is approximately the direction of the proton beam. Contrast with [[#muon-upstream | muon-upstream]].  {{Fixme|Link to coordinate system.}}.
;{{Anchor|Pulse|pulse|proton pulse|Proton pulse}} Proton Pulse
: The group of protons extracted during one turn of the [[Delivery Ring]] and sent to the Mu2e production target. During [[on-spill]] running, one pulse arrives at the production target approximately every 1694 ns.  In some early Mu2e documents this was called a [[#micro bunch|micro bunch]]; the term proton pulse is preferred.
 
==Q==
 
==R==
;{{Anchor|ROOT}} ROOT
: A [https://root.cern.ch software package for Scientific Data Analysis]] developed at [[CERN]]. It is also used as the underlying technology [[art]] format [[event-data files]].  As if March 2022, Mu2e has two data analysis environments based on ROOT, [[#TrkAna]] and [[#Stntuple]].  See also: [https://root.cern/doc/master/classes.html the ROOT Class Index].
 
==S==
;{{Anchor|SINDRUM|SINDRUM II|SINDRUM-II}} SINDRUM
: The previous best limit on muon to electron conversion was obtained by the [https://inspirehep.net/literature/1925834 SINDRUM II experiment], an experiment at [[PSI]].
 
==T==
;{{Anchor|TS}}TS
: The Transition Solenoid. {{Fixme|add reference.  Maybe the right answer is to refer to a labelled diagram.  We can link to it from many other places.}}.
;{{Anchor|TS}}TSd
: The muon-downstream arc of the [[TS]].
;{{Anchor|TS}}TSu
: The muon-upstream arc of the [[TS]].
 
==U==
;{{Anchor|Upstream|upstream|up-stream}} Upstream
: An ambiguous term meaning either [[#proton-upstream | proton-upstream]] or [[#muon-upstream|muon-upstream]]; hopefully it will usually be clear from the context which is intended. {{Fixme|Add the same for downstream}}.
;{{Anchor|UPS Product}} UPS Product
: A software package distributed using the [[UPS]] system; examples include the C++ compiler, [[art]], [[ROOT]], and [[GEANT4]].
 
==V==
 
==W==
 
==X==
 
==Y==
 
==Z==

Latest revision as of 18:50, 24 March 2022

This page has been moved to Glossary.

Retrieved from "http://mu2ewiki.fnal.gov/w/index.php?title=TestPage&oldid=19991"