[jdotc1]

Keep narrow-band work regions consistent with worker counts and exclude empty workers from timestep resolution. Addresses #6823.

Scope and risk

Empty-band termination changes solver behavior and requires maintainer acceptance.

Validation

The PR merge revision 2981a2f075cc for head 5301fa889442 passed all 4,721 configured Linux ARM64 tests, including itkNarrowBandSmallBandTest. Pre-commit checks also passed for this head.

Prior recorded validation: 25 partition cases passed with GCC and address, undefined-behavior, and float-cast-overflow sanitizers.

The initialization review thread is resolved.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The changes affect narrow-band image filters and their parallel updates.

No behavioral defect was found, but the new test must follow the repository’s initialization rule before merging.

Findings

1.  Initialization breaks the guide ▶

Summary

The PR makes narrow-band partitions match the requested worker count and excludes empty workers from timestep selection.

• Narrow-band splits keep one region for each requested worker.
• Narrow-band filters stop cleanly when no band nodes remain.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Initialize or refresh band] --> B{Band empty?}
  B -->|Yes| G[Finish and post-process output]
  B -->|No| C[Give each worker a range]
  C --> D[Compute changes for nonempty ranges]
  D --> E[Choose timestep from valid workers]
  E --> F[Apply updates and count iteration]
  F --> A

Loading

_{Reviews (1) · Last reviewed commit: "STYLE: Align narrow band regression test..." · Reviewed by Greptile}