Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M metaseq
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 95
    • Issues 95
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 41
    • Merge requests 41
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Administrator
  • metaseq
  • Issues
  • #7
Closed
Open
Issue created Mar 14, 2022 by Administrator@rootOwner

Figure out potential duplication in ConfigStore

Created by: suchenzang

By the time we get to our first convert_namespace_to_omegaconf call, we already have:

# from hydra.core.config_store import ConfigStore
(Pdb) cs = ConfigStore.instance()
(Pdb) cs.repo.keys()
dict_keys(['hydra', '_dummy_empty_config_.yaml', 'base_config.yaml', '_name.yaml', 'common.yaml', 'common_eval.yaml', 'distributed_training.yaml', 'dataset.yaml', 'optimization.yaml', 'checkpoint.yaml', 'generation.yaml', 'eval_lm.yaml', 'model.yaml', 'task.yaml', 'criterion.yaml', 'optimizer.yaml', 'lr_scheduler.yaml', 'bpe.yaml', 'tokenizer.yaml', 'model', 'optimizer', 'lr_scheduler', 'bpe', 'task'])

which seems to have some redundancy in yaml vs non-yaml keys. Figure out if we can remove the *.yaml keys somehow.

Assignee
Assign to
Time tracking