UCL / UCL/STIR

Some CTests require installation to pass

Open
#1,069 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

This is mostly for documenting the issue. I am running from Clion and a number of CTests (including test_data_processor_projectors) are failing because I haven't installed STIR, just built it. The issue relates to ${STIR_install_location}/share/stir/config/radionuclide_info.json not existing.

The obvious solution is to install STIR once.

Example output:

7: Test command: /Users/rts/devel/STIR/devel1/release_build/src/recon_test/test_data_processor_projectors "/Users/rts/devel/STIR/devel1/STIR/recon_test_pack/Utahscat600k_ca_seg4.hs"
7: Working Directory: /Users/rts/devel/STIR/devel1/release_build/src/recon_test
7: Test timeout computed to be: 10000000
7: 
7: ERROR: find_STIR_config_file could not open /Users/rts/devel/STIR/devel1/release_install/share/stir/config/radionuclide_info.json
7: 
7: End of tests. Please correct errors !
7: 
7: 
Failed

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 running the CTest named test_data_processor_projectors from the build tree in CLion and inspect the reported path under share/stir/config/radionuclide_info.json. Compare behavior before and after installing STIR; done should be defined as the affected CTests passing without the reported missing configuration file.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.