ProjectorPairByBin does not parse data processors

Open
#505 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
computer-vision

Research direction

Start by locating ProjectorPairByBin and compare how the forward and back projectors expose their pre- and post-data processors. Trace how those processors are passed through the projector pair and determine the corresponding image-space and projdata-space names. Done means users can provide both processor types through ProjectorPairByBin with consistent naming.

Written by the indexing model from the issue text.

Description

As far as I can see, ProjectorPairByBin does not allow the user to give data processors.

In the forward and back projectors, these are called pre- and post-data processors, respectively. I propose we call them image data processors (implying that they are applied in image space, which is pre-forward- and post-back-projection) and projdata data processors, or something similar. In that way, we can have the same name of the variables in both projectors as well as the projector pair.

Dominant language
C++
Stars
160
Forks
113
Avg merge
12d 15h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

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 UCL/STIR

All issues in UCL/STIR

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.