Page MenuHomePhabricator

[Registration] MITKMatchPoint code should use PropertyRelationRules for its results
Closed, ResolvedPublic

Description

Currently the registration code (e.g. mapping, registration) and views currently uses own defined propertes (see mitkMatchPointPropertyTags.h) to identify relations (e.g. by Prop_MappingInputData and Prop_UID).

In the meantime we have PropertyRelations for such things. So the code base should be reworked.

  1. Introduce a RegistrationResultRelationRule and a MappingResultRelationRule based on SourceImageRelationRule.
  2. Rework the code base to use this new classes and deprecate the old definitions and helper functions.

As an example one can have a look on ModelFitResultRelationRule and its integration. ModelFit code base had the same issue like our registration code based and was also reworked.

Related Objects

StatusAssignedTask
Resolvedkislinsk

Event Timeline

floca triaged this task as Normal priority.Nov 30 2021, 5:57 PM
floca created this task.
floca added a parent task: Restricted Maniphest Task.May 4 2022, 9:12 AM
kislinsk set Deadline to May 5 2022, 12:00 AM.May 4 2022, 11:19 AM
kislinsk removed Deadline.
kislinsk added a project: Auto-closed.
kislinsk added a subscriber: kislinsk.

Hi there! ๐Ÿ™‚

This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. ๐Ÿš‘

Best wishes,
The MITK devs

floca edited projects, added Next Milestone; removed Auto-closed.
kislinsk claimed this task.
kislinsk added a project: Moved to git.dkfz.de.

This task was closed here on Phabricator since it was migrated to GitLab. Please continue on GitLab.