4.26_large with SVP
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 131
- PR merge metrics
- No merged PRs in 30d
Description
Hi.
Sorry but v4.26_large is not good at all. I was going through a previously stable scene with no artefacts. But the whole scene was unstable before I even got to the part that normally has artefacts.
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
The report names v4.26_large and SVP but provides no file, test, or reproducible steps. Start by obtaining the scene, inputs, environment, and comparison with a stable version; done means reproducing the instability and documenting or correcting its cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100