Go to file
Matthew Treinish 6192bfd529
Fix return type from schedule() with a list of one entry (#7885)
This commit fixes the return type when calling schedule() with a list of
a single entry. Previously this would return a single Schedule object
instead of the expected list return. A similar issue was already fixed
in transpile() in #5298 but schedule still had the incorrect behavior.

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2022-04-04 23:46:02 +00:00
.binder Add rust to binder configuration (#7732) 2022-03-04 02:32:17 +00:00
.cargo Implement multithreaded stochastic swap in rust (#7658) 2022-02-28 21:49:54 +00:00
.github Add CODEOWNERS for the primitives submodule (#7810) 2022-03-23 20:09:38 +00:00
docs Bump version strings post release (#7852) 2022-03-31 23:21:46 +00:00
examples Implement multithreaded stochastic swap in rust (#7658) 2022-02-28 21:49:54 +00:00
qiskit Fix return type from schedule() with a list of one entry (#7885) 2022-04-04 23:46:02 +00:00
releasenotes Fix return type from schedule() with a list of one entry (#7885) 2022-04-04 23:46:02 +00:00
src dict-based `SparsePauliOp.simplify` (#7656) 2022-03-17 18:09:00 +00:00
test Fix return type from schedule() with a list of one entry (#7885) 2022-04-04 23:46:02 +00:00
tools Implement multithreaded stochastic swap in rust (#7658) 2022-02-28 21:49:54 +00:00
.editorconfig Add .editorconfig (#6033) 2022-01-31 20:12:23 +00:00
.git-blame-ignore-revs Update git blame rev ignore list (#7620) 2022-02-03 21:31:01 +00:00
.gitignore Support reproducible builds of Rust library (#7728) 2022-03-03 17:47:13 +00:00
.local-spellings speeling fixes (#5858) 2021-02-19 00:54:19 +00:00
.mailmap Update garrison's name in .mailmap (#7443) 2021-12-23 15:06:18 +00:00
.mergify.yml Bump version strings post release (#7852) 2022-03-31 23:21:46 +00:00
.pylintrc Implement multithreaded stochastic swap in rust (#7658) 2022-02-28 21:49:54 +00:00
.stestr.conf Removes stestr's grouping configuration. (#6399) 2021-05-12 19:06:06 +00:00
CODE_OF_CONDUCT.md Pointing all Qiskit projects to main CoC file moving forward. (#5412) 2020-11-18 13:24:17 -05:00
CONTRIBUTING.md Improve CONTRIBUTING.md (#7693) 2022-03-16 16:25:04 +00:00
Cargo.lock Bump indexmap from 1.8.0 to 1.8.1 (#7841) 2022-03-30 18:33:01 +00:00
Cargo.toml Bump indexmap from 1.8.0 to 1.8.1 (#7841) 2022-03-30 18:33:01 +00:00
LICENSE.txt Consistent license across all the project (#550) 2018-06-08 15:00:58 +02:00
MANIFEST.in Support reproducible builds of Rust library (#7728) 2022-03-03 17:47:13 +00:00
Makefile Add incremental pylint make target (#6597) 2021-07-23 00:06:55 +00:00
README.md Update README.md: `pip install qiskit` no longer installs all elements (#7476) 2022-01-28 22:50:48 +00:00
azure-pipelines.yml Prepare 0.20.0 release (#7828) 2022-03-31 20:22:20 +00:00
constraints.txt Pin jinja2 in CI (#7815) 2022-03-24 21:08:46 +00:00
pyproject.toml Remove Cython as a build dependency (#7777) 2022-03-14 22:18:57 +00:00
requirements-dev.txt Remove Cython as a build dependency (#7777) 2022-03-14 22:18:57 +00:00
requirements.txt Bump minimum supported symengine version for built-in pickle support (#7682) 2022-02-21 17:47:46 +00:00
setup.py Bump version strings post release (#7852) 2022-03-31 23:21:46 +00:00
tox.ini Implement multithreaded stochastic swap in rust (#7658) 2022-02-28 21:49:54 +00:00

README.md

Qiskit Terra

LicenseBuild StatusReleaseDownloadsCoverage Status

Qiskit is an open-source framework for working with noisy quantum computers at the level of pulses, circuits, and algorithms.

Qiskit is made up of elements that work together to enable quantum computing. This element is Terra and is the foundation on which the rest of Qiskit is built.

Installation

We encourage installing Qiskit via the pip tool (a python package manager). The following command installs the core Qiskit components, including Terra.

pip install qiskit

Pip will handle all dependencies automatically and you will always install the latest (and well-tested) version.

To install from source, follow the instructions in the documentation.

Creating Your First Quantum Program in Qiskit Terra

Now that Qiskit is installed, it's time to begin working with Terra.

We are ready to try out a quantum circuit example, which is simulated locally using the Qiskit BasicAer element. This is a simple example that makes an entangled state.

$ python
>>> from qiskit import QuantumCircuit, transpile
>>> from qiskit.providers.basicaer import QasmSimulatorPy
>>> qc = QuantumCircuit(2, 2)
>>> qc.h(0)
>>> qc.cx(0, 1)
>>> qc.measure([0,1], [0,1])
>>> backend_sim = QasmSimulatorPy()
>>> transpiled_qc = transpile(qc, backend_sim)
>>> result = backend_sim.run(transpiled_qc).result()
>>> print(result.get_counts(qc))

In this case, the output will be:

{'00': 513, '11': 511}

A script is available here, where we also show how to run the same program on a real quantum computer via IBMQ.

Executing your code on a real quantum chip

You can also use Qiskit to execute your code on a real quantum chip. In order to do so, you need to configure Qiskit for using the credentials in your IBM Q account:

Configure your IBMQ credentials

  1. Create an IBM Q > Account if you haven't already done so.

  2. Get an API token from the IBM Q website under My Account > API Token and the URL for the account.

  3. Take your token and url from step 2, here called MY_API_TOKEN, MY_URL, and run:

    >>> from qiskit import IBMQ
    >>> IBMQ.save_account('MY_API_TOKEN', 'MY_URL')
    

After calling IBMQ.save_account(), your credentials will be stored on disk. Once they are stored, at any point in the future you can load and use them in your program simply via:

>>> from qiskit import IBMQ
>>> IBMQ.load_account()

Those who do not want to save their credentials to disk should use instead:

>>> from qiskit import IBMQ
>>> IBMQ.enable_account('MY_API_TOKEN')

and the token will only be active for the session. For examples using Terra with real devices we have provided a set of examples in examples/python and we suggest starting with using_qiskit_terra_level_0.py and working up in the levels.

Contribution Guidelines

If you'd like to contribute to Qiskit Terra, please take a look at our contribution guidelines. This project adheres to Qiskit's code of conduct. By participating, you are expected to uphold this code.

We use GitHub issues for tracking requests and bugs. Please join the Qiskit Slack community and use our Qiskit Slack channel for discussion and simple questions. For questions that are more suited for a forum we use the Qiskit tag in the Stack Exchange.

Next Steps

Now you're set up and ready to check out some of the other examples from our Qiskit Tutorials repository.

Authors and Citation

Qiskit Terra is the work of many people who contribute to the project at different levels. If you use Qiskit, please cite as per the included BibTeX file.

Changelog and Release Notes

The changelog for a particular release is dynamically generated and gets written to the release page on Github for each release. For example, you can find the page for the 0.9.0 release here:

https://github.com/Qiskit/qiskit-terra/releases/tag/0.9.0

The changelog for the current release can be found in the releases tab: Releases The changelog provides a quick overview of notable changes for a given release.

Additionally, as part of each release detailed release notes are written to document in detail what has changed as part of a release. This includes any documentation on potential breaking changes on upgrade and new features. For example, You can find the release notes for the 0.9.0 release in the Qiskit documentation here:

https://qiskit.org/documentation/release_notes.html#terra-0-9

License

Apache License 2.0