Support for Recurrent layers for Quantization Aware Training.
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- keras, python, tensorflow
调研方向
首先阅读 default_8bit_quantize_registry.py 第 159 行附近的内容,此处禁用了对 RNN 的支持,并使用报告中的 TensorFlow 2.15 GRU 案例重现 quantize_apply 失败。调查自定义 QuantizeConfig 以及随后出现的 H5 保存错误。当循环层通过 quantize_apply 支持默认的 8 位量化,并且量化后的模型能够成功保存时,即表示完成。
由索引模型根据 Issue 内容生成。
描述
System information
- TensorFlow version (you are using): 2.15
- Are you willing to contribute it (Yes/No): Yes
Motivation
I am trying to train RNN model with quantization aware training for embedded devices.
Describe the feature
I am looking for a way to train with default 8bit weights & activations quantization using quantize_apply API without passing in custom config.
Describe how the feature helps achieve the use case
Describe how existing APIs don't satisfy your use case (optional if obvious)
I tried to use quantize_apply API but I received this error.
RuntimeError: Layer gru:<class 'keras.src.layers.rnn.gru.GRU'> is not supported. You can quantize this layer by passing a `tfmot.quantization.keras.QuantizeConfig` instance to the `quantize_annotate_layer` API.
After using quantize_annotate_layer, I was able to train the model but Model fails to save with following error:
keras.models.save_model(model, filepath=model_filename, save_format="h5")
Traceback (most recent call last):
File "/workspaces/project-embedded/syntiant-ndp-model-converter/examples/train_audio_model.py", line 169, in <module>
keras.models.save_model(model, filepath=model_filename, save_format="h5")
File "/home/vscode/tf_venv/lib/python3.10/site-packages/keras/src/saving/saving_api.py", line 167, in save_model
return legacy_sm_saving_lib.save_model(
File "/home/vscode/tf_venv/lib/python3.10/site-packages/keras/src/utils/traceback_utils.py", line 70, in error_handler
raise e.with_traceback(filtered_tb) from None
File "/home/vscode/tf_venv/lib/python3.10/site-packages/h5py/_hl/group.py", line 183, in create_dataset
dsid = dataset.make_new_dset(group, shape, dtype, data, name, **kwds)
File "/home/vscode/tf_venv/lib/python3.10/site-packages/h5py/_hl/dataset.py", line 163, in make_new_dset
dset_id = h5d.create(parent.id, name, tid, sid, dcpl=dcpl, dapl=dapl)
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "h5py/h5d.pyx", line 137, in h5py.h5d.create
ValueError: Unable to synchronously create dataset (name already exists)
I used following QuantizeConfig
class GruQuantizeConfig(tfmot.quantization.keras.QuantizeConfig):
# Configure how to quantize weights.
def get_weights_and_quantizers(self, layer):
return [
(
layer.cell.kernel,
LastValueQuantizer(
num_bits=8, symmetric=True, narrow_range=False, per_axis=False
),
),
(
layer.cell.recurrent_kernel,
LastValueQuantizer(
num_bits=8, symmetric=True, narrow_range=False, per_axis=False
),
),
]
# Configure how to quantize activations.
def get_activations_and_quantizers(self, layer):
return [
(
layer.cell.activation,
MovingAverageQuantizer(
num_bits=8, symmetric=False, narrow_range=False, per_axis=False
),
),
(
layer.cell.recurrent_activation,
MovingAverageQuantizer(
num_bits=8, symmetric=False, narrow_range=False, per_axis=False
),
),
]
def set_quantize_weights(self, layer, quantize_weights):
# Add this line for each item returned in `get_weights_and_quantizers`
# , in the same order
layer.cell.kernel = quantize_weights[0]
layer.cell.recurrent_kernel = quantize_weights[1]
def set_quantize_activations(self, layer, quantize_activations):
# Add this line for each item returned in `get_activations_and_quantizers`
# , in the same order.
layer.cell.activation = quantize_activations[0]
layer.cell.recurrent_activation = quantize_activations[1]
# Configure how to quantize outputs (may be equivalent to activations).
def get_output_quantizers(self, layer):
return []
def get_config(self):
return {}
I looked at the source code. It seems that the support for RNN is disabled here for some reason.
I was wondering if this can be enabled back?
- 主要语言
- Python
- 星标
- 1.6k
- 派生
- 349
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
tensorflow/model-optimization 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
tensorflow/model-optimization#1301 · 1 条评论 ·
-
bug
难度 4/5 3-5 天 新手友好度 48/100
tensorflow/model-optimization#1272 ·
-
bug
难度 3/5 1-2 天 新手友好度 50/100
tensorflow/model-optimization#1270 · 2 条评论 ·
-
bug
难度 2/5 1-3 小时 新手友好度 48/100
tensorflow/model-optimization#1241 ·
-
bug
难度 4/5 3-5 天 新手友好度 35/100
tensorflow/model-optimization#1182 · 1 条评论 ·
查看 tensorflow/model-optimization 的全部 Issue
相似的 Issue
-
pydanty:is-working
难度 2/5 1-3 小时 新手友好度 78/100
pydantic/pydantic-ai#8843 ·
维护者通常 1 天内回复
-
breaking change enhancement server
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
needs-triage
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复