if STIR is built with openmp, steepest_ascent demo prints the objective function values as zeros
at the same time, optimization function scipy.optimize.fminbound seem to get correct objective function values: exactly the same values of the argument x and changes in the image after an iteration are computed as without openmp - but objective function values are reported to be 0!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
confirmed that this is still the case. This must be a STIR bug.
fixed on STIR master at UCL/STIR@cc7c164.
We therefore need to bump the default_STIR_TAG
in the superbuild
Closed #157.