Adding a pixel size in OMERO metadata
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
@berombau suggested to be sure to add, when it's available, the units to pixel size value in the OMERO metadata.
This number is redundant as it can be computed from the coordinate transformations, but he said that it would be handy for tools to have a copy of this value readily available from disk, without having to derive it by looking at the eigenvalues of the affine transformation.
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 by locating the OMERO metadata handling and the representation of coordinate transformations in the repository. Determine how pixel size and its units should be represented when available, then verify that the value is written to disk and can be read by tools without deriving it from the affine transformation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100