-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* new pyLIQTR version * qchem script cleanup * cleaned up value_per_t_gate and added analytical use case for gsee * made change to allow unique file name when performing a sweep * responded to issue of improper gate synth accuracy. pyLIQTR handles it differently depending on the function? * allow trotter to use use_analytical * fix typo * Updated pylint badge * doing 1e-10 rther than string * accidentally scaling num_qubits * Updated pylint badge * adding exotic phases script and moving print statement for generating trotterized subprocess gsee to AFTER we create circuit * changed field from value_per_circuit to value. Additionally, cleaned up some code to make sure we getting right value per t gate * fixed capitalization on ars --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
- Loading branch information
1 parent
cc16f71
commit 8eacdd7
Showing
14 changed files
with
319 additions
and
109 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.