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

Hyperparam Table #167

Open
bitfort opened this issue Jan 10, 2019 · 2 comments
Open

Hyperparam Table #167

bitfort opened this issue Jan 10, 2019 · 2 comments
Labels
Backlog An issue to be discussed in a future Working Group, but not the immediate next one.

Comments

@bitfort
Copy link

bitfort commented Jan 10, 2019

How can we reduce the need to parameter tune params and optimizers and "borrow" parameters during review?

The proposal is to create a hyper parameter table which gives you the HPs to use based on the batch size and precision (and solve the optimizer choice problem).

SWG Notes:
This is a big topic being covered by Special Topics.

@bitfort bitfort added the Next Meeting Item to be discussed in the next Working Group label Jan 10, 2019
@bitfort
Copy link
Author

bitfort commented Apr 11, 2019

SWG Notes:

There is a lot desire to have such a thing. We intend to address this through logging in the submissions. Currently, we plan on using the same general approach to hyper parameters as we used for v0.5; pending future conversation on this topic.

This is a design criteria for logging.

We may want to do some sharing of parameters before v0.6 submission. There will be further discussion for v0.6.

@bitfort bitfort added Backlog An issue to be discussed in a future Working Group, but not the immediate next one. and removed Next Meeting Item to be discussed in the next Working Group labels Feb 13, 2020
@bitfort
Copy link
Author

bitfort commented Feb 13, 2020

We will keep working in this direction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog An issue to be discussed in a future Working Group, but not the immediate next one.
Projects
None yet
Development

No branches or pull requests

1 participant