Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chronos: Move orca.automl.metrics to Chronos #42

Open
TheaperDeng opened this issue Oct 18, 2021 · 1 comment
Open

Chronos: Move orca.automl.metrics to Chronos #42

TheaperDeng opened this issue Oct 18, 2021 · 1 comment

Comments

@TheaperDeng
Copy link

  • Since orca.automl is used for customized model for any area, while most of the metrics in orca.automl.metrics is designed and optimized for time series tasks.
  • The built-in metrics in orca.automl can be a simple map between string and sklearn.metrics
  • This will help Chronos to be self-contained.
@shanyu-sys
Copy link
Contributor

shanyu-sys commented Oct 19, 2021

Since in ·orca.automl·, AutoXGBoost also uses metrics, it might not be convenient to directly move metrics from orca to chronos.Otherwise, orca need depend on chronos.

For chronos, in the cases of

  1. Single node acceleration with nano: we could directly use TorchMetrics in pytorch-lightning, which might also be more efficient regarding both performance and memory.
  2. Distributed training or distributed tuning, both of which will depend on orca and could choose to use metrics in orca.automl.

[TBD]However, we might move metrics to nano, since it is for single node only...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants