Improve the PathSimulator

Open
#185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
backend

Research direction

Start by reading issue #105 for the detailed PathSimulator work areas. Inspect the PathSimulator implementation and its existing tests, then trace how gate-cost lookup tables are handled. Done means addressing the gate-cost performance concern, moving lookup-table generation into the library, documenting its input format, and expanding test coverage.

Written by the indexing model from the issue text.

Description

documentation enhancement good first issue

The PathSimulator has some issues which are no deal breakers, but should be fixed before continueing to work on it.

  • The handling of the gate costs may lead to performance degradation.
  • Generating the lookup table for the gate costs should be part of library and the input format should be documented.
  • The tests do not actually test as much as they should.

More details on the parts to work on can be found in #105

Dominant language
C++
Stars
162
Forks
40
Avg merge
4h 49m
Merged PRs (30d)
40

Contributor guide

Open the contributing guide

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 munich-quantum-toolkit/ddsim

All issues in munich-quantum-toolkit/ddsim

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.