giga floating-point operations "per sec"
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.9k
- Forks
- 7.3k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 13
Description
📚 The doc issue
Operations "per sec(ond)" should not be used here since there is no definitive input speed (fps),
https://github.com/pytorch/vision/blob/main/docs/source/conf.py#L367
https://github.com/pytorch/vision/blob/main/docs/source/conf.py#L369
Suggest a potential alternative/fix
Should be operations (OPs) but not operations per second (OPS)
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
Open docs/source/conf.py and inspect the references at lines 367 and 369. Update the terminology from operations per second (OPS) to operations (OPs), then verify that both documentation references no longer use the disputed wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100