Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix missing import | Willem Jan Palenstijn | 2020-07-04 | 1 | -0/+2 |
| | | | | Thanks to @jleuschn for catching this. | ||||
* | Merge branch 'direct_fpbp' | Willem Jan Palenstijn | 2020-07-02 | 8 | -48/+159 |
|\ | |||||
| * | Add error check | Willem Jan Palenstijn | 2020-07-02 | 1 | -0/+4 |
| | | |||||
| * | Add mode parameter to direct_FPBP3D | Allard Hendriksen | 2020-07-02 | 1 | -6/+5 |
| | | | | | | | | This change allows additive forward and backprojections. | ||||
| * | Check numpy array type | Willem Jan Palenstijn | 2020-07-02 | 5 | -16/+25 |
| | | |||||
| * | Add python astra.experimental.direct_FP3D/BP3D | Willem Jan Palenstijn | 2020-07-02 | 1 | -0/+54 |
| | | |||||
| * | Refactor cython data3d object creation to prepare | Willem Jan Palenstijn | 2020-07-02 | 4 | -37/+82 |
|/ | |||||
* | Use numpy backward binary compatibility for conda packages | Willem Jan Palenstijn | 2020-02-07 | 8 | -46/+8 |
| | | | | | | | | We now only build a single package built with numpy 1.11.x for numpy>=1.11,<2 . There is no guarantee that every future numpy version covered by this will be compatible with numpy 1.11, but numpy checks this internally at run-time, and should report this (noisily) when this occurs. | ||||
* | Fix potential geometry constant corruption in par3d_bp | Willem Jan Palenstijn | 2020-02-05 | 1 | -1/+1 |
| | |||||
* | Fix memory leaks in 3D BP | Willem Jan Palenstijn | 2020-02-05 | 2 | -0/+6 |
| | |||||
* | Update python/numpy/cuda versions for conda | Willem Jan Palenstijn | 2020-01-14 | 8 | -10/+19 |
| | |||||
* | Increment version to 1.9.9dev | Willem Jan Palenstijn | 2019-09-27 | 6 | -8/+8 |
| | |||||
* | Merge branch 'consistent_scaling' | Willem Jan Palenstijn | 2019-09-27 | 48 | -2532/+841 |
|\ | |||||
| * | Skip boost/cuda check if cuda is not found | Willem Jan Palenstijn | 2019-09-25 | 1 | -0/+2 |
| | | |||||
| * | Add note | Willem Jan Palenstijn | 2019-09-25 | 1 | -0/+3 |
| | | |||||
| * | Fix crash in FBP_CUDA when called without projector | Willem Jan Palenstijn | 2019-09-25 | 1 | -1/+1 |
| | | |||||
| * | Remove unmaintained, out of date 'STANDALONE' cuda code | Willem Jan Palenstijn | 2019-09-25 | 15 | -1822/+0 |
| | | |||||
| * | Add unit tests for 3D adjoints | Willem Jan Palenstijn | 2019-09-25 | 1 | -5/+76 |
| | | |||||
| * | Adjust par3d adjoint scaling, and clean up | Willem Jan Palenstijn | 2019-09-25 | 3 | -88/+96 |
| | | |||||
| * | Enable all 2D projector tests | Willem Jan Palenstijn | 2019-09-25 | 2 | -5/+8 |
| | | |||||
| * | Add 3D reconstruction scaling test | Willem Jan Palenstijn | 2019-09-25 | 1 | -18/+78 |
| | | |||||
| * | Fix part of non-cube cone scaling | Willem Jan Palenstijn | 2019-09-25 | 2 | -2/+5 |
| | | |||||
| * | Small clean up of factors | Willem Jan Palenstijn | 2019-09-25 | 4 | -14/+12 |
| | | |||||
| * | Remove C++ projector tests | Willem Jan Palenstijn | 2019-09-25 | 3 | -254/+0 |
| | | | | | | | | These have been superseded by python versions. | ||||
| * | Add missing header | Willem Jan Palenstijn | 2019-09-25 | 1 | -1/+1 |
| | | |||||
| * | Add feature flags for changed scaling behaviour | Willem Jan Palenstijn | 2019-09-25 | 2 | -2/+20 |
| | | |||||
| * | Remove obsolete DensityWeighting option | Willem Jan Palenstijn | 2019-09-25 | 4 | -15/+3 |
| | | |||||
| * | Improve adjoint matching for fan/cone BP functions, and clean up | Willem Jan Palenstijn | 2019-09-25 | 3 | -223/+251 |
| | | |||||
| * | Add test for reconstruction scaling | Willem Jan Palenstijn | 2019-09-25 | 1 | -0/+79 |
| | | |||||
| * | Fix fan-beam FBP scaling | Willem Jan Palenstijn | 2019-09-25 | 3 | -11/+15 |
| | | |||||
| * | Add error check for non-parallel FBP | Willem Jan Palenstijn | 2019-09-25 | 1 | -0/+5 |
| | | |||||
| * | Work around some warnings | Willem Jan Palenstijn | 2019-09-25 | 3 | -37/+34 |
| | | |||||
| * | Adjust SART to line integral scaling | Willem Jan Palenstijn | 2019-09-25 | 3 | -9/+10 |
| | | |||||
| * | Clean up outputscale naming confusion in cuda::algo | Willem Jan Palenstijn | 2019-09-25 | 5 | -20/+29 |
| | | |||||
| * | Adjust FBP to line integral scaling | Willem Jan Palenstijn | 2019-09-25 | 8 | -19/+31 |
| | | |||||
| * | Adjust adjoint to line integral scaling | Willem Jan Palenstijn | 2019-09-25 | 6 | -30/+132 |
| | | |||||
| * | Dynamically create python test functions | Willem Jan Palenstijn | 2019-09-25 | 1 | -34/+10 |
| | | |||||
| * | Check if boost and CUDA versions are compatible | Willem Jan Palenstijn | 2019-09-25 | 2 | -0/+23 |
| | | | | | | | | | | See https://github.com/astra-toolbox/astra-toolbox/issues/163 and https://github.com/boostorg/config/pull/175 . | ||||
| * | Adjust strip kernels to line integral scaling | Willem Jan Palenstijn | 2019-09-25 | 3 | -18/+26 |
| | | |||||
| * | Adjust distance driven kernels to line integral scaling | Willem Jan Palenstijn | 2019-09-25 | 2 | -7/+17 |
| | | |||||
| * | Adjust linear/cuda kernels to line integral scaling | Willem Jan Palenstijn | 2019-09-25 | 4 | -23/+12 |
| | | |||||
| * | Adjust line kernels to line integral scaling | Willem Jan Palenstijn | 2019-09-25 | 3 | -19/+7 |
|/ | |||||
* | Merge pull request #214 from ahendriksen/CI-use-conda-c-compiler-toolchain | Willem Jan Palenstijn | 2019-09-25 | 9 | -29/+52 |
|\ | | | | | Use conda compiler toolchain for conda builds | ||||
| * | Use conda compiler toolchain for conda builds | Allard Hendriksen | 2019-09-20 | 9 | -29/+52 |
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For both libastra and astra-toolbox: 1) We do not use script_env to set CC/CXX anymore, since the compilers are installed by conda. 2) The build string is made useful by including either the python+numpy version or the cudatoolkit version that the package was built with. 3) Some clean-up of build.sh in buildenv/ For libastra: 1) The libastra.so is built with the conda C/C++ compiler toolchain. This has two benefits: 1) The rpath of libastra.so is set to $ORIGIN, which makes linking easier for dependent packages. 2) libastra.so is linkable against ancient versions of glibc. With old versions of memcpy. 2) The C/C++ compiler version is fixed to 5.4.0 3) In libastra/build.sh, we rename $CONDA_PREFIX to $PREFIX. Apparently, this is how it is supposed to be done. For me, $CONDA_PREFIX was suddenly undefined. Why this was not a problem before, is unclear to me. 4) The cudatoolkit runtime dependency is pinned with pin_compatible 5) The libastra conda package now provides headers and .pc file. This is useful for building C++ packages that depend on astra. 6) Remove some old code related to cudatoolkit<8.0. For astra-toolbox: 1) astra-toolbox uses the conda-provided compilers 2) The compilers are fixed to version 7.3 3) Add boost to host requirements of astra-toolbox Notes on testing: - The libastra build has been tested with all versions of cudatoolkit - The astra-toolbox build has been tested with all provided versions of python after building a single cudatoolkit version of libastra. How to test this branch: - It should work by just editing `python/conda/linux_release/buildenv/build.sh`. Set BRANCH=CI-use-conda-c-compiler-toolchain URL=https://github.com/ahendriksen/astra-toolbox and run release.sh from the `python/conda/linux_release` directory. | ||||
* | Fix Travis CUDA setup | Willem Jan Palenstijn | 2019-09-18 | 1 | -2/+0 |
| | |||||
* | Fix clang build | Willem Jan Palenstijn | 2019-09-17 | 1 | -1/+3 |
| | |||||
* | Merge pull request #213 from ahendriksen/CI-update-conda | Willem Jan Palenstijn | 2019-09-17 | 1 | -1/+8 |
|\ | | | | | Use recent version of conda during linux conda-build | ||||
| * | Use recent version of conda during linux conda-build | Allard Hendriksen | 2019-09-17 | 1 | -1/+8 |
|/ | | | | | | This fixes the issue where cudatoolkit=8.0 would not install any more with recent versions of conda. Also, no corruption appears to take place while downloading packages. | ||||
* | Improve logging of mex detection to config.log | Willem Jan Palenstijn | 2019-08-16 | 1 | -2/+2 |
| | |||||
* | Check for the mex -R2017b option in configure | Willem Jan Palenstijn | 2019-08-16 | 3 | -4/+37 |
| | | | | | | | | | Since we use mex for linking, but CXX for compiling, we also need to set a preprocessor macro to emulate the -R2017b option. Currently we use -DMATLAB_MEXCMD_RELEASE=700, but it is unclear if this is the recommended way. This is required to build with Matlab R2018a and newer. |