From c1ebc2883a2fcf49bbe0d583ddd36910e1ef99ad Mon Sep 17 00:00:00 2001 From: Filip Leonarski Date: Tue, 25 Aug 2026 07:30:23 +0200 Subject: [PATCH] rugnux docs: give -N the rule the program actually follows Three stages take fewer workers than -N asks for, and only one of them was described. The per-image cap is lifted by a positive -N; the first-pass spot finding and beam-stop pre-scan ceilings are not, so -N 32 does not give 32 workers there. A value <= 0 counts as automatic and is capped like the default, which the previous "an explicit value is used as given" contradicted. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01Y5XisyYxmF8mUEQjzpMRe2 --- docs/RUGNUX.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/RUGNUX.md b/docs/RUGNUX.md index c15b6e3e..86fa063c 100644 --- a/docs/RUGNUX.md +++ b/docs/RUGNUX.md @@ -408,7 +408,7 @@ General: | Option | Description | | --- | --- | | `-o, --output-prefix ` | Output file prefix (default: `output`) | -| `-N, --threads ` | Number of worker threads (default: all hardware threads, with the per-image loop of `--mode mx` capped at 16 workers per GPU; an explicit value is used as given) | +| `-N, --threads ` | Number of worker threads (default, and for any value ≤ 0: all hardware threads). Some stages take fewer, because past a point more workers make them slower: the per-image loop of `--mode mx` uses at most 16 per GPU unless `-N` was given a positive value, and first-pass spot finding and the beam-stop pre-scan have ceilings of their own that `-N` does not lift. Scaling, merging and the space-group search use the full count | | `-s, --start-image ` | First image to process (default: 0) | | `-e, --end-image ` | Last image to process (default: all) | | `-t, --stride ` | Process every *n*-th image (default: 1) |