BlueBrain / BlueBrain/atlas-annotation
Keep track of displacement fields along several registrations
- Dominant language
- Python
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
- It seems scientists are doing registrations in an iterative way
- It could be nice to keep track of the resulting displacement fields and be able to compose them together
- Analyze if still give realistic results (Jacobian Matrix ?)
- Analyze if the compose displacement field applied to the input image is giving consistent results
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the registration and displacement-field handling code, then determine how iterative fields could be stored and composed. Done would require a defined composition workflow plus evidence that Jacobian behavior and composed-field application produce consistent results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100