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

Comparison with YACS #21

Open
ae86208 opened this issue Jun 1, 2020 · 1 comment
Open

Comparison with YACS #21

ae86208 opened this issue Jun 1, 2020 · 1 comment

Comments

@ae86208
Copy link

ae86208 commented Jun 1, 2020

There is something in common. https://github.com/rbgirshick/yacs

@zxytim
Copy link
Collaborator

zxytim commented Jul 31, 2020

There are at least two major advantages comparing hpman to yacs:

  1. No need of forward-declaration
    • Using hpman, you can declare a hyperparameter wherever you want. However, in YACS, prior to using a hyperparameter, you have to declare it first. The example given in yacs's README clearly shows that.
  2. Able to gather the meta info (file, lineno, default values, all appearances) of hyperparameters prior to running any code
    • In hpman, we statically parsed the code to gather all information we need. We could print out the code context of every single use of all hyperparameters, as shown in README, batteries-included. We believe recovering the context of writing a piece of code is fundamental to code-readability.
    • While in yacs, there's no easy way to do that.
    • This also eases the integration of hpman to downstream applications, such as hyperparamter optimization frameworks, IDEs, etc.

Besides, both hyperparameter managing framework supports common basic features like save/load from a config file, override hyperparameter values, etc.

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