repo_name
stringclasses 28
values | pr_number
int64 1.86k
122k
| pr_title
stringlengths 5
204
| author
stringlengths 3
58
| git_commit_prev
stringlengths 40
40
| git_commit_curr
stringlengths 40
40
| date_created
stringlengths 25
25
| date_merged
stringlengths 25
25
| query
stringlengths 12
65.6k
| context_file_path
stringlengths 6
233
| label
int64 -1
1
| language
stringclasses 5
values |
|---|---|---|---|---|---|---|---|---|---|---|---|
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/backend/tensorflow/nn.py | 1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/backend/jax/nn.py | 1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./examples/keras_io/vision/convmixer.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/convolutional/conv_transpose_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/optimizers/__init__.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/attention/attention_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/reshaping/reshape_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/convolutional/__init__.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/optimizers/adagrad.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/backend/common/name_scope_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/utils/naming.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/preprocessing/text_vectorization.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/reshaping/zero_padding2d.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/preprocessing/index_lookup.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/utils/python_utils.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./guides/writing_a_custom_training_loop_in_jax.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./examples/keras_io/generative/text_generation_with_miniature_gpt.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/metrics/reduction_metrics_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/preprocessing/rescaling_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./examples/keras_io/tensorflow/generative/dcgan_overriding_train_step.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/backend/common/variables.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/models/__init__.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/regularization/gaussian_noise_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/losses/losses.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/applications/resnet.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/rnn/gru.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/backend/numpy/layer.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./guides/writing_a_custom_training_loop_in_torch.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/regularization/gaussian_noise.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./examples/keras_io/vision/learnable_resizer.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/ops/numpy_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/utils/jax_utils.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./examples/keras_io/structured_data/tabtransformer.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/metrics/regression_metrics.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/activations/prelu_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/ops/numpy.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/preprocessing/string_lookup_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/utils/image_utils.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/optimizers/schedules/__init__.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/backend/tensorflow/sparse.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/pooling/global_average_pooling1d.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/backend/common/backend_utils.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/convolutional/separable_conv2d.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/trainers/epoch_iterator.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/utils/timeseries_dataset_utils.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/applications/vgg16.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/legacy/saving/legacy_h5_format_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/preprocessing/index_lookup_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/backend/common/compute_output_spec_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./requirements-tensorflow-cuda.txt | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/callbacks/learning_rate_scheduler_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/regularization/activity_regularization_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./kokoro/github/ubuntu/gpu/tensorflow/continuous.cfg | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/optimizers/adamax_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./guides/sequential_model.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/backend/torch/optimizers/torch_sgd.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/preprocessing/integer_lookup.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/rnn/conv_lstm3d.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/backend/torch/optimizers/torch_adam.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/convolutional/base_depthwise_conv.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./integration_tests/tf_distribute_training_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/convolutional/conv_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./integration_tests/numerical_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/reshaping/flatten.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/mixed_precision/__init__.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/callbacks/callback_list.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/callbacks/history.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/utils/image_dataset_utils_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/constraints/constraints_test.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/utils/text_dataset_utils.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/utils/__init__.py | -1 | python |
keras-team/keras | 18,860 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid` | james77777778 | 4d362cea4236637746d373623b89be37dce9660e | f0b7062e4c6a62c521af491b09d97f009b1add0b | 2023-12-01 02:02:15+00:00 | 2023-12-01 05:07:34+00:00 | Add `hard_swish` to `ops.nn` and dtype tests for `hard_swish` and `hard_sigmoid`. This PR:
- add `hard_swish` to `ops.nn` to ensure consistency for all activation functions in the codebase
- add dtype inference tests for `hard_sigmoid` and `hard_swish`
I plan to add more dtype inference tests for `ops.nn`. I think we can focus on float types for these ops, as it's uncommon to use them with integer types.
Is it a good idea (adding more tests / skipping integer types for `ops.nn`)? | ./keras/layers/rnn/gru_test.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/applications/mobilenet_v3.py | 1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/applications/imagenet_utils_test.py | 1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/activations/activations_test.py | 1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/applications/applications_test.py | 1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/activations/activations.py | 1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/activations/__init__.py | 1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/backend/torch/optimizers/torch_nadam.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./examples/keras_io/tensorflow/vision/mobilevit.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/backend/common/name_scope.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./examples/demo_custom_jax_workflow.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/utils/python_utils_test.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/optimizers/ftrl.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./examples/keras_io/vision/token_learner.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/optimizers/optimizer.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/datasets/california_housing.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/layers/preprocessing/resizing_test.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./examples/keras_io/vision/keypoint_detection.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/utils/sequence_utils.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/backend/tests/compute_output_spec_test.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/metrics/reduction_metrics.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/backend/tensorflow/distribution_lib.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/callbacks/callback_list.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./examples/keras_io/timeseries/timeseries_weather_forecasting.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/utils/backend_utils.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/callbacks/learning_rate_scheduler.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/backend/common/__init__.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/random/seed_generator.py | -1 | python |
keras-team/keras | 18,852 | Add hardswish | james77777778 | 9c62839cbb0e54b7bac09ce20471a0dfaa65ff55 | 724321c7b39a90f6125b79931284aa9932c673a0 | 2023-11-29 22:44:54+00:00 | 2023-11-30 05:45:38+00:00 | Add hardswish. Fix #18842
This PR has introduced HardSwish and replaced custom ops with `layers.HardSwish` in `keras/applications/mobilenet_v3.py` | ./keras/layers/core/einsum_dense.py | -1 | python |