Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SCU][Docathon][Add API Legend No.44] repeat_interleave #6988

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

yangrongxinuser
Copy link

Add image of expand and rewrite repeat_interleave_cn.rst
中文文档链接:docs/api/paddle/ repeat_interleave_cn.rst
@tianhaodongbd
@sunzhongkai588

Copy link

paddle-bot bot commented Nov 20, 2024

感谢你贡献飞桨文档,文档预览构建中,Docs-New 跑完后即可预览,预览链接:http://preview-pr-6988.paddle-docs-preview.paddlepaddle.org.cn/documentation/docs/zh/api/index_cn.html
预览工具的更多说明,请参考:飞桨文档预览工具

@CLAassistant
Copy link

CLAassistant commented Nov 20, 2024

CLA assistant check
All committers have signed the CLA.

@yangrongxinuser
Copy link
Author

Comment on lines +8 to +10
tensor.repeat_interleave 按指定次数重复张量的每个元素。
以上图为例,输入张量 [[1, 2, 3], [4, 5, 6]],重复次数为 [3, 2, 1],表示第1列元素重复3次,第2列重复2次,第3列重复1次。
最终输出为一维张量 [1, 1, 1, 2, 2, 3, 4, 4, 4, 5, 5, 6]。
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • 图例说明放在 API 说明简介的下面,参数部分的上面,参考示例 PR
  • 图例说明里要引用图片,才会在文档里显示
  • 这段说明里似乎也是错的,没有说明参数 axis 的值。看起来是按列重复。那说明参数 axis=1,最终结果不应该是 [[1, 1, 1, 2, 2, 3], [4, 4, 4, 5, 5, 6]] 么,而且你的说明和图例最终结果也不一致

请仔细攥写文档,确保图例说明和图例一致,输入输出、重要的参数均要注明并且确保正确,自己跑一遍代码试试。并且站在阅读文档的开发者角度写图例

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • 二维 tensor 以矩阵的样式表示就行,参考下图,并标明 axis=0 和axis =1
    image
  • 加上参数 axis 的值

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contributor HappyOpenSource Pro 进阶版快乐开源活动,更具挑战性的任务
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants