Two issues with mpi communicator configuration

Open
#22 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
64/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python

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.

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.
Dominant language
Python
Stars
2
Forks
0
Avg merge
8h 45m
Merged PRs (30d)
23

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Qiskit/sbd-eigensolver-python

All issues in Qiskit/sbd-eigensolver-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.