DeChat uses all CPU threads despite -t 16

[kuanchiun]

Dear developer,

Thank you very much for providing this wonderful tool. I currently have ~45× Nanopore R10.4.1 simplex data (N50 ≈ 54 kb) and would like to use DeChat to correct reads prior to assembly.

I ran the following command and limited the threads to 16:

dechat -i ../herro_corrected/preprocessed.fastq.gz -o dechat_corrected -t 16

However, I noticed that the process still utilized all CPU threads (256) on our server (screenshot attached).
Is my command incorrect, or is there a recommended way to restrict the number of threads?

DeChat verison: 1.0.1 installed from conda

Best Regards,
Kuan Chiun

[janoppelt]

I have the same issue with DeChat. I tested both the 1.0.0 and 1.0.1 versions and built from source. DeChat uses all available cores even with the default settings (=not using -t at all).

[qiyuanhuakai]

@kuanchiun @janoppelt
我这边也遇到了同样的问题。我提交了一个修复 -t 选项被忽略的 PR（#13）：
如果方便的话，能否在你们的环境里也测试一下，并确认现在是否会遵循 -t N？
我这边测试是正常的，但希望能得到验证。
I’m seeing the same issue. I submitted a fix for the -t option being ignored (PR #13):
If you have a chance to test it on your setup, could you confirm whether -t N is now respected?
It seems to work on my machine, but I’d appreciate confirmation on yours.