[GitHub] [incubator-mxnet] yangfly opened a new issue #14515: Should gluon layer support **name** field?

[GitBox <gi...@apache.org>]

yangfly opened a new issue #14515: Should gluon layer support **name** field?
URL: https://github.com/apache/incubator-mxnet/issues/14515
 
 
   At present, the **name** of **Gluon** layer is automatically extended to `xxx/operator0_fwd`, based on `name_scope`, which embodies modularization and avoids naming conflicts. However, the **name** field is not currently supported, resulting in a lack of flexibility. 
   
   for example
   ```
   gluon.nn.Conv2D(10, 3)  # xxx/conv0_fwd
   ```
   Should **Gluon** layer also support custom **name** like `Symbol`. Internally, only layer without user defined `name` are automatically named. 
   ```
   gluon.nn.Conv2D(10, 3, name='conv1')
   ```
   This feature is useful in the following scenarios
   - `Gluon` models can be aligned with `Symbol` models or other framework, and users can specify more consistent naming method.
   - `Gluon` models can be compared more intuitively with the net structure in the papers with `viz.print_summary` or `viz.plot_network`.
   - `Symbol` can be load more conveniently from `Gluon` with `load_parameters`.
   
   Welcome to this discussion!

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services