Affected Releases: CESM1.2.1(Bugzilla 1727) CLUBB can now be run with OMP_NUM_THREADS > 1, but clubb_history is not working with thread > 1.cam5_3_05 will contain the fixes to allow CLUBB to run with OMP_NUM_THREADS
greater than 1. Results are BFB with jobs run with a single thread.
clubb_history is the one feature which is still not working with thread > 1.
With threads > 1, fields are having chunks being set to zero (saw this using an
ncdump on a field in the output files and diffing the text files). It appears
that stats_zero is being called before the values are being written. Various
attempts to correct this problem did not yield a solution.
CLUBB appears to work properly with threading except for the clubb_history
option.
greater than 1. Results are BFB with jobs run with a single thread.
clubb_history is the one feature which is still not working with thread > 1.
With threads > 1, fields are having chunks being set to zero (saw this using an
ncdump on a field in the output files and diffing the text files). It appears
that stats_zero is being called before the values are being written. Various
attempts to correct this problem did not yield a solution.
CLUBB appears to work properly with threading except for the clubb_history
option.