monte-carlo

reconstruction and analysis launch version set files

markito31 Comment
  • reconstruction (recon) and analysis (ana) xml’s do not have complete set of software (missing halld_sim, mcwrapper, etc.) as put together by the launcher
  • new versions of a recon launch can be generated due to
    • calibrations (no new unique version set needed)
    • new version(s) of packages (needs new recon version set)
  • new versions of ana launches can be generated due to
    • different channels
    • halld_recon changes (e.g., analysis library changes)
    • a new recon launch (i.e., new set of REST files)
  • ana halld_recon version will indicate the halld_version that was used to create the root trees from the REST files (i.e., the analysis library)
    • [old, wrong wording of this bullet: ana halld_recon version will always match halld_recon version of recon launch that created the ana input REST files — correction made 4/12/21]
  • versions of packages that depend on halld_recon may or may not have different versions from ana launch to ana launch, they are not used in the launch itself
  • when a new recon launch is done because of calibrations, make a copy of the xml file, use same halld_recon version number, use same halld_sim, etc., name it with the new recon launch name and increment sub-version number, _n
  • when a new version set is needed to get updated halld_recon-dependent packages, increment sub-version, _n.
  • Make a new ana xml for every analysis launch, no need for a sub-version number if halld_recon-dependent packages are omitted
  • In correlation files, indicate the correlations between reconstruction launches and analysis launches. One reconstruction launch may correspond to multiple recon version sets (multiple sub-version numbers, with different halld_recon-dependent packages) so correlation notation should not specify a sub-version.