Skip to content

Releases: pasqal-io/Pulser-myQLM

Release v0.3.0

08 Oct 11:58
Compare
Choose a tag to compare

Main changes

  • Publish project to PyPi

Collaborators

Release v0.2.0

04 Oct 13:45
Compare
Choose a tag to compare

Main Changes

  • Implement FresnelQPU.get_specs to fetch the Device abstract representation associated with the last calibration of the QPU.
  • Implement system polling when querying the result of a Job from the QPU.
  • Relax condition on the Register of a Sequence submitted to FresnelQPU: a layout must be associated, but it no longer have to match one of the calibrated layouts.

Contributors

Release v0.1.6

24 Sep 11:09
Compare
Choose a tag to compare

Fix

Fixes the conversion of a Sequence into a Job for pulser-core>=v0.20.0.

Release v0.1.5

18 Sep 12:44
Compare
Choose a tag to compare

Bug Fixes

Adds an __init__.py file in the helpers folder to solve installation troubles.

Release v0.1.4

16 Sep 13:41
Compare
Choose a tag to compare

Additional documentation

  • Tutorial on solving a QUBO with pulser-myqlm
  • Tutorial on preparing an Antiferromagnetic State with pulser-myqlm
  • Script to deploy a MyQLM server either connected to a QPU on a given IP address and port, or mocking the QPU's behaviour by running pulser-simulation locally.

Refactoring

  • Splitting PulserAQPU.py into IsingAQPU.py and FresnelQPU.py.
  • Placing constants and helper functions in an external directory.
  • Splitting of the tests, isolation of the tests on FresnelQPU/IsingAQPU.

Bug Fixes

  • Adding requests to requirements.txt: this package is mandatory for the execution of FresnelQPU

Contributors

Thanks to all the contributors !

Releave v0.1.3

24 Jul 09:53
Compare
Choose a tag to compare

Bugfixes

Standardize conventions of Pulser and MyQLM:

  • The initial state in pulser-simulation is the ground state |g>. The excited state is the Rydberg state |r>.
  • In the Hamiltonian used in pulser-simulation (and used in pulser-myqlm < v0.1.3), |g> is associated to vector (0, 1)=|1> in myqlm. To perform correct simulations, users of pulser-myqlm < v0.1.3 have to define the initial state of the Job as |11...1> (each qubit is in state |1>=|g>) since otherwise the initial state is |00...0> (each qubit is in state |0>=|r>). That was the source of errors when simulating notebook such as MIS, where initial state matters (MIS Sequence on |rr..r> does not change the state of the system). Even with the correct initial state, users had to have in mind that in the provided results from a simulation with AnalogQPU, |0><->|r> and |1><->|g> which is counter-intuitive and does not match the way results of pulser-simulation are converted into myqlm Results.
  • Therefore, an alternative definition of the Pulser Hamiltonian is used in the Sequence-to-Job conversion, such that |g> is now associated with vector (1, 0)=|0> in myqlm, and |r> = (0, 1) = |1> in MyQLM. The convention is now stable throughout the package and output of MIS simulations are the same with pulser-simulation and myqlm emulators.

Release v0.1.2

15 Jul 13:43
Compare
Choose a tag to compare

Bug Fixes:

  • Transfer of error messages from server to RemoteQPU by defining error codes.
  • Add a regression test file (includes test of submission to AnalogQPU).
  • Installation of dev requirements/pytest with python3 setup.py install easy_install "pulser-myqlm[dev]"/python3 setup.py install easy_install "pulser-myqlm[test_dev]".
  • Possibility to define kwargs arguments to serve method (accounts for release of myqlm > 1.9.9).

Release v0.1.1

15 Jul 13:42
Compare
Choose a tag to compare

Bug Fixes:

  • Display of MyQLM Sample.state in MyQLM Result objects obtained from IsingAQPU.convert_samples_to_result.
  • Simulation of MyQLM Job made from IsingAQPU.convert_sequence_to_job using MyQLM AnalogQPU.

Release v0.1.0

15 Jul 13:40
Compare
Choose a tag to compare

Main changes

  • Creation of IsingAQPU to convert a Sequence into a Schedule or Job, and submit the job to either pulser-simulation or a MyQLM QPU.
  • Creation of FresnelQPU to connect to Pasqal QPUs using the base URI of the API and submit myQLM Jobs to it.
  • Creation of tests, test of the integration on the QLM.