Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

When test img size is not 128, how to get a complete result,

Open
#12 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

The issue names no source file, test, or entry point; begin by locating NBNet's testing path and the code that clips images to 128-pixel patches and merges them. Reproduce the block artifacts on an image larger than 128 pixels, then document and verify a complete result without obvious seams.

Written by the indexing model from the issue text.

Description

Thank you for your work. NBNet requires size 128 as its input, but when testing img size > 128, if we clip the input to size 128 and then merge the patches, there will be obvious blocky phenomena. How do you solve them?

Dominant language
Python
Stars
156
Forks
22
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MegEngine/NBNet

All issues in MegEngine/NBNet

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.