Physics Lists and Validation tools: Workplan 2019

Ongoing activities

  • Physics Lists
  • Documentation of physics lists(~All)
  • Maintain physics constructors and physics lists, including support (~All)
  • Develop and maintain physics list level test (test23) (Julia)
    • Monitor performance of existing production and/or experimental physics lists, focusing  on intensity frontier experiments, including beamline simulation projects (e.g. neutrino flux or Mu2e beamline) 
      • Analyze production of hadrons from the first hadronic inelastic interaction
      • If necessary, analyze secondary interactions (e.g. in the primary target) and benchmark results vs relevant thick target data (once such data are explored and added) 
      • Compose new physics lists, if needed
  • Physics List Validation Using Beam Simulation (Kihyeon, Soonwook)
  • Validation tools
  • Collecting and evaluate experimental data sets (Hans, Julia, Krzysztof, Robert, with input from others)
  • Support for changing of model parameters (Hans, Julia, Krzysztof, Robert)
  • geant-val:
  • Release, candidate and reference tag testing for physics performance on Grid (Alberto, Dmitri, Witold)
  • maintenance & further developments  (Dmitri, Grigory)

Development Items

  • Physics Lists
  • Recommendation / Documentation of physics lists for specific use cases ( ~ All)
  • Documentation of physics lists examples ( Alex, in collaboration with documentation wg.)
  • complete automated physics list documentation and integrate in web documentation (Gunter,  Alex)
  • Physics lists factories
    • Continue efforts to allow proper physics list/constructor registration behavior on Windows static library builds (Robert H.)
  • Review of physics lists code
    • Evaluate possibility to eliminate template mechanism in physics lists, implement if possible. (Gunter, Vladimir)
    • Define MT cleanup strategy for builders and physics processes in MT mode (missing MP)
    • remove independent version number (Gunter, Vladimir)
    • review use of DataQuestionaire (Vladimir, Gunter)
    • Deprecate or remove Setcuts from interface (Vladimir, Gunter)
  • produce graphs showing overlap of models (currently done by hand), very useful as a simple graph for new users (missing MP)
  • Create set-up to run regression testing at process level (missing MP)
  • Validation tools
  • DoSSiER Database and web application (Hans with feedback from collaborators)
    • define a human readable json data exchange format that allows for data exchange between databases at FNAL and CERN (Hans)
    • enable SSO authentication ( Hans)
    • periodic upload of grid test results, e.g. for SimplifiedCalo, for public releases to DoSSiER. (Hans, Dmitri)
    • extend set of experimental data used in validation (all…)
    • complete the tool for automated upload of results to DoSSiER (Hans, Julia)
  • Maintain relevant elements of artg4tk - a framework that provides an interface between Geant4 and the art framework which is used by the intensity frontier experiments. Artg4tk ensures that the intensity frontier experiments have access to the latest developments in Geant4 and that interfaces are kept up to date. Artg4tk is used to study experimental observables that are of interest for the intensity frontier experiments. In addition artg4tk is used to support the changing of model parameters framework and to test the relevant Geant4 API (Hans, Julia).