From 2eb7bf4cfa464f704be1f2f93cd056648b4853a4 Mon Sep 17 00:00:00 2001 From: Alexander Duda Date: Wed, 30 Nov 2022 11:37:35 +0100 Subject: [PATCH] core: improve doc for setNumThreads The old documentation implies that the call is only valid for the next parallel region and must be called again if addtional regions should be affected as well. --- modules/core/include/opencv2/core/utility.hpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/core/include/opencv2/core/utility.hpp b/modules/core/include/opencv2/core/utility.hpp index 108c0d93e7..5fc5a4eaac 100644 --- a/modules/core/include/opencv2/core/utility.hpp +++ b/modules/core/include/opencv2/core/utility.hpp @@ -179,7 +179,7 @@ CV_EXPORTS ErrorCallback redirectError( ErrorCallback errCallback, void* userdat CV_EXPORTS String tempfile( const char* suffix = 0); CV_EXPORTS void glob(String pattern, std::vector& result, bool recursive = false); -/** @brief OpenCV will try to set the number of threads for the next parallel region. +/** @brief OpenCV will try to set the number of threads for subsequent parallel regions. If threads == 0, OpenCV will disable threading optimizations and run all it's functions sequentially. Passing threads \< 0 will reset threads number to system default. This function must