Cudla input Tensort, output Tensort data layout, quantization, and inverse quantization issues
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.6k
- Forks
- 2.4k
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
I ran a command
./cuDLAStandaloneMode ../model_test/joint_model_cygnus_simple_batch1_512960_230220_dla_opt_sub_1.cudla 2
The output tensor information is as follows
Printing input tensor descriptor
TENSOR NAME : input'
size: 1966080
dims: [1, 4, 512, 960]
data fmt: 2
data type: 4
data category: 0
pixel fmt: 12
pixel mapping: 0
stride[0]: 1
stride[1]: 3840
stride[2]: 0
stride[3]: 0
-----------------------------------------tensor input:0
Printing output tensor descriptor
TENSOR NAME : M0_519'
size: 131072
dims: [1, 64, 32, 60]
data fmt: 1
data type: 4
data category: 3
pixel fmt: 0
pixel mapping: 0
stride[0]: 1
stride[1]: 64
stride[2]: 2048
stride[3]: 2048
-----------------------------------------tensor output:0
CUDLA_DATA_FORMAT_NHWC,The format of the input tensor is CUDLA_DATA_FORMAT_NHWC and the type is int8.
I have an input to an NCHW float, and I should get the quantization parameters and write them into input tensor in CUDLA_DATA_FORMAT_NHWC format.I don't quite understand what this street means.
Then where can I get the quantized parameters of Tensor.
The output tensort is int8, CUDLA_ DATA_ FORMAT_ NCHW format. How should I inversely convert it to float 32 and convert it to nchw format.
I didn't find its scale and zero in the model for either Tensor_ Parameter of point
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the cuDLAStandaloneMode command and the input/output tensor descriptor output in this report. Determine how the reported NHWC/NCHW layouts, strides, int8 quantization, and inverse quantization parameters are represented for the model; the issue provides no source file or test, so completion would require a reproducible explanation or correction validated against the shown tensors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100