Consider configurable injection bandwidth

[Cesartwothousands]

Context

INJECTION_BANDWIDTH is currently fixed at 2, likely reflecting the two routing planes supported by the current injection geometry. This can serialize circuits with more than two injections in the same channel.

Possible direction

• Add an --injection-bandwidth option, keeping 2 as the default.
• Propagate it through floorplanning, Program IR validation, and layout generation.
• Allocate collision-free routing resources for each slot, rather than only increasing the grouping limit.
• Add overlap checks and tests for 1-D and die-constrained layouts.

A scheduling-only change may create overlapping geometry because slots above 1 currently share a routing plane.

Are there other constraints this change should account for? Comments and implementation-roadmap suggestions are welcome.

[Nozidoali]

Thanks for pointing this out. Do you have an example QASM circuit to share where this works? i tested on some t-heavy benchmarks, but their dependencies do not allow parallelization these injections