ROI persistance mechanism
Open
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
About http://trac.imagej.net/ticket/536. I wonder to know wether you choose a strategy to store ROIs ?
Even if it could be important to have an independant mechanism (independant from image file), it would be very nice to be able to store ROIs in OME XML.
Contributor guide
No contributing guide indexed for this repository
Research direction
Begin with the linked Trac ticket 536 and review the issue's two proposed directions: an independent ROI mechanism or storage in OME XML. Done requires an agreed persistence strategy and a defined implementation scope; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-vision
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100