Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thorough benchmarks [$200] #64

Open
Krastanov opened this issue Jul 9, 2024 · 2 comments
Open

Thorough benchmarks [$200] #64

Krastanov opened this issue Jul 9, 2024 · 2 comments
Labels
bounty:200 bug bounty There is an award for solving this issue good first issue Good for newcomers

Comments

@Krastanov
Copy link
Member

Krastanov commented Jul 9, 2024

Bug bounty logistic details (click to expand)

To claim exclusive time to work on this bounty either post a comment here or message [email protected] with:

  • your name
  • github username
  • (optional) a brief list of previous pertinent projects you have engaged in

Currently the project is claimed by no one until ....

If you want to, you can work on this project without making a claim, however claims are encouraged to give you and other contributors peace of mind. Whoever has made a claim takes precedence when solutions are considered.

You can always propose your own funded project, if you would like to contribute something of value that is not yet covered by an official bounty.

Project: "Thorough benchmarks" [$200]

We have a small benchmark suite already implemented for our other repositories, which is executed as part of our CI runs. It is defined in the benchmark folder and reported for each pull request. We would like to implement a similar benchmark suite here to include many facets of this library. E.g. basic symbolic operations, simplifications, rule application, flattening and expanding, expressing into numerical backends, time to import, etc. The new benchmarks should be legible, easy to follow, and organized by topic. Most of them should be microbenchmarks testing only one concept, but a few holistic benchmarks would make sense as well.

Required skills: Generic Julia skills.

Reviewer: Stefan Krastanov

Duration: 1 month

Payout procedure:

The Funding for these bounties comes from the National Science Foundation and from the NSF Center for Quantum Networks. The payouts are managed by the NumFOCUS foundation and processed in bulk once every two months. If you live in a country in which NumFOCUS can make payments, you can participate in this bounty program.

Click here for more details about the bug bounty program.

@Krastanov Krastanov added bug bounty There is an award for solving this issue bounty:200 good first issue Good for newcomers labels Jul 9, 2024
@coderight1
Copy link

Hi @Krastanov , I would like to work on this .

@Krastanov
Copy link
Member Author

Hi, @coderight1 . Apologies for the slow response, I did not see this message originally. Do you have past experience experience with Julia? Could you list out a rough plan for what you are going to do?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:200 bug bounty There is an award for solving this issue good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants