Qiskit / Qiskit/sbd-eigensolver-python
Two issues with mpi communicator configuration
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 8h 45m
- Merged PRs (30d)
- 23
Description
From #21:
Two related issues found while investigating, not addressed here:
- h_comm_size is writable on both config objects, but tpb::diag / gdb::diag
recompute it from mpi_size, so setting it has no effect.- gdb_diag's docstring says b_comm_size must be 1, which is enforced nowhere and
unexplained. If true it deserves a reason; if stale it blocks the one dimension that
would parallelise the determinant list.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the two configuration objects into tpb::diag and gdb::diag, starting with how mpi_size and h_comm_size are handled. Read the gdb_diag docstring and inspect how b_comm_size is used or validated. Done means the writable settings and documentation agree with the implemented communicator behavior, with tests or checks covering the two reported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100