Inconsistency between ITKImageProcessing vector images and DREAM3D vector images

Open
#141 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp

Research direction

Start by comparing the ITKImageProcessing and DREAM3D representations in the issue: RGB(A) and vector image component dimensions are encoded differently. Clarify whether the intended fix is consistent encoding or a filter-level user checkbox, then verify that RGB(A) and vector images remain distinguishable in the Dream3D data container.

Written by the indexing model from the issue text.

Description

ITKImageProcessing encodes RGB(A) and vector images in Dream3D data container differently whereas DREAM3D encodes them the same way.

In DREAM3D,
RGB(A) and vector images: QVector<size_t> cDims(1, nb_components);

In ITKImageProcessing:
Vector images components: QVector<size_t> cDims(nb_components, 1);
RGB images: QVector<size_t> cDims(1, 3);

ITKImageProcessing uses this implementation difference to differentiate between RGB(A) images and vector images. A solution for ITKImageProcessing to differentiate between RGB(A) and vector images could be with additional input from the user (check box). This additional input would be selected at the filter level.

Dominant language
C++
Stars
4
Forks
12
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BlueQuartzSoftware/ITKImageProcessing

All issues in BlueQuartzSoftware/ITKImageProcessing

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.