3. Command Line Tools

The Belle2 Software provides a number of command line tools for general use, including tools to work with files, to help with debugging/testing or for validation purposes. The general rule is that all tools which are intended to be useful for most users should start with the name b2 followed by a usage category, for example b2file for all tools for file handling. Sub categories should be added using - signs, for example b2file-metadata-show is a tool intended to show the metadata embedded into files created by the Belle2 Software.

• 3.1. basf2: The Main Belle2 Software Executable
• 3.2. Tools for file handling
  • 3.2.1. b2file-metadata-show: Show the metadata of a basf2 output file
  • 3.2.2. b2file-metadata-add: Add/Edit LFN in given file
  • 3.2.3. b2file-catalog-add: Add a file to a local XML file catalog
  • 3.2.4. b2file-check: Check a basf2 output file for consistency
  • 3.2.5. b2file-merge: Merge multiple basf2 output files
  • 3.2.6. b2file-mix: Create a run of mixed data from a set of input files
  • 3.2.7. b2file-remove-branches: Create a copy of a basf2 output file removing a list of given branches in the process
  • 3.2.8. b2file-size: Show detailed size information about the content of a file
  • 3.2.9. b2file-normalize: Reset non-reproducible root file metadata and optionally the file name in the metadata
  • 3.2.10. b2file-md5sum: Calculate a md5 checksum of a root file content excluding the root metadata
• 3.3. Testing Tools
  • 3.3.1. b2test-units: Run unittests
  • 3.3.2. b2test-scripts: Run framework tests
• 3.4. Tools which will provide you help
  • 3.4.1. b2help-modules: List available basf2 modules and ask about their details
  • 3.4.2. b2help-particles: List particles used in the event generator
  • 3.4.3. b2help-variables: List available variables in the analysis package
• 3.5. Tools to help with debugging and checking code quality
  • 3.5.1. b2code-module: Create a source code template for a module
  • 3.5.2. b2code-memoryusage: Show memory usage of a program
  • 3.5.3. b2code-findsymbol: Look for a given C++ symbol
  • 3.5.4. b2code-doxygen-warnings: Show warnings when running doxygen
  • 3.5.5. b2code-classversion-check: Perform sanity checks on ROOT class versions
  • 3.5.6. b2code-classversion-update: Update linkdef information for sanity checks
  • 3.5.7. b2code-cppcheck: Run cppcheck static analyzer
  • 3.5.8. b2code-parallel_processing-benchmark: Measure multi-core performance
  • 3.5.9. b2code-sphinx-build: Build the sphinx documentation
  • 3.5.10. b2code-sphinx-warnings: Show all the warnings when building the documentation
• 3.6. b2conditionsdb: Conditions DB interface
  • 3.6.1. Sub-command b2conditionsdb diff
  • 3.6.2. Sub-command b2conditionsdb download
  • 3.6.3. Sub-command b2conditionsdb dump
  • 3.6.4. Sub-command b2conditionsdb iov
  • 3.6.5. Sub-command b2conditionsdb legacydownload
  • 3.6.6. Sub-command b2conditionsdb tag
    • Sub-command b2conditionsdb tag clone
    • Sub-command b2conditionsdb tag create
    • Sub-command b2conditionsdb tag invalidate
    • Sub-command b2conditionsdb tag list
    • Sub-command b2conditionsdb tag merge
    • Sub-command b2conditionsdb tag modify
    • Sub-command b2conditionsdb tag publish
    • Sub-command b2conditionsdb tag runningupdate
    • Sub-command b2conditionsdb tag show
    • Sub-command b2conditionsdb tag state
  • 3.6.7. Sub-command b2conditionsdb upload
  • 3.6.8. b2conditionsdb-extract: Extract payload for a run range and save as TTree
  • 3.6.9. b2conditionsdb-recommend: Recommend a global tag to analyse a given file
  • 3.6.10. b2conditionsdb-request: Request inclusion of payloads in official global tag
• 3.7. Tools for luminosity
  • 3.7.1. b2info-luminosity: Show the luminosity corresponding to a given experiment(s)
• 3.8. Tools for ParticleStats
  • 3.8.1. b2plot-particleStats: Analyze a json produced by ParticleStats to produce plot of retention rate and pass matrix
    • Optional Arguments