KitwareMedical / KitwareMedical/SlicerIMSTK
Handling force feedback from iMSTK in Slicer
Open
- Dominant language
- CMake
- Stars
- 9
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue has no body, so it names no files, tests, or entry points to start from. First clarify the expected force-feedback behavior and how iMSTK should integrate with the SlicerIMSTK extension; done criteria must be agreed with maintainers before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100