MegEngine / MegEngine/PMRID

confuse with raw data load

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

Nobody has claimed this yet.

Dominant language
Python
Stars
275
Forks
46
PR merge metrics
No merged PRs in 30d

Description

oppo data has 24bit for per channel:
![image](https://github.com/MegEngine/PMRID/assets/36892165/93c47241-3ab5-480d-af6c-14850654ad90)

why load raw dng with np.uint16 format?

```python
def read_array(path: Path) -> np.ndarray:
return np.fromfile(str(path), dtype=np.uint16)
```

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.

Research direction

Locate the read_array(path: Path) entry point and inspect how raw DNG data is loaded with np.uint16. Compare that behavior with the issue's 24-bit-per-channel Oppo data and determine the expected loading format; done when the format choice is clarified or corrected and covered by an appropriate validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
computer-vision, data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.