Components

[mousyball]

NOTE

• Transform

  • Use config to define the status of transform and output keys.
  • Visualization

• Dataset

  • Handle with Registry. The purpose is to leave flexibility for customized computation in the dataset.

• Network

  • Distinguish by different tasks. (detection/segmentation/others...)
  • Loss builder

• Config and Registry

  • Use config and registry for management.

Features

• Use fvcore for registry and config
• Network Builder
• Network
  • INetwork -> BaseNetwork (w/ a module only defines the layers connection) -> Network (registered network)
  • Wrapper class for communication with trainer
  • BaseNetwork includes a network module that only defines the layer connection.
• Config
  • Trainer and Network
  • YAML with Inheritance
  • NAME is required for components.
• Transform Visualization ([feat] Basic arch of transform visualization #20, [refactor] transform visualization #21)

Test

• Hook setting

Docs

• Design thinking
• Simple guide for entire customized setting.

TODOs

• Hierarchical Config (base & custom / network & custom) ([feat] Support config with multiple sources in _BASE_ #16)

• pytest ([test] Test for config, network and loss builder #15)

  • hook
  • test for builder, config, registry

• Docs

  • Registry
  • Config
  • Network
  • Transform Visualization
  • Simple Guide