Add verify tests for common model components
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 333
- Forks
- 150
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 54
Description
- There are common neutral network architectures that we should test separately from an end-to-end model.
- Testing these architectures can make diagnosing future problems much easier since we would be able to independently verify that certain network features work correctly on a stand-alone basis.
- We already have verify tests for model features that we modify in some way in compiler passes.
- Here are some features that we should test (feel free to add more)
- Bert Transformer
- Long short term memory (LSTM)
- Encoder
- Decoder
- Autoencoders
- We can also take snippets of models and create verify tests for them.
- May want to take a look at ORT tests that also use snippets
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the existing verify tests for model features modified in compiler passes, then compare the ORT tests that use model snippets. Define a focused set of standalone tests for the listed architectures or snippets, with verification results that independently confirm each component works correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- machine-learning, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100