-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Specify hyperparameter ranges for blocks #1420
Comments
@haifeng-jin I would be happy to take this one |
@lc0 Great! Thank you. Let me know if you have any questions. |
@lc0 Are you planning to take all the blocks? Can you share something with me? |
@dineshkumarsarangapani we can use this issue for coordination, so if you are taking any of the blocks, feel free to just mention it here |
@lc0 Thank you. I will work on BertBlock and ConvBlock today and raise a PR in a day or 2. |
@haifeng-jin we need to re-open this one again. Also how do you feel about adding a checklist of blocks to do? |
@haifeng-jin we have to open this ticket. I think this is not done completely. |
I can take up Embedding, Transformer, and MultiHeadSelfAttention block in the coming few days. |
@mandalbiswadip Thank you! please do. We don't have other people working on this right now. |
I can take XceptionBlock |
Partially fixes keras-team#1420 Added hyperparameter range for XceptionBlock
Partially fixes keras-team#1420 Added hyperparameter range for XceptionBlock
looking for low hanging fruits |
Hey, NickSmyr and I would like to contribute to this issue, so we are wondering whether it is still relevant and which blocks still need changes. |
@Neproxx Great to see you like to contribute! |
@haifeng-jin Just added a PR #1708 for one block |
Hey @haifeng-jin , Neproxx and I need to contribute to an open source project in the context of a university course (KTH DevOps course). We have proposed a PR a week ago (see #1710 ) for this issue and it would help us out a lot if you could review it and either merge it or tell us about necessary changes. If everything is fine, we would pose a PR for the rest of the hyperparameters that need to be changed. It is important to us to have this done within the next 10 days, so we would be very greatful if you could spare some time to look at the PR. Many thanks! |
@NickSmyr The PR is merged. Thanks for your contribution! |
@haifeng-jin yes, that was the last PR from our side. |
Feature Description
We want to enable the users to specify the value ranges for any argument in the blocks.
The following code example shows a typical use case.
The users can specify the number of units in a DenseBlock to be either 10 or 20.
Code Example
Note
Each pull request should only change one hyperparameter in one of the blocks.
Solution
Example pull requests are #1419 #1425 .
Here are the steps to follow:
from kerastuner.engine import hyperparameters
.The text was updated successfully, but these errors were encountered: