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.

Sign up for GitHub

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

Jump to bottom

Determine if Posterize should be included in RandAugment: #169

Closed
LukeWood opened this issue Mar 10, 2022 · 0 comments
Closed

Determine if Posterize should be included in RandAugment: #169

LukeWood opened this issue Mar 10, 2022 · 0 comments

Comments

@LukeWood
Copy link
Contributor

why do we need to implement Posterize, when the paper shows that posterize always has a detrimental impact 🤔

It is not clear, I will be emailing a paper author to find out.
@bhack bhack mentioned this issue May 4, 2022
Open
freedomtan pushed a commit to freedomtan/keras-cv that referenced this issue Jul 20, 2023
@mattdangerw
Add layers.MultiHeadAttention (keras-team#169)
8b94f2e 
* Add layers.MultiHeadAttention

* Update build/compute_output_signature argument checks

We do not definitively know which arguments are tensor arguments
at any given invocation (e.g. arguments with a None value may be tensor
arguments).

So rather than check that the build signature matches perfectly with
tensor call arguments, we will check the build signature arguments match
with some call argument.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LukeWood