# \[Question\] May all op has it's own name?

**URL:** <https://discuss.tvm.apache.org/t/question-may-all-op-has-its-own-name/13222>\
**Category:** Questions\
**Created:** [July 28, 2022, 1:39pm UTC](https://discuss.tvm.apache.org/t/question-may-all-op-has-its-own-name/13222 "2022-07-28T13:39:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chenugray](https://discuss.tvm.apache.org/letter_avatar_proxy/v4/letter/c/3be4f8/32.png) [@chenugray](https://discuss.tvm.apache.org/u/chenugray)\
**Post date:** [July 28, 2022, 1:39pm UTC](https://discuss.tvm.apache.org/t/question-may-all-op-has-its-own-name/13222/1 "2022-07-28T13:39:12Z")

</div>

When I Import a model to tvm model, always I don’t know what op correspoding to. when I debug with some ops with accuracy problem, it’s hard for me. So how about every import op has it’s own name, not just the name Node\_244, Node\_378?

when a conv2d op has name “resnet\_v1\_50/block4/unit\_3/bottleneck\_v1/conv3/Conv2D”, convert from frontend take this name as op name.

when we legalize some op, it decompose the op with scope name.

like Op SquaredDifference with name `bert/encoder/layer_0/output/LayerNorm/moments/SquaredDifference`, the op will be composed by some trival op. so the names will be `bert_encoder_layer_0_output_LayerNorm/moments/SquaredDifference_mean`，`bert_encoder_layer_0_output_LayerNorm/moments/SquaredDifference_subtract`

this may be too long for a name. maybe its a good for debugging?
