Glossary: Difference between revisions
Jump to navigation
Jump to search
m (→E: fix typo in anchor to event_window) |
|||
(64 intermediate revisions by 4 users not shown) | |||
Line 62: | Line 62: | ||
;{{Anchor|boost}} boost | ;{{Anchor|boost}} boost | ||
: Freeware c++ supplemental [https://www.boost.org/ libraries] for common algorithms. | : Freeware c++ supplemental [https://www.boost.org/ libraries] for common algorithms. | ||
;{{Anchor|BO|Booster}} Booster (BO) | |||
: An element of the Fermilab accelerator complex that is used to deliver proton beam to Mu2e. It receives beam from the [[#LINAC|LINAC]] and sends it to the [[#Main Injector|Main Injector]]. See [[#Booster Cycle|Booster Cycle]] and [[ProtonBeamIntro]]. | |||
;{{Anchor|Booster Batch|booster batch}} Booster Batch | |||
: The unit of beam that is accelerated in the [[#Booster|Booster]] and transferred out of the Booster. In normal Mu2e operations it will consist of 80 bunches. See [[#Booster Cycle|Booster Cycle]] and [[ProtonBeamIntro]]. | |||
;{{Anchor|Booster Cycle}} Booster Cycle | |||
: The repeating cycle of the Fermilab [[#Booster|Booster]]; within one cycle it receives beam from the [[#LINAC|LINAC]], accelerates it to 8 GeV kinetic energy and sends it to one of the [[#Recycler|Recycler]], the [[#Main Injector|Main Injector]] or to the booster neutrino beam target. Beam destined for Mu2e goes to the Recycler. One booster cycle has a duration of 1/15 seconds. See [[ProtonBeamIntro]]. | |||
;{{Anchor|BTrk|btrk}} BTrk | ;{{Anchor|BTrk|btrk}} BTrk | ||
Line 70: | Line 79: | ||
==C== | ==C== | ||
;{{Anchor|Calorimeter|CAL|Cal|ECAL|EMCAL}} Calorimeter | ;{{Anchor|Calorimeter|calorimeter|CAL|Cal|ECAL|EMCAL}} Calorimeter | ||
: The Mu2e [[CalorimeterIntro|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. | : The Mu2e [[CalorimeterIntro|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. | ||
Line 77: | Line 86: | ||
;{{Anchor|CCD}}CCD | ;{{Anchor|CCD}}CCD | ||
: Core Computing Division at Fermilab. | : Core Computing Division at Fermilab. Prior to October 2022, CCD was an organization within the Fermilab [[#Computing Sector|Computing Sector (CS)]]. It managed Windows, business systems, printers, networking, security. Succeeded by the [[#ITD|ITD]]. | ||
;{{Anchor|CD|CD}} CD, CD-0, CD-1, CD-2, CD-3, CD-4 | ;{{Anchor|CD|CD}} CD, CD-0, CD-1, CD-2, CD-3, CD-4 | ||
: Critical Decision. Major [https://opss.fnal.gov/critical-decision-overview approval points] in the progress of a [[#DOE|DOE]] [[#project|project]] | : Critical Decision. Major [https://opss.fnal.gov/critical-decision-overview approval points] in the progress of a [[#DOE|DOE]] [[#project|project]] | ||
;{{Anchor|CDR|Conceptual Design Report}} CDR | |||
: Conceptual Design Report. A fairly advanced conceptual desicription of the experiment, which has been superseded by the Technical Design Report ([[#TDR|TDR]]) | |||
;{{Anchor|CE|ce|conversion electron}} CE | ;{{Anchor|CE|ce|conversion electron}} CE | ||
Line 87: | Line 99: | ||
;{{Anchor|CERN}}CERN | ;{{Anchor|CERN}}CERN | ||
: A High Energy Physics lab in Geneva, Switzerland. See the [https://home.cern CERN home page]. | : A High Energy Physics lab in Geneva, Switzerland. See the [https://home.cern CERN home page]. | ||
;{{Anchor|Certificate|certificate}} Certificate | |||
: A method of user authentication that is needed to access some computing resources. For example certificates are used to submit grid jobs and to write information to [[#SAM|SAM]]. For additional information see [https://mu2ewiki.fnal.gov/wiki/Authentication#Certificate]. | |||
;{{Anchor|CFO}} CFO | |||
: Command Fan Out. Hardware component of the online DAQ ([[#TDAQ|TDAQ]]) that provides the interface between the command host and the [[#DTC|DTC]]s. The CFO drives run plan, synchronization, and timing for the online DAQ. (For additional information, see [https://mu2e-docdb.fnal.gov/cgi-bin/sso/ShowDocument?docid=5619].) | |||
;{{Anchor|CLFV}} CLFV | ;{{Anchor|CLFV}} CLFV | ||
Line 101: | Line 119: | ||
;{{Anchor|COMET}} COMET | ;{{Anchor|COMET}} COMET | ||
: A competitor experiment, also building an experiment to look for Muon to Electron Conversion. Located at [[ | : A competitor experiment, also building an experiment to look for Muon to Electron Conversion. Located at [[#J-PARC|J-PARC]]. See also the [https://comet.kek.jp COMET Home Page]. | ||
;{{Anchor|CORSICA|corsica}} CORSICA | ;{{Anchor|CORSICA|corsica}} CORSICA | ||
: A [https://www.iap.kit.edu/corsika/ software package] for generating cosmic | : A [https://www.iap.kit.edu/corsika/ software package] for generating cosmic ray air showers for simulation. | ||
;{{Anchor|CPR|cpr|CalPatRec}} CPR, CalPatRec | ;{{Anchor|CPR|cpr|CalPatRec}} CPR, CalPatRec | ||
: CalPatRec is a tracker helix pattern recogniton algorithm, where the hit search is seeded by a calorimeter cluster | : CalPatRec is a tracker helix pattern recogniton algorithm, where the hit search is seeded by a calorimeter cluster. See also [[#TPR|TPR]] | ||
;{{Anchor|CRR}} CRR | ;{{Anchor|CRR}} CRR | ||
: Construction | : Construction Readiness Review. A review of a [[#project|project]] component, such as an electronics board, to make sure the design is complete and tested, before the component construction begins. | ||
;{{Anchor|CRS}} CRS | ;{{Anchor|CRS}} CRS | ||
: Cosmic Ray Shield, and obsolete name for the [[#CRV|CRV]] | : Cosmic Ray Shield, and obsolete name for the [[#CRV|CRV]] | ||
;{{Anchor|CRV|Cosmic Ray Veto}} CRV | |||
: The Mu2e [[CosmicRayVetoIntro|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. During data analysis Mu2e will exclude exclude tagged events. | |||
;{{Anchor|cry|CRY}} CRY | ;{{Anchor|cry|CRY}} CRY | ||
Line 122: | Line 140: | ||
;{{Anchor|CS|Computing Sector}} CS | ;{{Anchor|CS|Computing Sector}} CS | ||
: The Fermilab Computing Sector | : The Fermilab Computing Sector. Prior to October 2022, the organization within Fermilab that supported our scientific computing needs. The successor organization is [[#CSAI|CSAI]]. It had two divisions, [[#CCD | CCD ]] and [[#SCD|SCD]]. See [https://computing.fnal.gov https://computing.fnal.gov] | ||
;{{Anchor|CSAI|CSAID}} CSAID | |||
: Computational Science and AI Directorate; since Octobber 2022, the organization within Fermilab that supports our scientific computing needs. This organization succeeds [[#CS|CS]]. The divisions within CSAI are: [[#SCSSD|SCSSD]], [[#DSSLD|DSSLD]] and [[#RTPSD|RTPSD]]. | |||
;{{Anchor|CsI}} CsI | ;{{Anchor|CsI}} CsI | ||
Line 132: | Line 153: | ||
==D== | ==D== | ||
;{{Anchor|Data Product|data product|data products|DataProduct}}Data Product | ;{{Anchor|Data Product|data product|data products|DataProduct}}Data Product | ||
: The unit of data that can be read from an [[#art|''art'']] format [[#event-data |event-data file]]. | : The unit of data that can be written to or read from an [[#art|''art'']] format [[#event-data |event-data file]]. | ||
;{{Anchor|DAQ}} DAQ | ;{{Anchor|DAQ}} DAQ | ||
: Data AQuisition, the process of reading out the low-level detector data and | : Data AQuisition, the process of reading out the low-level detector data and building it into an [[#Event|event]] on disk. In Mu2e, the DAQ system is built around the [[#artdaq|artdaq]] and [[#OTSDAQ|OTSDAQ]] packages. | ||
;{{Anchor| | ;{{Anchor|DB}} DB | ||
: Database | : Database | ||
Line 144: | Line 165: | ||
;{{Anchor|DCS}} DCS | ;{{Anchor|DCS}} DCS | ||
: Detector Control System. A set of online [[Detector_Control_System|software systems]] and procedures used to control and monitor the detector and [[#DAQ|DAQ]] components. | : Detector Control System. A set of online [[Detector_Control_System|software systems]] and procedures used to control and monitor the detector and [[#DAQ|DAQ]] components. The underlying technology is [[#EPICS|EPICS]] and the DCS system is sometimes called the "EPICS System". It is also called the [[#SlowControl|Slow Control]] system. | ||
;{{Anchor|DDR}} DDR | ;{{Anchor|DDR}} DDR | ||
Line 150: | Line 171: | ||
;{{Anchor|degrader}} degrader | ;{{Anchor|degrader}} degrader | ||
:A foil near the entrance of the [[#DS|DS]] that can be moved into the beam, to reduce the beam intensity for calibrations. | :A foil near the entrance of the [[#DS|DS]] that can be moved into the beam, to reduce the beam intensity for use in calibrations or to reduce the momentum of beam particles for use in calibrations. | ||
;{{Anchor|DeM}} DeM | |||
:Acronym referring to the track fit hypothesis of a downstream going negative electron. | |||
;{{Anchor|DES|Downstream External Shielding}} DES | |||
:Downstream External Shielding: The muon beamline shielding external to the Downstream Transport Solenoid ([[#TSd|TSd]]) and the Detector Solenoid ([[#DS|DS]]). | |||
;{{Anchor|Delivery Ring}} Delivery Ring | |||
: A component of the Fermilab accelerator complex that delivers [[#proton pulse|proton pulses]] to the Mu2e production target. The Delivery Ring is a synchrotron and its period sets the time between pulses arriving at the Mu2e [[#production target|production target]]. For additional information see [[ProtonBeamIntro]]. | |||
;{{Anchor|Digi|digi|digis|DIGI}} Digi | ;{{Anchor|Digi|digi|digis|DIGI}} Digi | ||
Line 166: | Line 196: | ||
;{{Anchor|DOE}} DOE | ;{{Anchor|DOE}} DOE | ||
: The United States Department of Energy, which funds Fermilab. See [https://www.energy.gov]. | : The United States Department of Energy, which funds Fermilab. See [https://www.energy.gov]. | ||
;{{Anchor|Downstream|downstream|down-stream}} Downstream | |||
: An ambiguous term meaning the opposite of another ambiguous term. See the definition of [[#upstream|upstream]]. | |||
;{{Anchor|DPA|Displacements Per Atom}} DPA | |||
: Displacements Per Atom. A measure of radiation exposure. | |||
;{{Anchor|DQM}} DQM | ;{{Anchor|DQM}} DQM | ||
: Data Quality Monitor. A process, online and offline, to histogram data content to record data status and monitor for quality. | : Data Quality Monitor. A process, [[#online|online]] and [[#offline|ofline]], to histogram data content to record data status and monitor for quality. | ||
;{{Anchor|DS}} DS | ;{{Anchor|DS}} DS | ||
: Detector Solenoid. The [[DetectorSolenoidIntro|magnet]] surrounding the tracker and calorimeter. | : Detector Solenoid. The [[DetectorSolenoidIntro|magnet]] surrounding the tracker and calorimeter. | ||
;{{Anchor|DSSLD}} DSSLD | |||
: Data Science, Simulation and Learning Division. Since October 2022, a division within the Fermilab [[#CSAI|CSAI]]. This organization supports art, Geant4 and the distribution of UPS products by the Scisoft team. It is the home organization to many of the scientistic staff within [[#CSAI|CSAI]]. | |||
;{{Anchor|DTC}} DTC | ;{{Anchor|DTC}} DTC | ||
Line 194: | Line 233: | ||
;{{Anchor|EPICS|epics}}EPICS | ;{{Anchor|EPICS|epics}}EPICS | ||
: A freeware [https://docs.epics-controls.org/en/latest/guides/EPICS_Intro.html real-time monitoring system]. In Mu2e, used for online detector monitoring and control. | : A freeware [https://docs.epics-controls.org/en/latest/guides/EPICS_Intro.html real-time monitoring system]. In Mu2e, it is used for online detector monitoring and control. See [[#DCS|DCS]] and [[#SlowControl|Slow Control]]. | ||
;{{Anchor|ESS|Electrostatic Septum}}ESS | |||
: Electrostatic Septum, part of the Resonent Extraction System. (An overview may be found in the [[#TDR|TDR]] section 4.6.) | |||
;{{Anchor|Eventacc|eventacc}} Event (accelerator) | |||
: In the Fermilab accelerator complex, some of the timing and control signals are referred to as "events". | |||
;{{Anchor|Event|event}} Event (DAQ) | |||
: All of the data associated with some time interval; it includes the [[#raw data|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. In casual use, the word event may refer either to the time period or to the data associated with that time period. In the [[#DAQ|DAQ]] community the time period is called an [[#Event Window|Event Window]] and the data is called an event. When Mu2e is taking [[#onspill|on-spill]] data, an event is all of the data associated with one [[#proton pulse|proton pulse]]. When Mu2e is taking [[#off-spill|off-spill]] data, an event is all of the data associated with a time period that's chosen considering several trade-offs; as of March 2022, the duration of the time period is defined to be 100 micro-seconds. | |||
;{{Anchor|Event data|Event-data|event data|event-data}} Event-data | ;{{Anchor|Event data|Event-data|event data|event-data}} Event-data | ||
: A collective noun referring to both data and simulated events. Here "data" refers to information that comes from | : A collective noun referring to both data and simulated events. Here "data" refers exclusively to information that comes from measurements made by experiments, test beams or test stands. Simulated information should not be named "data". The use of the terms "real data" and "simulated data", as synonyms for data and simulated events, is discouraged but is in wide use. | ||
;{{Anchor|Event Window|event window}} Event Window | |||
: A time interval inside the [[#DAQ|DAQ]] system. All data measured during this time interval will be organized into one [[#event|event]]. | |||
;{{Anchor|EWM|ewm|Event Window Marker}} Event Window Marker (EWM) | |||
: A timing signal distributed throughout the [[#DAQ|DAQ]] system that signals when a new [[#Event Window|Event Window]] begins. | |||
;{{Anchor|EWT|ewt|Event Window Tag}} Event Window Tag (EWT) | |||
: A 48-bit integer that uniquely identifies each [[#event_window|Event Window]] over the lifetime of Mu2e. | |||
;{{Anchor|Extinction|extinction}} Extinction | |||
: The ratio of the number of out-of-time protons to the number of in-time protons is called the extinction. Here, in-time refers to protons that arrive at the production target within a proton pulse from the [[#Delivery Ring|Delivery Ring]] and out-of-time refers to protons that arrive between two pulses. Out-of-time protons can produce false signals, principally via the mechanism of [[#RPC|RPC]]. Mu2e must achieve an extinction of <math>10^{-10}</math> in order to reduce these backgrounds to an acceptable level. | |||
;{{Anchor| | ;{{Anchor|ExMon|EXTMON|extmon}} EXTMON | ||
: | : Extinction Monitor. A device to monitor the level of [[#extinction|extinction]] in the proton beam. See [[ExtinctionMonitorIntro]]. | ||
==F== | ==F== | ||
Line 267: | Line 325: | ||
: A freeware software versioning [[GitHubWorkflow|tool]]. Each large conceptual code package is kept in its own repository ([[#repo|repo]]). | : A freeware software versioning [[GitHubWorkflow|tool]]. Each large conceptual code package is kept in its own repository ([[#repo|repo]]). | ||
;{{Anchor|github}} | ;{{Anchor|GitHub|github}} GitHub | ||
: A free (for | : A free (for Mu2e) [https://github.com/Mu2e web site] where we can keep our [[#git|git]] repositories and manage them. | ||
;{{Anchor|GNN}} GNN | ;{{Anchor|GNN}} GNN | ||
Line 279: | Line 337: | ||
;{{Anchor|Hit|hit}} Hit | ;{{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}}. | : 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}}. | ||
;{{Anchor|HPC}} HPC | ;{{Anchor|HPC}} HPC | ||
: High Performance Computing, a generic term for large, uniform [[HPC|computing centers]] (supercomputers), such as systems at [[#NERSC|NERSC]] and [[#ALCF|ALCF]] | : High Performance Computing, a generic term for large, uniform [[HPC|computing centers]] (supercomputers), such as systems at [[#NERSC|NERSC]] and [[#ALCF|ALCF]] | ||
;{{Anchor|HRS|Heat and Radiation Shield}} HRS | |||
: Heat and Radiation Shield. The shield that surrounds the production target to protect the superconducting Production Solenoid ([[#PS|PS]]) | |||
==I== | ==I== | ||
;{{Anchor|IFB}} IFB | ;{{Anchor|IFB}} IFB | ||
: Instrumentation Feedthrough Bulkhead. A [[MuonBeamlineIntro|plate]] at the end of the [[#DS|DS]], maintaining the DS | : Instrumentation Feedthrough Bulkhead. A [[MuonBeamlineIntro|plate]] at the end of the [[#DS|DS]], maintaining the DS vacuum and providing a path for the services and signals between vacuum and hall air. | ||
;{{Anchor|IFDH|ifdh|ifdhc}} ifdh | ;{{Anchor|IFDH|ifdh|ifdhc}} ifdh | ||
: Intensity Frontier Data Handling. A set of scripts in a [[#UPS product|UPS product]] to ensure efficient transfer of data files between [[Grids|grids]] and [[Dcache|dCache]], and other places. Used by Mu2e. | : Intensity Frontier Data Handling. A set of scripts in a [[#UPS product|UPS product]] to ensure reliable and efficient transfer of data files between [[Grids|grids]] and [[Dcache|dCache]], and other places. Used by Mu2e. | ||
;{{Anchor|INFN}} INFN | ;{{Anchor|INFN}} INFN | ||
: [https://www.presid.infn.it/index.php/it/ Istituto Nazionale Fisica Nucleare]. The governmental body overseeing HEP in Italy. | : [https://www.presid.infn.it/index.php/it/ Istituto Nazionale Fisica Nucleare]. The governmental body overseeing HEP in Italy. | ||
;{{Anchor|Intensity|intensity}} Intensity | |||
: This term has several different meanings. In the future we will define and adopt more precise language to distinguish these meanings. For now you need to interpret the meaning from the context. In the analysis community, intensity usually refers to the number of muons that stop in the stopping target, or a measurement that stands as a proxy for that number; it may refer to the [[#pulse|pulse]] by pulse value or it may refer to the sum over a longer period of time. See also [[#STM|STM]] and [[#Caphri|CAPHRI]]. Alternatively, intensity may refer to the number of protons in a single [[#proton pulse|proton pulse]]; the related term [[#POT|POT]] is used as the sum over a longer period of time. See also [[#PBI|PBI]]. | |||
;{{Anchor|ORC}} IOC | ;{{Anchor|ORC}} IOC | ||
Line 297: | Line 362: | ||
;{{Anchor|IPR}} IPR | ;{{Anchor|IPR}} IPR | ||
: Independent Project Review | : Independent Project Review. Part of the process by which the [[#DOE|DOE]] monitors the Mu2e construction project. | ||
;{{Anchor|IPA}} IPA | ;{{Anchor|IPA}} IPA | ||
: Inner Proton Absorber. | : Inner Proton Absorber. A plastic absorber inside the [[#DS|DS]], downstream of the [[#stopping target|stopping target]] and upstream of the [[#tracker|tracker]]; intended to prevent protons emitted from the target from aging the tracker. | ||
;{{Anchor|ITD}} ITD | |||
: The Fermilab Information Technology Division. Since October 2022, the successor organization to the [[#CCD|CCD]]. It manages the hardware for scientific computing, Windows, business systems, printers, networking, security. | |||
==J== | ==J== | ||
Line 306: | Line 374: | ||
;{{Anchor|jenkins|Jenkins}} Jenkins | ;{{Anchor|jenkins|Jenkins}} Jenkins | ||
: [[Jenkins]] is infrastructure to run software builds on multiple platforms in parallel. It is managed by [[#SCD|SCD]] and used my Mu2e and other experiements. | : [[Jenkins]] is infrastructure to run software builds on multiple platforms in parallel. It is managed by [[#SCD|SCD]] and used my Mu2e and other experiements. | ||
;{{Anchor|JPARC|J-PARC}} J-PARC | |||
: Japan Proton Accelerator Research Complex. An HEP lab in Japan that hosts many HEP experiments, including [[#COMET|COMET]], a competitor to Mu2e. For more information see [https://j-parc.jp/c/en/ their home page]. | |||
==K== | ==K== | ||
;{{Anchor|Kerberos}} Kerberos | ;{{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]]. | : A secure single sign on system that is used to access many resources at Fermilab. Some other resources are accessed using the [[#SSO|SSO]] system and others using [[#certificate|certificates]]. | ||
;{{Anchor|Kerberos Principal|kerberos principal}} Kerberos Principal | ;{{Anchor|Kerberos Principal|kerberos principal}} Kerberos Principal | ||
: Your username within the [[#Kerberos|Kerberos]] system. You use it to [[ComputingLogin |log into the Mu2e interactive computers]]. | : Your username within the [[#Kerberos|Kerberos]] system. You use it to [[ComputingLogin |log into the Mu2e interactive computers]]. | ||
Line 316: | Line 387: | ||
;{{Anchor|L2|L3}} L2, L3 | ;{{Anchor|L2|L3}} L2, L3 | ||
: Level-2 Manager. A [[#DOE|DOE]] [[#project|project]] will have level-2 managers for major project components, who in turn may appoint level-3 managers for smaller components. | : Level-2 Manager. A [[#DOE|DOE]] [[#project|project]] will have level-2 managers for major project components, who in turn may appoint level-3 managers for smaller components. The Mu2e web site documents the [https://mu2e.fnal.gov/atwork/project/L2SubProjects.shtml Level-2 sub-projects] within the [https://mu2e.fnal.gov/atwork/project/index.shtml Mu2e Construction Project]. | ||
;{{Anchor|LINAC}} LINAC | |||
: Linear Accelerator. An element of the Fermilab accelerator complex that is used to deliver proton beam to Mu2e. | |||
;{{Anchor|LRU}} LRU | ;{{Anchor|LRU}} LRU | ||
: Light Response Uniformity. A measure of consistentcy | : Light Response Uniformity. A measure of consistentcy along the length of a [[#calorimeter|calorimeter]] crystal. | ||
;{{Anchor|Luminoisity|lunminosity|lumi}} Luminosity | ;{{Anchor|Luminoisity|lunminosity|lumi}} Luminosity | ||
: | : In the past some people on Mu2e used this term 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 and it is still in common use. The reason for the change is that the word luminosity has a well defined meaning in the collider community that is quite different than the meaning in Mu2e. | ||
;{{Anchor|LY}} LY | ;{{Anchor|LY}} LY | ||
Line 343: | Line 417: | ||
;{{Anchor|MC|Monte Carlo}} MC (Monte Carlo) | ;{{Anchor|MC|Monte Carlo}} MC (Monte Carlo) | ||
: The computer codes used to simulate the response of Mu2e detector to the many physics processes of interest use Monte Carlo methods, a class of computing techniques that uses random sampling to produce numerical results. | : The computer codes used to simulate the response of Mu2e detector to the many physics processes of interest use Monte Carlo methods, a class of computing techniques that uses random sampling to produce numerical results. | ||
;{{Anchor|MI|Main Injector}} MI (Main Injector) | |||
: An element of the Fermilab accelerator complex. It is not used to delivery proton beam Mu2e but the delivery of beam to Mu2e follows a repeating pattern called an [[#MI Cycle|MI Cycle]]. | |||
;{{Anchor|MI Cycle|Main Injector Cycle}} MI Cycle | |||
: A repeating series of operations that involves the Main Injector (MI) and related elements of the accelerator complex. Mu2e will share beam with NOvA, and later with DUNE; during normal operations an MI cycle will consist of 21 or 22 [[#Booster Cycle|Booster Cycles]], during which both Mu2e and NOvA get beam. See [[ProtonBeamIntro]]. | |||
;{{Anchor|micro bunch|micro-bunch|micronbunch}} Micro bunch | ;{{Anchor|micro bunch|micro-bunch|micronbunch}} Micro bunch | ||
Line 364: | Line 444: | ||
;{{Anchor|Mu2e-II|Mu2eII|mu2eii}} Mu2eII, Mu2e-II | ;{{Anchor|Mu2e-II|Mu2eII|mu2eii}} Mu2eII, Mu2e-II | ||
: A proposed [https://mu2eiiwiki.fnal.gov/wiki/Mu2e-II successor] to the Mu2e experiment | : A proposed [https://mu2eiiwiki.fnal.gov/wiki/Mu2e-II successor] to the Mu2e experiment | ||
;{{Anchor|Mu2e Offline Software}} Mu2e Offline Software | |||
: A collective noun for all of the Mu2e software that is normally run [[#Offline|offline]]. Most of this software is kept in git repositories at the [https://github.com/Mu2e Mu2e GitHub organization]. | |||
;{{Anchor|muon-upstream}} muon-upstream | ;{{Anchor|muon-upstream}} muon-upstream | ||
: In the | : In the direction of the muon beam. Most of the time this means 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|Muse|muse}} Muse | ;{{Anchor|Muse|muse}} Muse | ||
Line 382: | Line 465: | ||
;{{Anchor|Offline|offline}} Offline | ;{{Anchor|Offline|offline}} Offline | ||
: This term has two meanings. Generically it refers to all Mu2e software and workflows that usually are run in computer centers, university computing resources, laptops and other resources outside of the Mu2e building. Specifically it refers to a software repository, named [https://github.com/Mu2e/Offline Offline], located in the [https://github.com/Mu2e Mu2e GitHub organization]; it contains the main reconstruction and simulation codes for Mu2e. See also [[Mu2e Offline Software|Mu2e Offline Software]]. | : This term has two meanings. Generically it refers to all Mu2e software and workflows that usually are run in computer centers, university computing resources, laptops and other resources outside of the Mu2e building. Specifically it refers to a software repository, named [https://github.com/Mu2e/Offline Offline], located in the [https://github.com/Mu2e Mu2e GitHub organization]; it contains the main trigger, calibration, reconstruction and simulation codes for Mu2e. Contrast with [[#online|online]]. See also [[#Mu2e Offline Software|Mu2e Offline Software]]. | ||
;{{Anchor|offspill}} offspill | ;{{Anchor|offspill|off-spill}} offspill | ||
: | : A time period in which Mu2e is taking data but no beam is present. During offspill periods, Mu2e will collect cosmic ray data and calibration data. Contrast with [[#onspill|onspill]]. Offspill refers both to the offspill period within an [[#MI cycle|MI cycle]] and to extended offspill periods when the accelerator off. See [[TriggerDAQIntro|TDAQ intro]] and [[ProtonBeamIntro|proton beamline]]. | ||
;{{Anchor|Online|online}} Online | ;{{Anchor|Online|online}} Online | ||
: Software and workflows that are run on the [[#TDAQ|TDAQ]] resources in the Mu2e building. This includes [[#OTS|OTS]], [[#artdaq|artdaq]], [[#DCS|DCS]], the online component of [[#DQM|DQM]]. It excludes [[#RDM|RDM]], which is developed and operated by the [[#Offline|Offline]] group. | : Software and workflows that are run on the [[#TDAQ|TDAQ]] resources in the Mu2e building. This includes [[#OTS|OTS]], [[#artdaq|artdaq]], [[#DCS|DCS]], the online component of [[#DQM|DQM]]. It excludes [[#RDM|RDM]], which is developed and operated by the [[#Offline|Offline]] group. Contrast with [[#offline|offline]]. | ||
;{{Anchor|onspill|on-spill}} onspill | ;{{Anchor|onspill|on-spill}} onspill | ||
: The data-taking time period related to a [[# | : The data-taking time period related to a continuous sequence of [[#proton pulse|proton pulses]]; or the data taken during this time; or other activities related to this time. Contrast with [[#offspill|offspill]]. See [[TriggerDAQIntro|TDAQ intro]] and [[ProtonBeamIntro|proton beamline]]. | ||
;{{Anchor|OOT}} OOT | ;{{Anchor|OOT}} OOT | ||
: Out of Time | : Out of Time; not within a specified time window. | ||
;{{Anchor|OOT}} OOT | ;{{Anchor|OOT}} OOT | ||
Line 416: | Line 499: | ||
==P== | ==P== | ||
;{{Anchor| | ;{{Anchor|PBI}} PBI | ||
: Proton Bunch Intensity. The number of protons in a single [[#proton pulse|proton pulse]]. It should have been called Proton Pulse Intensity but the acronym was defined long ago and has stuck. There is a large variation in PBI over the course of a [[#spill|spill]]. | |||
;{{Anchor|PCB}} PCB | |||
: Printed Circuit Board | : Printed Circuit Board | ||
Line 440: | Line 526: | ||
: Either a [[#UPS Product| UPS Product]] or a [[#Data Product| Data Product]]; hopefully the meaning will be clear from the context. | : Either a [[#UPS Product| UPS Product]] or a [[#Data Product| Data Product]]; hopefully the meaning will be clear from the context. | ||
;{{Anchor|Production Target| production target}} Production Target | ;{{Anchor|Production Target|production target}} Production Target | ||
: The target inside the Mu2e [[#PS|PS]]; protons from the accelerator complex hit this target to produce pions that decay to muons. This is the source of the Mu2e muon beam. See also [[ProductionTargetIntro]]. | : The target inside the Mu2e [[#PS|PS]]; protons from the accelerator complex hit this target to produce pions that decay to muons. This is the source of the Mu2e muon beam. See also [[ProductionTargetIntro]]. | ||
;{{Anchor|PTSM}} PTSM | |||
: Production Target Scanning Monitor. A proposed Mu2e subsystem. If installed, it will be located downstream of the PS and will be used during beam commissioning to ensure that the proton beam is properly aligned with the [[#production target|production target]]. | |||
;{{Anchor|Pulse|pulse|proton pulse|Proton pulse}} Proton Pulse | ;{{Anchor|Pulse|pulse|proton pulse|Proton pulse}} Proton Pulse | ||
: The | : The protons extracted during one turn of the [[#Delivery Ring|Delivery Ring]] and delivered to the Mu2e production target. During [[#on-spill|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. | ||
;{{Anchor|proton-upstream}} proton-upstream | ;{{Anchor|proton-upstream}} proton-upstream | ||
Line 451: | Line 540: | ||
;{{Anchor|PS}} PS | ;{{Anchor|PS}} PS | ||
: Production Solenoid. The [[ProductionSolenoidIntro|magnet]] surrounding the [[#Production Target|production target]], the first step in steering muons into the beamline. | : Production Solenoid. The [[ProductionSolenoidIntro|magnet]] surrounding the [[#Production Target|production target]], the first step in steering muons into the beamline. | ||
;{{Anchor|PSI}} PSI | |||
: The [https://www.psi.ch/en Paul Sherrer Institut]. A research facility in Switzerland that is the home of the [[#SINDRUM-II|SINDRUM-II]] experiment. | |||
;{{Anchor|PV}} PV | ;{{Anchor|PV}} PV | ||
: Process Variable. A Variable monitored in [[#EPICS|EPICS]] such as temperature or voltage. | : Process Variable. A Variable monitored in [[#EPICS|EPICS]] such as temperature or voltage. | ||
;{{Anchor|Pulse|pulse}} Pulse | |||
: Usually refers to a [[#proton pulse|proton pulse]] but may also refer to the muon pulse that follows each proton pulse. | |||
==Q== | ==Q== | ||
Line 459: | Line 554: | ||
;{{Anchor|QC}} QC | ;{{Anchor|QC}} QC | ||
: Quality Control | : Quality Control | ||
;{{Anchor|QPM}} QPM | |||
: Quench Protection and Monitoring system. ([https://lss.fnal.gov/archive/2021/pub/fermilab-pub-21-637-sqms-td.pdf fermilab-pub-21-637]) | |||
==R== | ==R== | ||
;{{Anchor|Raw Data|Raw Data|raw data}} Raw data | |||
: The low level data collected from the experiment by the [[#DAQ|DAQ]] system. The data is in a highly compressed format that can be unpacked into collections of [[#digi|digis]]. For packet definitions see [https://mu2e-docdb.fnal.gov/cgi-bin/sso/ShowDocument?docid=4914 Mu2e-doc-4914]. | |||
;{{Anchor|raw data file}} Raw data file | |||
: A file written by the [[#TDAQ|TDAQ]] system. It contains raw data plus additional data products that describe why the [[#trigger|trigger]] system accepted the event. | |||
;{{Anchor|RDM}} RDM | ;{{Anchor|RDM}} RDM | ||
:Raw Data Mover. The working name for the system of scripts which copies raw data from the [[#DAQ|DAQ]] disks to the offline [[#dCache|dCache]] disks and tape, and declares the file metadata. | :Raw Data Mover. The working name for the system of scripts which copies raw data from the [[#DAQ|DAQ]] disks to the offline [[#dCache|dCache]] disks and tape, and declares the file metadata. | ||
;{{Anchor|RR|Recycler}} Recycler (RR) | |||
: An element of the Fermilab accelerator complex that is used to deliver beam to Mu2e. It receives protons from the [[#Booster|Booster]], rebunches them and sends them to the [[#Delivery Ring|Delivery Ring]]. See [[ProtonBeamIntro]]. | |||
;{{Anchor|Redmine|redmine}} Redmine | ;{{Anchor|Redmine|redmine}} Redmine | ||
: An integrated code management system, used to manage and document many lab [https://cdcvs.fnal.gov/redmine/projects projects] | : An integrated code management system, used to manage and document many lab [https://cdcvs.fnal.gov/redmine/projects projects] (requires [[#SSO|SSO]]). The Mu2e [[#TDAQ|TDAQ]] team uses redmine but most other Mu2e software has been moved to the [https://github.com/Mu2e Mu2e GitHub organziation] and its documentation moved to the [[Computing]] section of this wiki. | ||
;{{Anchor|repo|repository}} repo, repository | ;{{Anchor|repo|repository}} repo, repository | ||
Line 478: | Line 585: | ||
;{{Anchor|ROOT}} ROOT | ;{{Anchor|ROOT}} ROOT | ||
: A [https://root.cern.ch software package for Scientific Data Analysis] developed at [[#CERN | CERN]]. It is also used as the underlying technology for [[#art | ''art'']] format [[#event-data| event-data files]]. As of 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]. | : A [https://root.cern.ch software package for Scientific Data Analysis] developed at [[#CERN | CERN]]. It is also used as the underlying technology for [[#art | ''art'']] format [[#event-data| event-data files]]. As of March 2022, Mu2e has two data analysis environments based on ROOT, [[#TrkAna|TrkAna]] and [[#Stntuple|Stntuple]]. See also: [https://root.cern/doc/master/classes.html the ROOT Class Index]. | ||
;{{Anchor|RPC}} RPC | ;{{Anchor|RPC}} RPC | ||
:Radiative Pion Capture. A [[BackgroundsPhysIntro|background process]] for Mu2e | :Radiative Pion Capture. A [[BackgroundsPhysIntro|background process]] for Mu2e | ||
;{{Anchor|RTPSD}} RTPSD | |||
: Real Time Processing Systems Division. Since October 2022 a division within the Fermilab [[#CSAI|CSAI]] that does R&D on and supports trigger and DAQ systems. | |||
==S== | ==S== | ||
Line 489: | Line 599: | ||
;{{Anchor|SCD}}SCD | ;{{Anchor|SCD}}SCD | ||
: Scientific Computing Division at Fermilab. | : Scientific Computing Division at Fermilab. Prior to October 2022, SCD was the organization within the Fermilab [[#Computing Sector|Computing Sector (CS)]] that managed grids, data handling, databases, infrastructure software, linux systems, and real time systems. Succeeded by the [[#CSAI|CSAI]]. | ||
;{{Anchor|Scons|scons}} Scons | ;{{Anchor|Scons|scons}} Scons | ||
: A freeware [[Scons|software package]] that drives a code [[#build|build]]. In Mu2e, it runs inside [[#Muse|Muse]] | : A freeware [[Scons|software package]] that drives a code [[#build|build]]. In Mu2e, it runs inside [[#Muse|Muse]] | ||
;{{Anchor|SCSSD}} SCSSD | |||
: Scientific Computing Systems and Services Division; since October 2022 a division within the Fermilab [[#CSAI|CSAI]] that manages grids, data handling, databases, infrastructure software, and linux systems. | |||
;{{Anchor|search path|Search path| search paths| Search paths}} Search path | ;{{Anchor|search path|Search path| search paths| Search paths}} Search path | ||
: Mu2e Offline uses several environment variables to find auxiliary input files, such as .fcl files and geometry files. These obey the same model as path environment variables such as PATH, LD_LIBRARY_PATH and the [[#UPS|UPS]] PRODUCTS variable. For details see [[SearchPaths]]. | : Mu2e Offline uses several environment variables to find auxiliary input files, such as .fcl files and geometry files. These obey the same model as path environment variables such as PATH, LD_LIBRARY_PATH and the [[#UPS|UPS]] PRODUCTS variable. For details see [[SearchPaths]]. | ||
;{{Anchor|Service|service}} Service (art software) | |||
: A concept within the [[#art|art]] framework. Services are most commonly used to make a resource available to many [[#modules|modules]]. Examples include serving geometry and conditions information. For more information see [[Services]]. | |||
;{{Anchor|Service Desk|Help Desk}} Service Desk | |||
: The way to request help and services from the Fermilab [[#CS|Computing Sector]]. For Mu2e specific questions you should consult [[ComputingHelp]]. For other questions use the [https://servicedesk.fnal.gov/ Service Desk website]; also email: [mailto:servicedesk@fnal.gov servicedesk@fnal.gov]; telephone: (630) 840-2345; in person between 8 AM and 5 PM Central Time Monday to Friday, on the ground floor of Wilson Hall on the north cross-over. | |||
;{{Anchor|Services password}} Services password | |||
: Your password for the [[#SSO|SSO]] system. It is distinct from your [[#Kerberos|Kerberos]] password. | |||
;{{Anchor|SEU}} SEU | ;{{Anchor|SEU}} SEU | ||
Line 501: | Line 623: | ||
;{{Anchor|SINDRUM|SINDRUM II|SINDRUM-II}} SINDRUM | ;{{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]]. | : 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|PSI]]. | ||
;{{Anchor|Singularity|singularity}}Singularity | ;{{Anchor|Singularity|singularity}}Singularity | ||
Line 511: | Line 633: | ||
;{{Anchor|SLAM}}SLAM | ;{{Anchor|SLAM}}SLAM | ||
: Scientific Linux Architecture Management. An organization within the Fermilab [[#SCD|SCD]]. Manages linux desktops and the Scientific Linux distribution. | : Scientific Linux Architecture Management. An organization within the Fermilab [[#SCD|SCD]]. Manages linux desktops and the Scientific Linux distribution. | ||
;{{Anchor|SlowControl}} Slow Control | |||
: A synonym for the Detector Control System; see [[#DCS|DCS]]. | |||
;{{Anchor|SMatrix|SMatrix|SMATRIX|smatrix}} SMatrix | ;{{Anchor|SMatrix|SMatrix|SMATRIX|smatrix}} SMatrix | ||
: SMatrix is a C++ package for high performance vector and matrix computations. It is distributed as part of [[#ROOT|ROOT]]. See [https://root.cern.ch/doc/v606/SMatrixPage.html]. SMatrix is used inside the [[#KinKal|KinKal]] tracking package and in Mu2e code that uses the output of KinKal. | : SMatrix is a C++ package for high performance vector and matrix computations. It is distributed as part of [[#ROOT|ROOT]]. See [https://root.cern.ch/doc/v606/SMatrixPage.html]. SMatrix is used inside the [[#KinKal|KinKal]] tracking package and in Mu2e code that uses the output of KinKal. | ||
;{{Anchor|SNOW}} SNOW | |||
: Service Now; the technology that underlies the Fermilab [[#Service Desk|Service Desk]]. Some people use it as a synonym for the Service Desk. | |||
;{{Anchor|spill}} spill | ;{{Anchor|spill}} spill | ||
: A | : A continuous sequence of [[#proton pulse|proton pulses]]. See [[TriggerDAQIntro|TDAQ intro]] and [[ProtonBeamIntro|proton beamline]]. | ||
;{{Anchor|SQL|sql}}SQL | ;{{Anchor|SQL|sql}}SQL | ||
Line 523: | Line 651: | ||
;{{Anchor|SSI}}SSI | ;{{Anchor|SSI}}SSI | ||
: Scientific Server Infrastructure. An organization within the Fermilab [[#SCD|SCD]]. Manages linux servers, such as mu2egpvm. | : Scientific Server Infrastructure. An organization within the Fermilab [[#SCD|SCD]]. Manages linux servers, such as mu2egpvm. | ||
;{{Anchor|SSO|Single Sign On}} SSO | |||
: Single Sign On. Commonly known as [[#Services password|your services password]]. This is a single sign on system used to access many resources at Fermilab including, the [https://mu2e-docdb.fnal.gov/cgi-bin/sso/DocumentDatabase/ Mu2e DocDb], write access to [[Main_Page | this wiki]], all access to the [https://mu2einternalwiki.fnal.gov/wiki/Main_Page Mu2e Internal Wiki], the [https://cdcvs.fnal.gov/redmine/projects/mu2e Mu2e redmine project], the [https://servicedesk.fnal.gov/ Service Desk] and many other lab resources. You use a different system, [[#Kerberos|Kerberos]], to log onto the Mu2e interactive machines. Your SSO username and your [[#Kerberos Principal| Kerberos Principal]] are identical but the lab asks that you use distinct passwords. | |||
;{{Anchor|STM}}STM | ;{{Anchor|STM}}STM | ||
Line 534: | Line 665: | ||
;{{Anchor|supercycle}} supercycle | ;{{Anchor|supercycle}} supercycle | ||
: The repeating cycle of the accelerator complex preparing and delivering fixed-target beam | : The repeating cycle of the accelerator complex preparing and delivering fixed-target beam. It consists of many [[#Main Injector Cycles|Main Injector Cycles]]. See [[TriggerDAQIntro|TDAQ intro]] and [[ProtonBeamIntro|proton beamline]]. | ||
==T== | ==T== | ||
;{{Anchor|TD}} TD | ;{{Anchor|TD}} TD | ||
: | : Technical Division. A division of Fermilab responsible for developing and building magnets and other beamline devices. | ||
;{{Anchor| | ;{{Anchor|TDAQ}} TDAQ | ||
: Trigger and Data AQuisition | : Trigger and Data AQuisition. See also [[#Trigger|Trigger]] and [[#DAQ|DAQ]]. The [https://www-ese.fnal.gov/mu2e/notebook/ Mu2e group responsible for these systems] (needs VPN). | ||
;{{Anchor|}} TDC | ;{{Anchor|TDC}} TDC | ||
: Time to Digital Converter. Used to measure the time a detector pulse waveform crosses a threshold. | : Time to Digital Converter. Used to measure the time a detector pulse waveform crosses a threshold. | ||
;{{Anchor|TDR|Technical Design Report}} TDR (document) | |||
: Technical Design Report. (The Mu2e TDR may be found at [https://mu2e-docdb.fnal.gov/cgi-bin/sso/ShowDocument?docid=4299 Mu2e-doc-4299] (full resolution version) or [https://arxiv.org/pdf/1501.05241.pdf arXiv:1501.05241] (compressed). | |||
;{{Anchor|TDR|time domain reflectometry}} TDR (measurement technique) | |||
: Time Domain Reflectometry: a measurement technique used to determine the properties of transmission lines by observing reflected signals | |||
;{{Anchor|time division}} time division | ;{{Anchor|time division}} time division | ||
Line 552: | Line 689: | ||
;{{Anchor|TOT}} TOT | ;{{Anchor|TOT}} TOT | ||
: Time Over Threshold. The time that a pulse waveform of over a threshold, an approximation of the pulse integral. | : Time Over Threshold. The time that a pulse waveform of over a threshold, an approximation of the pulse integral. | ||
;{{Anchor|TPC|Total Project Cost}} TPC | |||
: Total Project Cost. Total cost to get to [[#CD|CD]]-4, including all overheads and contingency. | |||
;{{Anchor|Tracker|tracker}} Tracker | |||
: A device, inside the [[#DS|DS]], for measuring the trajectories of charged particles that pass through it. Given the trajectory and the magnetic field strength one can compute the momentum of the charged particle. The main purpose of the device is to make a precision measurement of the momentum of [[#CE|conversion electron]] candidates. See [[TrackerIntro]]. | |||
;{{Anchor|Trigger|trigger}} Trigger | ;{{Anchor|Trigger|trigger}} Trigger | ||
: In Mu2e, set of [[#art|art]] modules that [[TriggerDAQIntro|run online]], in real-time, as the data is read out, and filters for the the most useful subset events, which are then recorded. | : In Mu2e, a set of [[#art|art]] modules that [[TriggerDAQIntro|run online]], in real-time, as the data is read out, and filters for the the most useful subset of events, which are then recorded. | ||
;{{Anchor|TPR|tpr|TrkPatRec}} TPR | ;{{Anchor|TPR|tpr|TrkPatRec}} TrkPatRec (TPR) | ||
: TrkPatRec is a pattern recognition algorithm, seeded only from the tracker hits, see also [[#CPR|CPR]] | : TrkPatRec is a pattern recognition algorithm, seeded only from the tracker hits, see also [[#CPR|CPR]] | ||
Line 565: | Line 708: | ||
: The Transport Solenoid. The [[TransportSolenoidIntro|S-shaped magnet]] channeling particles from the [[#PS|PS]] to the [[#DS|DS]] | : The Transport Solenoid. The [[TransportSolenoidIntro|S-shaped magnet]] channeling particles from the [[#PS|PS]] to the [[#DS|DS]] | ||
;{{Anchor| | ;{{Anchor|TSd}}TSd | ||
: The muon-downstream arc of the [[#TS|TS]]. | : The muon-downstream arc of the [[#TS|TS]]. | ||
;{{Anchor| | ;{{Anchor|TSu}}TSu | ||
: The muon-upstream arc of the [[#TS|TS]]. | : The muon-upstream arc of the [[#TS|TS]]. | ||
==U== | ==U== | ||
;{{Anchor|Upstream|upstream|up-stream}} Upstream | ;{{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. | : 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. | ||
;{{Anchor|UPS Product|UPS product}} UPS Product | ;{{Anchor|UPS Product|UPS product}} UPS Product | ||
: A software package distributed using the [[UPS]] system; examples include the C++ compiler, [[#art|''art'']], [[#ROOT|ROOT]], and [[#GEANT4|GEANT4]]. | : A software package distributed using the [[UPS]] system; examples include the C++ compiler, [[#art|''art'']], [[#ROOT|ROOT]], and [[#GEANT4|GEANT4]]. | ||
Line 580: | Line 724: | ||
;{{Anchor|valgrind}}valgrind | ;{{Anchor|valgrind}}valgrind | ||
: A freeware [[CodeDebugging#valgrind|software package]] that can check running code for memory errors, such as overwrites or uninitialized variables. | : A freeware [[CodeDebugging#valgrind|software package]] that can check running code for memory errors, such as overwrites or uninitialized variables. | ||
;{{Anchor|VOMS}}VOMS | |||
: The acronym for the Virtual Organization Membership Serviicem https://italiangrid.github.io/voms/, which is a facility for controlling access to grid based computing resources originally developed for the LHC based experiments and later adopted more widely in HEP and elsewhere. | |||
;{{Anchor|VST}} VST | ;{{Anchor|VST}} VST | ||
Line 622: | Line 769: | ||
# Maybe the right answer is to extend an existing definition or to provide an additional anchor for an existing definition? | # Maybe the right answer is to extend an existing definition or to provide an additional anchor for an existing definition? | ||
# Inspect the page source to understand how to use the Anchor and Fixme macros; follow that model. The Anchor macro permits at most 10 variants of the spelling and capitalization. | # Inspect the page source to understand how to use the Anchor and Fixme macros; follow that model. The Anchor macro permits at most 10 variants of the spelling and capitalization. | ||
# Think of synonyms for your definition; either include the synonym among the anchor variants or add a definition for the synonym and link it to your new entry. | |||
# Leave one blank line between definitions. | # Leave one blank line between definitions. | ||
# We do not have a tool to force correct alphabetization; please put your definition in the correct spot. | # We do not have a tool to force correct alphabetization; please put your definition in the correct spot. |
Latest revision as of 22:54, 26 February 2024
A glossary of terms and acronyms that one will encounter when working on Mu2e. There are other glossaries in which you may find terms not covered here:
- Acronyms specific to the Fermilab accelerator complex and the Mu2e Construction Project: MAD: The Mu2e Acronym Dictionary .
- Fermilab Computing Sector acronyms page: Computing Acronyms
- TDAQ engineers acronyms (must be on-site or using VPN).
To contribute to this glossary, please see the section: How to contribute.
0–9
- 413.3B
- DOE Order 413.3B specifies a series of staged approvals for major construction projects. The Mu2e construction project follows this order. See also [1] and links from the lower left of the Mu2e internal home page, [2]. For more DOE acronyms see the Mu2e Acronym Dictionary (MAD).
A
- AD
- Accelerator Division. A division of Fermilab responsible for assembling, maintaining and running beamlines.
- ADC
- Analog to Digital Converter. Used in detectors to measure a pulse waveform and produce a time series of values.
- AI
- Artificial Intelligence
- ALCF
- Argonne Leadership Computing Facility, a supercomputer center managed by the DOE
- ANN
- Artificial Neural Network. A Machine Learning technique.
- art (software)
- art is the name of an event processing framework used by Mu2e and many other particle physics experiments associated with Fermiab; the Mu2e Offline code runs within art. The home page for the art proejct is [3]. FIXME: write an art section in the wiki and link to it from here.
- artdaq, artdaq_core, mu2e_artdaq, mu2e_artdaq_core
- Artdaq is a DAQ package written by SCD, the "mu2e" parts are customizations for Mu2e, the "core" parts are just the definition of the data format.
B
- Badge
- The plastic card issued by Fermilab with your picture and Fermilab ID number on it. Contrast with Fermilab ID.
- BDT
- Boosted Decision Tree, a machine learning algorithm
- Beaglebone
- A minimal commercial computer on a small board, typically used to run a dedicated program.
- boost
- Freeware c++ supplemental libraries for common algorithms.
- Booster (BO)
- An element of the Fermilab accelerator complex that is used to deliver proton beam to Mu2e. It receives beam from the LINAC and sends it to the Main Injector. See Booster Cycle and ProtonBeamIntro.
- Booster Batch
- The unit of beam that is accelerated in the Booster and transferred out of the Booster. In normal Mu2e operations it will consist of 80 bunches. See Booster Cycle and ProtonBeamIntro.
- Booster Cycle
- The repeating cycle of the Fermilab Booster; within one cycle it receives beam from the LINAC, accelerates it to 8 GeV kinetic energy and sends it to one of the Recycler, the Main Injector or to the booster neutrino beam target. Beam destined for Mu2e goes to the Recycler. One booster cycle has a duration of 1/15 seconds. See ProtonBeamIntro.
- BTrk
- BTrk is a helix track pattern recognition and fitting package, ported to Mu2e from BaBar.
- build
- The process of compiling and linking code with a specific configuration, or the output of that process.
C
- 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.
- Caphri
- A proposed system for potentially measuring total stopped muons using four LYSO crystals on the outside of the calorimeter. See 33857.
- CCD
- Core Computing Division at Fermilab. Prior to October 2022, CCD was an organization within the Fermilab Computing Sector (CS). It managed Windows, business systems, printers, networking, security. Succeeded by the ITD.
- CD, CD-0, CD-1, CD-2, CD-3, CD-4
- Critical Decision. Major approval points in the progress of a DOE project
- CDR
- Conceptual Design Report. A fairly advanced conceptual desicription of the experiment, which has been superseded by the Technical Design Report (TDR)
- CE
- Conversion Electron. The result of a muon which has converted to an electron through CLFV, the primary signature of the Mu2e search.
- CERN
- A High Energy Physics lab in Geneva, Switzerland. See the CERN home page.
- Certificate
- A method of user authentication that is needed to access some computing resources. For example certificates are used to submit grid jobs and to write information to SAM. For additional information see [4].
- CFO
- Command Fan Out. Hardware component of the online DAQ (TDAQ) that provides the interface between the command host and the DTCs. The CFO drives run plan, synchronization, and timing for the online DAQ. (For additional information, see [5].)
- CLFV
- Charged Lepton Flavor Violation. A rare process where, for example, a muon can spontaneously convert to an electron. The primary process of the Mu2e new physics search.
- 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 SMatrix package.
- CMM
- Coordinate Measuring Machine
- CNN
- Convolutional Neural Network. A Machine Learning technique.
- COMET
- A competitor experiment, also building an experiment to look for Muon to Electron Conversion. Located at J-PARC. See also the COMET Home Page.
- CORSICA
- A software package for generating cosmic ray air showers for simulation.
- CPR, CalPatRec
- CalPatRec is a tracker helix pattern recogniton algorithm, where the hit search is seeded by a calorimeter cluster. See also TPR
- CRR
- Construction Readiness Review. A review of a project component, such as an electronics board, to make sure the design is complete and tested, before the component construction begins.
- CRS
- Cosmic Ray Shield, and obsolete name for the CRV
- 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. During data analysis Mu2e will exclude exclude tagged events.
- CRY
- A software package for generating cosmic rays for simulation.
- CS
- The Fermilab Computing Sector. Prior to October 2022, the organization within Fermilab that supported our scientific computing needs. The successor organization is CSAI. It had two divisions, CCD and SCD. See https://computing.fnal.gov
- CSAID
- Computational Science and AI Directorate; since Octobber 2022, the organization within Fermilab that supports our scientific computing needs. This organization succeeds CS. The divisions within CSAI are: SCSSD, DSSLD and RTPSD.
- CsI
- Cesium Iodide. The material used for the calorimeter crystals
- CVMFS
- CERN Virtual Machine File System, a virtual, distributed disk system used to provide software to the central servers, the grid, and institutions.
D
- Data Product
- The unit of data that can be written to or read from an art format event-data file.
- DAQ
- Data AQuisition, the process of reading out the low-level detector data and building it into an event on disk. In Mu2e, the DAQ system is built around the artdaq and OTSDAQ packages.
- DB
- Database
- dCache
- A very large virtual disk array for experiment data managed by the Fermilab SCD.
- DCS
- Detector Control System. A set of online software systems and procedures used to control and monitor the detector and DAQ components. The underlying technology is EPICS and the DCS system is sometimes called the "EPICS System". It is also called the Slow Control system.
- degrader
- A foil near the entrance of the DS that can be moved into the beam, to reduce the beam intensity for use in calibrations or to reduce the momentum of beam particles for use in calibrations.
- DeM
- Acronym referring to the track fit hypothesis of a downstream going negative electron.
- DES
- Downstream External Shielding: The muon beamline shielding external to the Downstream Transport Solenoid (TSd) and the Detector Solenoid (DS).
- Delivery Ring
- A component of the Fermilab accelerator complex that delivers proton pulses to the Mu2e production target. The Delivery Ring is a synchrotron and its period sets the time between pulses arriving at the Mu2e production target. For additional information see ProtonBeamIntro.
- 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 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.
- DIO
- Decay In Orbit. When a muon undergoes a Standard Model decay while in orbit around a nucleus. A background process for Mu2e.
- DIRAC
- The calorimeter board containing ADC's and the ROC function.
- Docker
- A freeware "software container platform", providing a way to bundle software and its linux environment, including system libraries (but not the kernel, like a virtual machine would). The container is then very portable.
- DOE
- The United States Department of Energy, which funds Fermilab. See [6].
- Downstream
- An ambiguous term meaning the opposite of another ambiguous term. See the definition of upstream.
- DPA
- Displacements Per Atom. A measure of radiation exposure.
- DQM
- Data Quality Monitor. A process, online and ofline, to histogram data content to record data status and monitor for quality.
- DS
- Detector Solenoid. The magnet surrounding the tracker and calorimeter.
- DSSLD
- Data Science, Simulation and Learning Division. Since October 2022, a division within the Fermilab CSAI. This organization supports art, Geant4 and the distribution of UPS products by the Scisoft team. It is the home organization to many of the scientistic staff within CSAI.
- DTC
- Data Transfer Controller. A set of PCIe card's in the TDAQ servers which communicate with the ROC's
- DT generator
- Deuterium-Tritium generator. A source of neutrons, used for calorimeter calibration
E
- EMC
- ElectroMagnetic Calorimeter. Another name for the Mu2e calorimeter
- EMMA
- Extensible Magnetic Measurement Application. A framework developed by the Software Systems Group of Fermilab’s Technical Division to build magnetic measurement applications.
- ENE
- Engaging Non-Experts. A thread within Mu2e, to produce documentation and tutorials to help onboard new collaborators.
- Enstore
- The system of data tapes managed by the Fermilab SCD.
- EPICS
- A freeware real-time monitoring system. In Mu2e, it is used for online detector monitoring and control. See DCS and Slow Control.
- ESS
- Electrostatic Septum, part of the Resonent Extraction System. (An overview may be found in the TDR section 4.6.)
- Event (accelerator)
- In the Fermilab accelerator complex, some of the timing and control signals are referred to as "events".
- Event (DAQ)
- All of the data associated with some time interval; it includes 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. In casual use, the word event may refer either to the time period or to the data associated with that time period. In the DAQ community the time period is called an Event Window and the data is called an event. When Mu2e is taking on-spill data, an event is all of the data associated with one proton pulse. When Mu2e is taking off-spill data, an event is all of the data associated with a time period that's chosen considering several trade-offs; as of March 2022, the duration of the time period is defined to be 100 micro-seconds.
- Event-data
- A collective noun referring to both data and simulated events. Here "data" refers exclusively to information that comes from measurements made by experiments, test beams or test stands. Simulated information should not be named "data". The use of the terms "real data" and "simulated data", as synonyms for data and simulated events, is discouraged but is in wide use.
- Event Window
- A time interval inside the DAQ system. All data measured during this time interval will be organized into one event.
- Event Window Marker (EWM)
- A timing signal distributed throughout the DAQ system that signals when a new Event Window begins.
- Event Window Tag (EWT)
- A 48-bit integer that uniquely identifies each Event Window over the lifetime of Mu2e.
- Extinction
- The ratio of the number of out-of-time protons to the number of in-time protons is called the extinction. Here, in-time refers to protons that arrive at the production target within a proton pulse from the Delivery Ring and out-of-time refers to protons that arrive between two pulses. Out-of-time protons can produce false signals, principally via the mechanism of RPC. Mu2e must achieve an extinction of [math]\displaystyle{ 10^{-10} }[/math] in order to reduce these backgrounds to an acceptable level.
- EXTMON
- Extinction Monitor. A device to monitor the level of extinction in the proton beam. See ExtinctionMonitorIntro.
F
- FCC
- Fermi Computing Center. The round building, just north of Wilson hall, which houses computing sector personnel and hardware.
- FEA, FEM
- Finite Element Analysis (or Method). An engineering method for analyzing material stress or temperature patterns.
- FEE
- Front End Electronics, a generic term for electronics close to a detector, typically ADC's and TDC's.
- Fermigrid
- A system of approximately 20,000 grid computing nodes managed by the Fermilab SCD.
- 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.
- FIFE
- Fabric for Frontier Experiments. An umbrella term for projects within the SCD supporting Intensity Frontier experiments.
- Fluka
- A software package to simulate interactions of particles and matter, often used to check geant
- FMS
- Field Mapping System. A device that can be run through the DS magnet (before the detector is inserted) to measure the magnetic field precisely.
- FNAL
- Fermi National Accelerator Lab; the full name of Fermilab. The lab has a public home page and a separate home page for employees, Users and Affliates.
- FPGA
- Field Programmable Gate Array. A chip which can be programmed to perfom arbitrary digital logic.
- FTS
- File Transfer Service. A service to upload files to tape and record their metadata, managed by SCD
G
- gallery
- A software package that allows an art event-data file to be read like an ntuple. Managed by SCD.
- GCC
- Grid Computing Center. A lab building, near the end of the fixed-target beamlines, which houses computing sector hardware.
- G4beamline
- A system of simplified geometry for running geant simulations, originally intended for quickly prototyping beamline alternatives.
- gcc, g++
- The freeware c and c++ compiler from Gnu, used by Mu2e.
- geant, g4, geant4
- Software for tracing particles and interacting them with material. This is the core of most HEP simulations, including Mu2e. See [7].
- git
- A freeware software versioning tool. Each large conceptual code package is kept in its own repository (repo).
- GNN
- Graph Neural Network. A Machine Learning technique.
- Grafana
- a software graphics package used by SCD in monitoring dashboard applications
H
- Hit
- A software object that represents the calibrated form of a 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.
- HPC
- High Performance Computing, a generic term for large, uniform computing centers (supercomputers), such as systems at NERSC and ALCF
- HRS
- Heat and Radiation Shield. The shield that surrounds the production target to protect the superconducting Production Solenoid (PS)
I
- IFB
- Instrumentation Feedthrough Bulkhead. A plate at the end of the DS, maintaining the DS vacuum and providing a path for the services and signals between vacuum and hall air.
- ifdh
- Intensity Frontier Data Handling. A set of scripts in a UPS product to ensure reliable and efficient transfer of data files between grids and dCache, and other places. Used by Mu2e.
- INFN
- Istituto Nazionale Fisica Nucleare. The governmental body overseeing HEP in Italy.
- Intensity
- This term has several different meanings. In the future we will define and adopt more precise language to distinguish these meanings. For now you need to interpret the meaning from the context. In the analysis community, intensity usually refers to the number of muons that stop in the stopping target, or a measurement that stands as a proxy for that number; it may refer to the pulse by pulse value or it may refer to the sum over a longer period of time. See also STM and CAPHRI. Alternatively, intensity may refer to the number of protons in a single proton pulse; the related term POT is used as the sum over a longer period of time. See also PBI.
- IPR
- Independent Project Review. Part of the process by which the DOE monitors the Mu2e construction project.
- IPA
- Inner Proton Absorber. A plastic absorber inside the DS, downstream of the stopping target and upstream of the tracker; intended to prevent protons emitted from the target from aging the tracker.
- ITD
- The Fermilab Information Technology Division. Since October 2022, the successor organization to the CCD. It manages the hardware for scientific computing, Windows, business systems, printers, networking, security.
J
- Jenkins
- Jenkins is infrastructure to run software builds on multiple platforms in parallel. It is managed by SCD and used my Mu2e and other experiements.
- J-PARC
- Japan Proton Accelerator Research Complex. An HEP lab in Japan that hosts many HEP experiments, including COMET, a competitor to Mu2e. For more information see their home page.
K
- 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.
- Kerberos Principal
- Your username within the Kerberos system. You use it to log into the Mu2e interactive computers.
L
- L2, L3
- Level-2 Manager. A DOE project will have level-2 managers for major project components, who in turn may appoint level-3 managers for smaller components. The Mu2e web site documents the Level-2 sub-projects within the Mu2e Construction Project.
- LINAC
- Linear Accelerator. An element of the Fermilab accelerator complex that is used to deliver proton beam to Mu2e.
- LRU
- Light Response Uniformity. A measure of consistentcy along the length of a calorimeter crystal.
- Luminosity
- In the past some people on Mu2e used this term 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 but some older documents use luminosity and it is still in common use. The reason for the change is that the word luminosity has a well defined meaning in the collider community that is quite different than the meaning in Mu2e.
- LY
- Light Yield
- LYSO
- Lutetium–yttrium oxyorthosilicate, a scintillating crystal material
M
- MARS
- A software package for simulating the interaction of particles and matter. Its detailed nulcear model is often used to predict radiation levels.
- MB
- MotherBoard for electronics.
- MBS
- Muon Beam Stop. This device absorbs most of the beam particles after they have passed through the detector region.
- MC (Monte Carlo)
- The computer codes used to simulate the response of Mu2e detector to the many physics processes of interest use Monte Carlo methods, a class of computing techniques that uses random sampling to produce numerical results.
- MI (Main Injector)
- An element of the Fermilab accelerator complex. It is not used to delivery proton beam Mu2e but the delivery of beam to Mu2e follows a repeating pattern called an MI Cycle.
- MI Cycle
- A repeating series of operations that involves the Main Injector (MI) and related elements of the accelerator complex. Mu2e will share beam with NOvA, and later with DUNE; during normal operations an MI cycle will consist of 21 or 22 Booster Cycles, during which both Mu2e and NOvA get beam. See ProtonBeamIntro.
- Micro bunch
- This term is now obsolete and has been replaced by proton pulse. Some older documents use the obsolete name.
- millepede
- A software package for fitting alignment parameters
- ML
- Machine Learning. A data analysis technique where an algorithm with a goal (physics analysis) is trained on data sets.
- Module (software)
- A module is the unit of processing that can be executed by the art framework. See also Modules. This use of the word module is unrelated to concepts with the same name in programming languages such as Perl, Python, Pascal or the upcoming C++20 standard.
- MSTM
- Muon Stopping Target Monitor, another name for the STM
- MTBF
- Mean Time Between Failures. A measure of reliability.
- Mu2eII, Mu2e-II
- A proposed successor to the Mu2e experiment
- Mu2e Offline Software
- A collective noun for all of the Mu2e software that is normally run offline. Most of this software is kept in git repositories at the Mu2e GitHub organization.
- muon-upstream
- In the direction of the muon beam. Most of the time this means the +z direction, which is the direction of the muon beam when it is in the PS and the DS. Contrast with proton-upstream. FIXME: Link to coordinate system..
- Muse
- MU2e Software Environment, a set of scripts maintained by Mu2e, used to coordinate the building of multiple code repos.
- MVA
- Multi-Variant Analysis. A Machine Learning umbrella term - typically separating classes of events in many-dimensional parameter space.
N
- NERSC
- National Energy Research Scientific Computing Center, a supercomputer center managed by the DOE
O
- Offline
- This term has two meanings. Generically it refers to all Mu2e software and workflows that usually are run in computer centers, university computing resources, laptops and other resources outside of the Mu2e building. Specifically it refers to a software repository, named Offline, located in the Mu2e GitHub organization; it contains the main trigger, calibration, reconstruction and simulation codes for Mu2e. Contrast with online. See also Mu2e Offline Software.
- offspill
- A time period in which Mu2e is taking data but no beam is present. During offspill periods, Mu2e will collect cosmic ray data and calibration data. Contrast with onspill. Offspill refers both to the offspill period within an MI cycle and to extended offspill periods when the accelerator off. See TDAQ intro and proton beamline.
- Online
- Software and workflows that are run on the TDAQ resources in the Mu2e building. This includes OTS, artdaq, DCS, the online component of DQM. It excludes RDM, which is developed and operated by the Offline group. Contrast with offline.
- onspill
- The data-taking time period related to a continuous sequence of proton pulses; or the data taken during this time; or other activities related to this time. Contrast with offspill. See TDAQ intro and proton beamline.
- OOT
- Out of Time; not within a specified time window.
- OOT
- Out of Target. Usually referring to a muon which has stopped outside of the stopping target
- OPA
- Outer Proton Absorber. Plastic around the stopping target, intended to prevent protons emitted from the target from aging the tracker.
- ORC
- Operational Readiness Clearance. Permission to operate a potentially hazardous system.
- ORR
- Operational Readiness Review. A formal or informal review of a system as small as a test stand to as large a whole experiment, to make sure it is safe and will perform as needed.
- OSG
- Open Science Grid. An organization within High Energy Physics to provide standards and distribute opportunistic grid computing cycles.
- OTS, OTSDAQ
- Off-The-Shelf DAQ, a software package, managed by SCD which provides a human-friendly GUI for configuration and control of the artdaq DAQ process.
P
- PBI
- Proton Bunch Intensity. The number of protons in a single proton pulse. It should have been called Proton Pulse Intensity but the acronym was defined long ago and has stuck. There is a large variation in PBI over the course of a spill.
- PCB
- Printed Circuit Board
- Plotly
- a python graphics package for displaying interactive plots
- POMS
- Production Operations Management Service, an SCD tool that helps users to run large and complex grid computing campaigns.
- postgres
- A freeware relational database. In Mu2e, conditions data, online run records, and EPICS data are stored in postgres databases managed by SCD.
- POT
- Protons On Target: the number of protons delivered by the Fermilab accelerator complex to the Mu2e Production Target. Usually expressed as the sum over some period of time, typically weeks or years. Contrast with proton pulse.
- PPD
- Particle Physics Division, a division of Fermilab, the home of Mu2e.
- Product
- Either a UPS Product or a Data Product; hopefully the meaning will be clear from the context.
- Production Target
- The target inside the Mu2e PS; protons from the accelerator complex hit this target to produce pions that decay to muons. This is the source of the Mu2e muon beam. See also ProductionTargetIntro.
- PTSM
- Production Target Scanning Monitor. A proposed Mu2e subsystem. If installed, it will be located downstream of the PS and will be used during beam commissioning to ensure that the proton beam is properly aligned with the production target.
- Proton Pulse
- The protons extracted during one turn of the Delivery Ring and delivered 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; the term proton pulse is preferred.
- 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. FIXME: Link to coordinate system..
- PS
- Production Solenoid. The magnet surrounding the production target, the first step in steering muons into the beamline.
- PSI
- The Paul Sherrer Institut. A research facility in Switzerland that is the home of the SINDRUM-II experiment.
- PV
- Process Variable. A Variable monitored in EPICS such as temperature or voltage.
- Pulse
- Usually refers to a proton pulse but may also refer to the muon pulse that follows each proton pulse.
Q
- QC
- Quality Control
- QPM
- Quench Protection and Monitoring system. (fermilab-pub-21-637)
R
- Raw data
- The low level data collected from the experiment by the DAQ system. The data is in a highly compressed format that can be unpacked into collections of digis. For packet definitions see Mu2e-doc-4914.
- Raw data file
- A file written by the TDAQ system. It contains raw data plus additional data products that describe why the trigger system accepted the event.
- RDM
- Raw Data Mover. The working name for the system of scripts which copies raw data from the DAQ disks to the offline dCache disks and tape, and declares the file metadata.
- Recycler (RR)
- An element of the Fermilab accelerator complex that is used to deliver beam to Mu2e. It receives protons from the Booster, rebunches them and sends them to the Delivery Ring. See ProtonBeamIntro.
- Redmine
- An integrated code management system, used to manage and document many lab projects (requires SSO). The Mu2e TDAQ team uses redmine but most other Mu2e software has been moved to the Mu2e GitHub organziation and its documentation moved to the Computing section of this wiki.
- repo, repository
- A logically-related set of source code, stored and manged as a unit, by git. The Mu2e repos are here.
- RMC
- Radiative Muon Capture. A background process for Mu2e
- ROC
- ReadOut Controller. A electronics system that is the first part of the digital DAQ readout chain.
- ROOT
- A software package for Scientific Data Analysis developed at CERN. It is also used as the underlying technology for art format event-data files. As of March 2022, Mu2e has two data analysis environments based on ROOT, TrkAna and Stntuple. See also: the ROOT Class Index.
- RPC
- Radiative Pion Capture. A background process for Mu2e
- RTPSD
- Real Time Processing Systems Division. Since October 2022 a division within the Fermilab CSAI that does R&D on and supports trigger and DAQ systems.
S
- SAM
- Serial Access to Metadata, a metadata database for data files, used by Mu2e, managed by the SCD.
- SCD
- Scientific Computing Division at Fermilab. Prior to October 2022, SCD was the organization within the Fermilab Computing Sector (CS) that managed grids, data handling, databases, infrastructure software, linux systems, and real time systems. Succeeded by the CSAI.
- Scons
- A freeware software package that drives a code build. In Mu2e, it runs inside Muse
- SCSSD
- Scientific Computing Systems and Services Division; since October 2022 a division within the Fermilab CSAI that manages grids, data handling, databases, infrastructure software, and linux systems.
- Search path
- Mu2e Offline uses several environment variables to find auxiliary input files, such as .fcl files and geometry files. These obey the same model as path environment variables such as PATH, LD_LIBRARY_PATH and the UPS PRODUCTS variable. For details see SearchPaths.
- Service (art software)
- A concept within the art framework. Services are most commonly used to make a resource available to many modules. Examples include serving geometry and conditions information. For more information see Services.
- Service Desk
- The way to request help and services from the Fermilab Computing Sector. For Mu2e specific questions you should consult ComputingHelp. For other questions use the Service Desk website; also email: servicedesk@fnal.gov; telephone: (630) 840-2345; in person between 8 AM and 5 PM Central Time Monday to Friday, on the ground floor of Wilson Hall on the north cross-over.
- SEU
- Single Event Upset. A form of electronics glitch.
- SINDRUM
- The previous best limit on muon to electron conversion was obtained by the SINDRUM II experiment, an experiment at PSI.
- Singularity
- A freeware "software container platform", providing a way to bundle software and its linux environment, including system libraries (but not the kernel, like a virtual machine would). The container is then very portable. Often used to run experiment software on grid nodes.
- SiPM
- Silicon PhotoMultiplier. A solid-state photon detector, used in the CRV and the Calorimeter.
- SLAM
- Scientific Linux Architecture Management. An organization within the Fermilab SCD. Manages linux desktops and the Scientific Linux distribution.
- Slow Control
- A synonym for the Detector Control System; see DCS.
- SMatrix
- SMatrix is a C++ package for high performance vector and matrix computations. It is distributed as part of ROOT. See [8]. SMatrix is used inside the KinKal tracking package and in Mu2e code that uses the output of KinKal.
- SNOW
- Service Now; the technology that underlies the Fermilab Service Desk. Some people use it as a synonym for the Service Desk.
- spill
- A continuous sequence of proton pulses. See TDAQ intro and proton beamline.
- SSI
- Scientific Server Infrastructure. An organization within the Fermilab SCD. Manages linux servers, such as mu2egpvm.
- SSO
- Single Sign On. Commonly known as your services password. This is a single sign on system used to access many resources at Fermilab including, the Mu2e DocDb, write access to this wiki, all access to the Mu2e Internal Wiki, the Mu2e redmine project, the Service Desk and many other lab resources. You use a different system, Kerberos, to log onto the Mu2e interactive machines. Your SSO username and your Kerberos Principal are identical but the lab asks that you use distinct passwords.
- STM
- Stopping Target Monitor, a set of photon detectors which observe the muon stopping target, and measure the number of stopped muons.
- Stntuple
- A Mu2e ntuple package, with a custom data format and event-reading framework.
- Stopping Target
- Aluminum foils at the entrance of the DS where most muons lose energy and stop, then fall into orbit around a nucleus.
- supercycle
- The repeating cycle of the accelerator complex preparing and delivering fixed-target beam. It consists of many Main Injector Cycles. See TDAQ intro and proton beamline.
T
- TD
- Technical Division. A division of Fermilab responsible for developing and building magnets and other beamline devices.
- TDAQ
- Trigger and Data AQuisition. See also Trigger and DAQ. The Mu2e group responsible for these systems (needs VPN).
- TDC
- Time to Digital Converter. Used to measure the time a detector pulse waveform crosses a threshold.
- TDR (document)
- Technical Design Report. (The Mu2e TDR may be found at Mu2e-doc-4299 (full resolution version) or arXiv:1501.05241 (compressed).
- TDR (measurement technique)
- Time Domain Reflectometry: a measurement technique used to determine the properties of transmission lines by observing reflected signals
- time division
- locating a hit along the length of a straw by comparing pulse arrival times at the two ends.
- TOT
- Time Over Threshold. The time that a pulse waveform of over a threshold, an approximation of the pulse integral.
- TPC
- Total Project Cost. Total cost to get to CD-4, including all overheads and contingency.
- Tracker
- A device, inside the DS, for measuring the trajectories of charged particles that pass through it. Given the trajectory and the magnetic field strength one can compute the momentum of the charged particle. The main purpose of the device is to make a precision measurement of the momentum of conversion electron candidates. See TrackerIntro.
- Trigger
- In Mu2e, a set of art modules that run online, in real-time, as the data is read out, and filters for the the most useful subset of events, which are then recorded.
- TrkPatRec (TPR)
- TrkPatRec is a pattern recognition algorithm, seeded only from the tracker hits, see also CPR
- TrkAna
- an ntuple format for track-based analyses. See TrkAna for details
- TS
- The Transport Solenoid. The S-shaped magnet channeling particles from the PS to the DS
- TSd
- The muon-downstream arc of the TS.
- TSu
- The muon-upstream arc of the TS.
U
- Upstream
- An ambiguous term meaning either proton-upstream or muon-upstream; hopefully it will usually be clear from the context which is intended.
- UPS Product
- A software package distributed using the UPS system; examples include the C++ compiler, art, ROOT, and GEANT4.
V
- valgrind
- A freeware software package that can check running code for memory errors, such as overwrites or uninitialized variables.
- VOMS
- The acronym for the Virtual Organization Membership Serviicem https://italiangrid.github.io/voms/, which is a facility for controlling access to grid based computing resources originally developed for the LHC based experiments and later adopted more widely in HEP and elsewhere.
- VST
- Vertical Slice Test. A test of detector readout, using the full chain of prototype electronics, but only for a few channels.
W
X
- xrootd
- Part of the root software, xrootd can provide root file access across a network.
Y
Z
How to Contribute
- To request a new definition or suggest an edit, please send email to mu2e-glossary@fnal.gov.
- Edit this page yourself.
- View the contribution guidelines, below.
- Edit the page, following those guidelines.
- Within a few days your contribution will be reviewed by a moderator, who may contact you to discuss it.
Contribution Guidelines
- If you have questions, send email to mu2e-glossary@fnal.gov.
- Check if the definition you propose already exists.
- Maybe the right answer is to extend an existing definition or to provide an additional anchor for an existing definition?
- Inspect the page source to understand how to use the Anchor and Fixme macros; follow that model. The Anchor macro permits at most 10 variants of the spelling and capitalization.
- Think of synonyms for your definition; either include the synonym among the anchor variants or add a definition for the synonym and link it to your new entry.
- Leave one blank line between definitions.
- We do not have a tool to force correct alphabetization; please put your definition in the correct spot.
- Limit your definition to at most few sentences and link to additional material. Use the Fixme macro if the content you need to link to does not yet exist.
- If you use terms also defined on this page, link to them.
- For links within this page, use the syntax [[#anchor | text]] even if the text is the same as the anchor. We don't like the look of the extra # produced by the alternative syntax, [[#anchor]].
- If the definition is closely related to other definitions on this page, make links in both directions.
- Don't leave broken links; instead use the Fixme macro to indicate that more work is needed.
- When you are finished, use the "Preview" button to verify that your contribution renders correctly. Also use the "Show Changes" button to check that you have not inadvertently modified other content.
- Remember to click on "Save Changes".