Update CRNN readme #191
Merged
Update CRNN readme #191
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SamitHuang
reviewed
Apr 25, 2023
configs/rec/crnn/README.md
Outdated
There was a problem hiding this comment.
这里补充下 training set, validation set分别多少张images.
There was a problem hiding this comment.
Inference的数据也合进去。分Training performance 和 Inference performance两张表。
HaoyangLee
reviewed
Apr 26, 2023
configs/参数配置文档说明.md
Outdated
HaoyangLee
approved these changes
May 3, 2023
4 tasks
colawyee
pushed a commit
that referenced
this pull request
Jan 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
针对之前文档中模糊不清的部分，细化了一些介绍：
[419更新]
[420更新]
文档在有一些冗余的部分，根据个人理解有一些删减，请review，thanks!
Thank you for your contribution to the MindOCR repo.
Before submitting this PR, please make sure:
Motivation
(Write your motivation for proposed changes here.)
Test Plan
(How should this PR be tested? Do you require special setup to run the test or repro the fixed bug?)
Related Issues and PRs
(Is this PR part of a group of changes? Link the other relevant PRs and Issues here. Use https://help.github.com/en/articles/closing-issues-using-keywords for help on GitHub syntax)