Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • athena athena
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Jira
    • Jira
  • Merge requests 160
    • Merge requests 160
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Repository
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • atlasatlas
  • athenaathena
  • Merge requests
  • !55499

Legacy Simulation Configuration Module Renaming (Preparation for ComponentAccumulator Migration) (part 2)

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged John Derek Chapman requested to merge jchapman/athena:G4AtlasConfigRenaming_22.0 into 22.0 Jul 28, 2022
  • Overview 5
  • Commits 1
  • Pipelines 2
  • Changes 14

The old-style simulation configuration uses ConfiguredFactory. This uses configuration methods defined in ...Config.py modules which are associated with a component name in various PackageNameConfigDb.py modules.

The new ComponentAccumulator-based configuration tends to use ...Config.py as the naming convention for the configuration modules, but in Simulation we have typically used ...ConfigNew.py to avoid a naming clash. This MR renames all the ConfiguredFactory ...Config.py modules to ...ConfigLegacy.py for packages under Simulation/G4Atlas. I will rename the ComponentAccumulator-based modules in a follow-up merge request, but I wanted to avoid this one getting too large.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: G4AtlasConfigRenaming_22.0