Difference between revisions of "Software"
From GlueXWiki
| Line 6: | Line 6: | ||
* <span style="color:orange; font-size:2em">●</span> Raw data is saved by the [https://coda.jlab.org/drupal/ '''''DAQ system'''''] in the [https://www.jlab.org/evio '''''EVIO'''''] file format and processed using programs in [https://github.com/JeffersonLab/halld_recon/wiki '''''halld_recon''''']. More details about the '''''EVIO''''' file format can be found [https://coda.jlab.org/drupal/content/event-io-evio '''''here'''''] (Mark) | * <span style="color:orange; font-size:2em">●</span> Raw data is saved by the [https://coda.jlab.org/drupal/ '''''DAQ system'''''] in the [https://www.jlab.org/evio '''''EVIO'''''] file format and processed using programs in [https://github.com/JeffersonLab/halld_recon/wiki '''''halld_recon''''']. More details about the '''''EVIO''''' file format can be found [https://coda.jlab.org/drupal/content/event-io-evio '''''here'''''] (Mark) | ||
* There are three main databases: | * There are three main databases: | ||
| − | ** <span style="color:green; font-size:2em">●</span> Run conditions (e.g. beam current, radiator) are stored in [https://github.com/JeffersonLab/rcdb/wiki RCDB] ([https://halldweb.jlab.org/rcdb/runs/ web interface]) (Naomi) | + | ** <span style="color:green; font-size:2em">●</span> Run conditions (e.g. beam current, radiator) are stored in [https://github.com/JeffersonLab/rcdb/wiki '''''RCDB'''''] ([https://halldweb.jlab.org/rcdb/runs/ '''''web interface''''']) (Naomi) |
| − | ** <span style="color:orange; font-size:2em">●</span> Calibrations and other parameters used in reconstruction/analysis are stored in [https://github.com/JeffersonLab/ccdb/wiki/ CCDB] ([https://halldweb.jlab.org/cgi-bin/ccdb/objects web interface]). (Naomi & Sean) | + | ** <span style="color:orange; font-size:2em">●</span> Calibrations and other parameters used in reconstruction/analysis are stored in [https://github.com/JeffersonLab/ccdb/wiki/ '''''CCDB'''''] ([https://halldweb.jlab.org/cgi-bin/ccdb/objects '''''web interface''''']). (Naomi & Sean) |
| − | ** <span style="color:green; font-size:2em">●</span> Hall-D Online Skim System records data for individual raw data files [https://halldweb.jlab.org/hoss HOSS] (e.g. number of events per file, number of each trigger type, ... ''n.b. only for 2020 and later Run Periods'') (David) | + | ** <span style="color:green; font-size:2em">●</span> Hall-D Online Skim System records data for individual raw data files [https://halldweb.jlab.org/hoss '''''HOSS'''''] (e.g. number of events per file, number of each trigger type, ... ''n.b. only for 2020 and later Run Periods'') (David) |
| − | * <span style="color:orange; font-size:2em">●</span> hd_root is used to analyse EVIO and REST data with plugins for monitoring, [[Calibrations]], and event reconstruction (Sean [calibrations] - & Mark) | + | * <span style="color:orange; font-size:2em">●</span> hd_root is used to analyse EVIO and REST data with plugins for monitoring, [[Calibrations|'''''Calibrations''''']], and event reconstruction (Sean [calibrations] - & Mark) |
* <span style="color:red; font-size:2em">●</span> REST files are an HDDM format which stores reconstructed physics objects (no detector hit information) (Richard) | * <span style="color:red; font-size:2em">●</span> REST files are an HDDM format which stores reconstructed physics objects (no detector hit information) (Richard) | ||
'''Simulated data - halld_sim''' | '''Simulated data - halld_sim''' | ||
| − | * <span style="color:orange; font-size:2em">●</span> Simulated data are in [[HDDM_Programmer%27s_Interface | HDDM format]]. (Richard) | + | * <span style="color:orange; font-size:2em">●</span> Simulated data are in [[HDDM_Programmer%27s_Interface |'''''HDDM format''''']]. (Richard) |
| − | * <span style="color:green; font-size:2em">●</span> [[Event generators]] generate simulated physics data (particle, momentum, track angle) (Simon & Malte) | + | * <span style="color:green; font-size:2em">●</span> [[Event generators|'''''Event generators''''']] generate simulated physics data (particle, momentum, track angle) (Simon & Malte) |
* <span style="color:red; font-size:2em">●</span> hdgeant4 models the measurements (detector hits) produced by those tracks (Richard) | * <span style="color:red; font-size:2em">●</span> hdgeant4 models the measurements (detector hits) produced by those tracks (Richard) | ||
* <span style="color:red; font-size:2em">●</span> mcsmear models the detector resolution which makes the measurements less exact. (Richard) | * <span style="color:red; font-size:2em">●</span> mcsmear models the detector resolution which makes the measurements less exact. (Richard) | ||
| − | * <span style="color:orange; font-size:2em">●</span> [[How_to_choose_software_versions_on_the_MC_submission_form |MCWrapper]] runs the above on demand. (Sean) | + | * <span style="color:orange; font-size:2em">●</span> [[How_to_choose_software_versions_on_the_MC_submission_form |'''''MCWrapper''''']] runs the above on demand. (Sean) |
| Line 27: | Line 27: | ||
'''Analysis Tree analysis''' | '''Analysis Tree analysis''' | ||
| − | * <span style="color:orange; font-size:2em">●</span> DSelectors are used to analyze "Analysis Trees" (see reaction filter above) to generate histograms of invariant mass etc. and generate highly reduced output trees for further analysis. [https://halldweb.jlab.org/wiki/index.php/Analyze_Analysis_Trees '''Analyze an Analysis Tree'''](Beni) | + | * <span style="color:orange; font-size:2em">●</span> DSelectors are used to analyze "Analysis Trees" (see reaction filter above) to generate histograms of invariant mass etc. and generate highly reduced output trees for further analysis. [https://halldweb.jlab.org/wiki/index.php/Analyze_Analysis_Trees '''''Analyze an Analysis Tree'''''](Beni) |
| − | * <span style="color:green; font-size:2em">●</span> [[FSRoot]] is an alternative to DSelectors that uses flat trees. (Ryan) | + | * <span style="color:green; font-size:2em">●</span> [[FSRoot|'''''FSRoot''''']] is an alternative to DSelectors that uses flat trees. (Ryan) |
| − | * <span style="color:green; font-size:2em">●</span> AmpTools ([https://github.com/mashephe/AmpTools GitHub], [https://github.com/mashephe/AmpTools/blob/master/AmpTools_User_Guide.pdf User Guide]) is used for partial wave analysis. GlueX specifics are documented [https://halldweb.jlab.org/wiki-private/index.php/AmpTools_Fits_Best_Practices here (PRIVATE)] (Malte) | + | * <span style="color:green; font-size:2em">●</span> AmpTools ([https://github.com/mashephe/AmpTools '''''GitHub'''''], [https://github.com/mashephe/AmpTools/blob/master/AmpTools_User_Guide.pdf '''''User Guide''''']) is used for partial wave analysis. GlueX specifics are documented [https://halldweb.jlab.org/wiki-private/index.php/AmpTools_Fits_Best_Practices '''''here (PRIVATE)'''''] (Malte) |
Revision as of 10:33, 7 February 2022
This page provides a very brief overview of the GlueX-specific software used between recording data and publishing results. In time, it should become populated with links to more detailed documentation.
Raw and reconstructed data – halld_recon
- ● Raw data is saved by the DAQ system in the EVIO file format and processed using programs in halld_recon. More details about the EVIO file format can be found here (Mark)
- There are three main databases:
- ● Run conditions (e.g. beam current, radiator) are stored in RCDB (web interface) (Naomi)
- ● Calibrations and other parameters used in reconstruction/analysis are stored in CCDB (web interface). (Naomi & Sean)
- ● Hall-D Online Skim System records data for individual raw data files HOSS (e.g. number of events per file, number of each trigger type, ... n.b. only for 2020 and later Run Periods) (David)
- ● hd_root is used to analyse EVIO and REST data with plugins for monitoring, Calibrations, and event reconstruction (Sean [calibrations] - & Mark)
- ● REST files are an HDDM format which stores reconstructed physics objects (no detector hit information) (Richard)
Simulated data - halld_sim
- ● Simulated data are in HDDM format. (Richard)
- ● Event generators generate simulated physics data (particle, momentum, track angle) (Simon & Malte)
- ● hdgeant4 models the measurements (detector hits) produced by those tracks (Richard)
- ● mcsmear models the detector resolution which makes the measurements less exact. (Richard)
- ● MCWrapper runs the above on demand. (Sean)
Reaction channel analysis
- ● ReactionFilter plugin is used to find the events corresponding to a particular reaction to make Analysis Trees. The basic ideas and steps are outlined here(Beni)
- ● Requests for analysis trees are collected via a webpage, and launched bundled together on the JLab farm. Lists for already existing trees are kept here. (Alex A)
Analysis Tree analysis
- ● DSelectors are used to analyze "Analysis Trees" (see reaction filter above) to generate histograms of invariant mass etc. and generate highly reduced output trees for further analysis. Analyze an Analysis Tree(Beni)
- ● FSRoot is an alternative to DSelectors that uses flat trees. (Ryan)
- ● AmpTools (GitHub, User Guide) is used for partial wave analysis. GlueX specifics are documented here (PRIVATE) (Malte)
