Closed ledigchr closed 3 years ago
Some experiments around that seem to confirm what is also discussed in this thread by the N4 developers.
ITK_GLOBAL_DEFAULT_NUMBER_OF_THREADS
. So if this is set explicitly, N4 should be reproducible across systems with varying number of CPUs. m5a.8xlarge
(32 CPUs) on a t2.xlarge
(4 CPUs, but with ITK_GLOBAL_DEFAULT_NUMBER_OF_THREADS=32
). My suggested fix for the MALPEM package is to update malpem-proot
and explicitly set ITK_GLOBAL_DEFAULT_NUMBER_OF_THREADS
. E.g.
'XAUTHORITY=/tmp/.mdmCHXAXX' \
"${PROOT}" \
-->
'XAUTHORITY=/tmp/.mdmCHXAXX' \
'ITK_GLOBAL_DEFAULT_NUMBER_OF_THREADS=32' \
"${PROOT}" \
Fixed in malpem-v1.3 by setting 'ITK_GLOBAL_DEFAULT_NUMBER_OF_THREADS=8'
in malpem-proot
This is an important issue reported with suggested fix here: https://github.com/MIRTK/MALPEM/issues/2