-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NiftyPET version 2 #1292
NiftyPET version 2 #1292
Conversation
31d6e01
to
4dfb6c2
Compare
11ad9a4
to
1c3cba5
Compare
- use CUDA version - let CMake find NiftyPET
d1162a6
to
3bcc1e7
Compare
- change step condition - see where NiftyPET*cmake is - exclude CUDA tests from ctest
I've got the non-CUDA jobs to run again (phew) (minor correction to come). Turns out that github actions conditional steps are a bit fragile, or I misunderstand the doc, anyway. I still have a problem letting CMake find NiftyPET (after installation from PyPy). I followed recommendations from export PATHTOOLS=${GITHUB_WORKSPACE}/NiftyPET_tools
export HMUDIR=${GITHUB_WORKSPACE}/mmr_hardwareumaps
python -m pip install "nipet>=2"
niftypet_cmake_prefix=$(python -c "from niftypet.nipet import cmake_prefix; print(cmake_prefix)")
ls -R "$niftypet_cmake_prefix"
echo NiftyPET_PREFIX="$niftypet_cmake_prefix" >> $GITHUB_ENV
which surprised me a bit as that doesn't seem to be the prefix, but the actual location of the config files. Using
CMake isn't happy:
so it seems we need to set |
forgot to mention @casperdcl in the above. |
- use NiftyPETnipet_DIR - fix condition in ctest
NiftyPET's Config.cmake needs CMake 3.3, but we announced in STIR 5.2 that we'd require 3.14 anyway.
a6c0369
to
6eaff48
Compare
setting Currently struggling with g++ not finding prbj.h |
6eaff48
to
71f01f6
Compare
I cannot find prbj.h: https://github.com/UCL/STIR/actions/runs/6992200721/job/19023543893#step:6:773
returns nothing https://github.com/UCL/STIR/actions/runs/6992200721/job/19023543893#step:9:978 shows that the include path set by CMake is likely correct
NiftyPET installation bug? |
@casperdcl @pjmark I created NiftyPET/NIPET#51. I suppose this might still work with a self-installed NIPET, but I have run out of steam. |
some members were removed from Cnts
As NiftyPET 2 is not compatible with C++, I will essentially abandon this PR, only keeping the CI cuda stuff |
the core of NIPET is written in C, so should be easy to add it to C++, no? |
The problem is that all the set-up is in Python (where it used to be in C). See NiftyPET/NIPET#52 for more information. |
Non-NiftyPET commits are now in #1300. I'm abandoning the rest. |
upgraded to version 2.
Also added CUDA and NiftyPET to GitHub Actions.
@gschramm @casperdcl @pjmark please check