Persist circuits in batch execute

[WingCode]

Issue #, if available: closes #255

Description of changes: Add persistence of multiple circuits when batch_execute is called

Testing done:

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

• I have read the CONTRIBUTING doc
• I used the commit message format described in CONTRIBUTING
• I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (7cfecb8) to head (70adc56).
Report is 1 commits behind head on feature/persist-batch-circuits.

Additional details and impacted files

@@                       Coverage Diff                        @@
##           feature/persist-batch-circuits      #260   +/-   ##
================================================================
  Coverage                          100.00%   100.00%           
================================================================
  Files                                   7         7           
  Lines                                1211      1225   +14     
  Branches                              295       297    +2     
================================================================
+ Hits                                 1211      1225   +14     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[AbeCoull]

Hi @WingCode and thanks for raising this! It seems the linter check is failing. Locally, you can run tox -e linters to fix this.

[WingCode]

@math411 I have fix the linting issues. Could you please review?

[yitchen-tim]

Hi @WingCode , thanks for contributing to the issue! This PR solves half of the problem stated in #255. Printing noisy circuits when using noise model is still not supported. However, after reviewing this PR, I think printing noisy circuits is not the right goal to pursue.

The right goal is to allow users to retrieve the tasks (and the task ids), from which noisy circuits can be retrieved. If you can extend this PR to include the following feature, we are good to go: "Persist the task when parallel=True", which requires

1. Add an attribute self._tasks=[]
2. Add a method for returning tasks

    @property
    def tasks(self) -> list[QuantumTask]:
        ...

, similar to

amazon-braket-pennylane-plugin-python/src/braket/pennylane_plugin/braket_device.py

Line 179 in a17e8b9

def task(self) -> QuantumTask:

3. Add unit tests for tasks

[yitchen-tim]

self._circuits here is a private variable. that users should not access. Instead, users access _circuits through properties. So, there need to be a new property of this class called circuits defined as a method of the class, similar to

amazon-braket-pennylane-plugin-python/src/braket/pennylane_plugin/braket_device.py

Line 174 in a17e8b9

def circuit(self) -> Circuit:

.

[yitchen-tim]

And yes, it's a bit repetitive now that we have both circuits and circuit, but I think it's okay for now. In long term, circuit may be deprecated.

[yitchen-tim]

Hi @WingCode, the PR looks good! I changed the target branch to be a feature branch instead of the main branch because Amazon Braket needs rework the duplication of circuit and circuits which requires some discussions. I will assign the issue to you and close the issue. This should be good in UnitaryHack regards. Thanks for contributing!

I somehow have trouble assigning the issue to you. I am asking my team to resolve it.

[WingCode]

Thank you @yitchen-tim for the reviews and all of the timely support!

[yitchen-tim]

@WingCode Could you leave a comment on the issue: #255? After that, I should be able to assign you.