avoid buffer size overflow

[36000]

No description provided.

[Copilot]

Pull request overview

Adjusts how ArraySequence buffer sizing is computed/passed to prevent buffer sizing issues (unit mismatch/truncation) during streamline generation.

Changes:

• Change SeedBatchPropagator.get_buffer_size() to return a megabyte-based (ceil’d) value.
• Update ArraySequence construction sites to pass the new buffer size value directly (no // MEGABYTE at call sites).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
cuslines/cuda_python/cu_tractography.py	Updates ArraySequence buffer size argument for SFT generation to use the new units returned by the propagator.
cuslines/cuda_python/cu_propagate_seeds.py	Changes buffer size calculation to return MB (rounded up) and updates ArraySequence creation accordingly.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

In generate_sft, the ArraySequence is built from generators that are created from SeedBatchPropagator state. Because SeedBatchPropagator.as_generator() reads from self.slines/self.sline_lens (which are overwritten on each propagate() call), collecting generators across multiple chunks and consuming them after the loop will yield the last chunk’s data repeatedly (earlier chunk results are lost). Consider materializing/copying each chunk’s results before the next propagate(), or restructure to yield streamlines immediately per chunk instead of storing generators.

[Copilot]

Since the conversion by MEGABYTE was removed here, MEGABYTE appears to be unused in this module now. Removing the unused import will avoid lint/static-analysis failures and keep the unit handling clear.