UCL / UCL/STIR

Incompatible projection data due to differences in bed position

Open
#293 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

When carrying out motion corrected reconstruction, previously, it appeared STIR ignored the bed position when reading projection data, but now throws up an error.

Carrying out the following command:

INPUT=sino_pmroverlap OUTPUT=recon_motion_MCIR_normalise NORM=normacfsino BACKGROUND=backgroundsino OSMAPOSL OSMAPOSL_with_motion.par

The normalisation files with the prefix normacfsino are created with vertical and horizontal bed positions at the origin (0,0). The sinogram projection data data with prefix sino_pmroverlap have different bed positions. Previous versions of STIR would successfully run this reconstruction, however, now states:

WARNING: BinNormalisationFromProjData: incompatible projection data

displays info as if ran list_projdata_info for both sinogram & norm

ERROR: Single gate objective functions is not set correctly!

Manually adjusting the bed positions to match does appear to fix the issue.

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.

Research direction

Start by reproducing the OSMAPOSL command with the provided projection, normalisation, background, and parameter files, then compare the sinogram and normalisation metadata using list_projdata_info. Investigate why differing bed positions trigger the incompatible projection-data warning and objective-function error; done means the reconstruction handles the reported inputs without manually changing bed positions, or the incompatibility is clearly confirmed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.