Welcome to chanser’s documentation!

• Getting Started
  • Installation
  • Creating your own final state class
  • Configuring an analysis
  • Running the analyse
• Combitorial Events
  • Combitorials of the first kind
  • Combitorials of the second kind
  • Combitorials of the third kind
  • Combining Combitorials of different kinds
  • Setting combitorial behaviour for configured FinalState objects
• HipoData
• Actions
  • StartTime Actions
  • Particle Data Actions
  • Particle Cut Actions
  • Particle Correction Actions
  • Quick Usage
• Masking particles
  • Masking Calorimeter split-off clusters
  • Masking Radiated photons
  • Masking Secondary Neutron Clusters
• CHANSER analysis database
  • Including Parameter Lookup in Code
  • Defining Parameters in .db files
• CLAS12 DataBases
  • ccdb
  • rcdb
  • qadb
• CLAS12 Standard Actions
  • Standard Run Group A Actions
  • Neutron path length correction FDn_pathCorrection
• Handling Simulated Data
  • Constructing generated truth distributions
  • Constructing reconstructed distributions
  • Constructing accepted truth distributions and truth matching
  • Correcting the FT particle z-vertex
• Machine Learning interface : TMVA

Some preamble

• FinalState

  chanser is designed to analyse specific particle final states. In practise this can be achieved by detecting a subset of the final particles (missing particles) and so you may simulatanously define various topologies for your final state.

  For example, you may be interested in reactions with an e-, proton, pi+ and pi-. These are your final state particles. But you may be able to analyse events where, for example, the proton has not been detected. So you may define 1 topology with an exclusive final state (detect e-,p,pi+,pi-) and one with just (e-,pi+,pi-).