Skip to content
This repository was archived by the owner on Jan 12, 2024. It is now read-only.

Conversation

@swernli
Copy link
Collaborator

@swernli swernli commented Aug 12, 2020

No description provided.

bamarsha and others added 18 commits July 6, 2020 10:56
* Use a default target when submitting to Azure Quantum

* Update doc comments

* Move settings.Target null check to switch case

Co-authored-by: bettinaheim <34236215+bettinaheim@users.noreply.github.com>
* Implemented friendly uri option in azure quantum.

* Fixed tests.

* Fixed tests after nerge conflict.

Co-authored-by: bettinaheim <34236215+bettinaheim@users.noreply.github.com>
Added execution test projects for various simulators.
Added tests to check measurements on qubits work.
Added tests for conditions on measurement results.
* Extends #257 (fixing #256) to QuantumProcessorDispatcher sim as well

* Pulled SampleDistribution method out to shared utils

Co-authored-by: Yury Sudzilouski <v-yusudz@microsoft.com>
Changed the isGeneric method of the C# generation code to count the length of the type parameter list for a callable.
…Get packages. (#311)

This change includes the following:

- NuGet version is updated to 5.6 and the .Net Core SDK to 3.1.300.

- The deprecated NuGet property IconUrl is replaced by an embedded icon in the packages themselves.

- The asset used as an icon for the packages is a newly created graphic.
* Handle operations as arguments in GetNonQubitArgumentsAsString

* Handle null values for IApplyData types
* EncourageReuse option in QubitManager.
Currently Qubit Manager tries to reuse released qubits as soon as possible and prefers it to allocating fresh unused ones. This is good for some scenarios, however, in other scenarios it may be preferrable to first allocate fresh unused qubits, and only then try to reuse released ones (oldest released first). Both behaviors are now possible via a backwards-compatible optional parameter in QubitManager constructor.

* Review feedback

* .
@swernli swernli closed this Aug 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants