onnx-graphsurgeon inquery
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 13.4k
- Forks
- 2.4k
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 2
Description
Thanks for your great tool, I have been using onnx-graphsurgeon quite recently, it's very useful but really buggy, I have made some prs but very few are merged. So I developed a tool called onnxslim, which is very easy to use and reallly robust, I have maintained a private version of onnx-graphsurgeon and made an acknowledgement in the README, onnxslim is now open sourced, and I'm wondering if it's appropriate to do so, or do I have to make other citations or declarations. Thanks!
@pranavm-nvidia @rajeevsrao
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
Start with the README acknowledgement and the linked onnxslim repository, then read the issue’s question about reuse, citations, and declarations. Done means the maintainers provide a clear response or document the required attribution and declaration guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100