NumExpr safe limit for number of threads threads

[JB91451]

Dear all,

I run MS2PIP on a workstation which would has 24 cores and therefore set --num_cpu accordingly. however, when running the program, there is a warning that "NumExpr detected 24 cores but 'NUMEXPR_MAX_THREADS' not set, so enforcing safe limit of 8. NumExpr defaulting to 8 threads." I guess it is not possible to set NUMEXPR_MAX_THREADS directly during the ms2pip call? If so, would it be possible to couple this value with the --num_cpu option for a future release?

Best regards, Juergen

[RalfG]

Dear Juergen,

Apologies for the late reply. Thank you for reporting this issue!

NumExpr is a downstream dependency of DeepLC. In DeepLC itself, the environment variable NUMEXPR_MAX_THREADS is set as the configured number of cores. Expected behavior would be that MS²PIP passes its --num_cpu value on to DeepLC, which would then set NUMEXPR_MAX_THREADS. As this currently does not seem to be the case, we will look into it.

In the meantime, you can set the NUMEXPR_MAX_THREADS environment variable yourself when running MS²PIP:

• On Linux/macOS: NUMEXPR_MAX_THREADS=24 ms2pip <your ms2pip arguments>
• On Windows PowerShell: $env:NUMEXPR_MAX_THREADS= '24'; ms2pip <your ms2pip arguments>

Best, Ralf

[RalfG]

Fixed in #193