Backport tutorials into stable 0.23 branch (#1131)

* Fixed issue 1034 by correcting the typo

* Fixed issue 1065 by correcting the typo

* Add new line for list to be rendered properly

The two lists are not being rendered as lists so we add an extra newline for it to behave properly.

* Fix Aer tutorials (#1074)

* fixed setting of initial unitary

* fixed build noise model tutorial

* fixed tutorial applying noise to custom gate

* fixed extended stabilizer tutorial

* fixed the MPS tutorial

* Bopes tutorial fix (#1069)

* fix in bopes sampler tutorial

* kernel renaming for CI

Co-authored-by: Paul Nation <nonhermitian@gmail.com>

* fix qgans (#1071)

* fix qgans

* fix qgan code

* Pin docplex version in constraints.txt for CI job (#1082)

The recent new release of docplex has broken the released version of
aqua. There is a fix in aqua qiskit-community/qiskit-aqua#1420 which was released
in 0.8.1, but this hasn't been included in a metapackage release yet as
we're waiting for bugfix releases from all the other elements in the
next couple of days. Until that is included in a metapackage release we
won't be able to use the latest version of docplex in the CI job. This
commit adds a pin on the version of docplex used in a constraints file
to always use a known working version to unblock CI.

* Fix incorrect fidelity calculations in tomography tutorial (#1072)

* Fix tomography tutorial

* Remove noisy GST example

The old example can't use process fidelity function because it is comparing two noisy channels. My attempt to update using diamond norm distance instead cant be run in CI due to CVXPY solver not working without BLAS or CVXOPT.

* Remove header

Co-authored-by: Matthew Treinish <mtreinish@kortar.org>

* updated device noise model tutorial (#1080)

Co-authored-by: Paul Nation <nonhermitian@gmail.com>

* Add seed to quantum_instance (#1081)

Co-authored-by: Paul Nation <nonhermitian@gmail.com>

* Remove legacy tutorials (#1085)

* Combine advanced circuits and pulse (#1086)

* Combine advanced circuits and pulse

* remove pulse from toc

* fix numbering for proper globing

* All Qiskit projects point to main CoC (#1088)

* remove unused variables (#1089)

* Fixes minor typo in the electronic structure  chemsitry tutorial

* Bump cell timeout in sphinx config (#1091)

* Bump cell timeout in sphinx config

The 07_asian_barrier_spread_pricing tutorial is quite slow and often
times out in CI because running the simulation takes very close to 3
minutes in the fastest case. But, the performance of the CI nodes is
quite variable since they run on virtual machines in azure's public
cloud. So many jobs fail randomly because of timeouts on that notebook.
This commit attempts to fix this by bumping the timeout 60 seconds which
hopefully will give us enough slack time in the job to handle slow CI
nodes.

* Make cell timeout an env var

* Add missing int cast for QISKIT_CELL_TIMEOUT (#1092)

In #1091 we added a new env var to enable downstream CI to adjust the
per cell timeout to make things more reliable in variable performance
environments. But in that PR we neglected to cast the value of the env
var, which is always a string, to an int. This commit fixes that
oversight so the new env var is actually usable.

* Algorithm and machine learning tutorials (#1087)

* Add algorithm and ml tutorials for Aqua

* Number qgan and add advanced vqe

* Fix notebook link

* Change IBMQ to mock simulator

* Add folders to index.rst

* Fix warnings in grover notebook

Co-authored-by: Manoel Marques <manoel.marques@ibm.com>
Co-authored-by: Paul Nation <nonhermitian@gmail.com>

* Remove deprecated DAGCircuit method usage. (#1093)

* Fix typo (#1095)

### Summary
Fix issue #1095 

### Details and comments
Delete the wrong and meaningless part of the sentence ". which it has to do the same thing".

* Add external collaborator (#1094)

* Fixed some typos on 04_vqe_advanced.ipynb

* Delete 05_getting_started_with_pulse.ipynb

* Add files via upload

* Delete 05_getting_started_with_pulse.ipynb

* Add files via upload

* Delete 05_getting_started_with_pulse.ipynb

* Add files via upload

* Fixed a typo on 04_vqe_advanced.ipynb

* algorithms: fix typo on grover jupyter notebook

* Migrate pulse_lib to library (#1107)

* Fixed all the broken links in "05_getting_started_with_pulse.ipynb." (#1102)

* Delete 05_getting_started_with_pulse.ipynb

* Add files via upload

* Delete 05_getting_started_with_pulse.ipynb

* Add files via upload

* Delete 05_getting_started_with_pulse.ipynb

* Add files via upload

Co-authored-by: Paul Nation <nonhermitian@gmail.com>

* Delete 06_building_pulse_instructions.ipynb

* Add files via upload

* Delete 07_building_pulse_schedules.ipynb

* Add files via upload

* Delete 07_building_pulse_schedules.ipynb

* Add files via upload

* Delete 08_adding_measurements.ipynb

* Add files via upload

* Delete 09_gathering_system_information.ipynb

* Add files via upload

* Delete 01_algorithms_introduction.ipynb

* Fixed Some Broken Links in this tutorial

* Delete 03_vqe_simulation_with_noise.ipynb

* Fix some Old Links in this tutorials

* Delete 7_examples_vehicle_routing.ipynb

* Fixed some old links

* Fixed some old links

* Delete docs which are not as useful anymore

* Reindex and rename files

* Add new page about pulse gates

* Modify existing files

* Add note about openpulse being enabled for pulse gates

* Add note about scheduling

* Add Aqua operators tutorial (#1068)

* Add Aqua operators tutorial

* Make corrections and changes in PR review
	modified:   tutorials/operators/01_operator_flow.ipynb

* Add table of contents

* Remove duplicate H1 header

Co-authored-by: Paul Nation <nonhermitian@gmail.com>

* Deleting file uploading new one

* Uploaded the file with a added extra link.

* Corrected Link

* Run pulse gates on 0.16.2

* Execute on terra version 0.16.2

* Update 02_portfolio_diversification.ipynb

* Update 02_portfolio_diversification.ipynb

* Update 02_portfolio_diversification.ipynb

* Delete 08_fixed_income_pricing.ipynb

* Update file with a working link

* Delete 08_fixed_income_pricing.ipynb

* Add files via upload

* Delete 08_fixed_income_pricing.ipynb

* With Updated Qiskit version

* Delete 10_qgan_option_pricing.ipynb

* Updated Few Links

* Pin cvxpy in CI (#1127)

* Pin cvxpy in CI

The latest release of cvxpy is causing job failures because of how they
changed their numpy requirement. This commit unblocks CI by just capping
the version installed in CI to just exclude the latest version.

* Pin numpy too

* Add operators to docs structure (#1126)

Co-authored-by: Matthew Treinish <mtreinish@kortar.org>

* Remove numpy cap from tutorials job (#1139)

Co-authored-by: Tanya Garg <tanyagarg1701@gmail.com>
Co-authored-by: Peter J <peter.j@kakao.com>
Co-authored-by: Azeem Bande-Ali <A.BandeAli@gmail.com>
Co-authored-by: Yael Ben-Haim <yaelbh@il.ibm.com>
Co-authored-by: Panagiotis Barkoutsos <bpa@zurich.ibm.com>
Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
Co-authored-by: Christopher J. Wood <cjwood@us.ibm.com>
Co-authored-by: Manoel Marques <Manoel.Marques@ibm.com>
Co-authored-by: Maureen McElaney <mmcelaney@users.noreply.github.com>
Co-authored-by: ewinston <ewinston@us.ibm.com>
Co-authored-by: danchepkwony <dan.k.chepkwony@gmail.com>
Co-authored-by: Dan Chepkwony <67590846+danchepkwony@users.noreply.github.com>
Co-authored-by: Steve Wood <40241007+woodsp-ibm@users.noreply.github.com>
Co-authored-by: Kevin Krsulich <kevin.krsulich@ibm.com>
Co-authored-by: Shota Nakasuji <schulta.8715@gmail.com>
Co-authored-by: Dongsin Kim <ds.justin.kim@gmail.com>
Co-authored-by: Divyanshu Singh <55018955+divshacker@users.noreply.github.com>
Co-authored-by: Luís Ferreira <lsferreira169@gmail.com>
Co-authored-by: Lauren Capelluto <laurencapelluto@gmail.com>
Co-authored-by: SooluThomas <soolu.elto@gmail.com>
Co-authored-by: John Lapeyre <jlapeyre@users.noreply.github.com>

CODE_OF_CONDUCT.md

@@ -1,113 +1,9 @@
-# Code of Conduct
-
-## Our Pledge
-
-The Qiskit Community is dedicated to our values of treating every individual
-with respect and dignity. In the interest of fostering an open and welcoming
-environment, all participants, including attendees, speakers, sponsors,
-volunteers, online contributors, and IBM employees are expected to show
-courtesy for each other and our community by creating a harassment-free
-experience for everyone, regardless of age, personal appearance, disability,
-ethnicity, gender identity and expression, body size, level of experience,
-nationality, race, religion, caste, or sexual identity and orientation.
-Expected behavior applies to both online and offline engagement within the
-Qiskit Community.
-
-## Scope
-
-The purpose of this Code of Conduct is to define and enforce the values and
-conduct of contributors and participants in the Qiskit open source community.
-The Code of Conduct applies both within project spaces and in public spaces
-when an individual is engaging with the Qiskit open source community. Examples
-include attending a Qiskit event, contributing to online projects, commentary
-on Slack, or representing a project or community, including using an official
-project e-mail address, posting via an official social media account, or
-acting as an appointed representative at an online or offline event.
-Representation of a project may be further defined and clarified by project
-maintainers.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
+<!-- Copyright Contributors to the Qiskit project. -->
 
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints, experiences, and cultures
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
-- Being mindful of your surroundings and your fellow participants and listening
-  to others
-- Valuing the contributions of all participants
-- Engaging in collaboration before conflict
-- Pointing out unintentionally racist, sexist, casteist, or biased comments and
-  jokes made by community members when they happen
-
-Examples of unacceptable behavior by participants, even when presented as
-"ironic" or "joking," include:
-
-- The use of sexualized language or imagery and unwelcome physical contact,
-  sexual attention, or advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment, including offensive or degrading language
-- Publishing others' private information, such as a physical or electronic
-  address, without explicit permission. This includes any sort of "outing" of
-  any aspect of someone's identity without their consent.
-- "Doxxing," Publishing screenshots or quotes, especially from identity slack
-  channels, private chat, or public events, without all quoted users' explicit
-  consent.
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Responsibilities & Enforcement
-
-The entire Qiskit community is responsible for upholding the terms of the Code
-of Conduct in Qiskit Community events and spaces and reporting violations if
-they see them. The internal Qiskit team at IBM is ultimately responsible for
-clarifying the standards of acceptable behavior and enforcement, and is expected
-to take appropriate and fair corrective action in response to any instances of
-unacceptable behavior.
-
-If a participant or contributor engages in negative or harmful behavior, IBM
-will take any action they deem appropriate, including but not limited to
-issuing warnings, expulsion from an event with no refund, deleting comments,
-permanent banning from future events or online community, or calling local law
-enforcement. IBM has the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, or to temporarily or permanently ban any
-contributor or participant for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-If you see a Code of Conduct violation:
+# Code of Conduct
+All members of this project agree to adhere to the Qiskit Code of Conduct listed at [https://github.com/Qiskit/qiskit/blob/master/CODE_OF_CONDUCT.md](https://github.com/Qiskit/qiskit/blob/master/CODE_OF_CONDUCT.md)
 
-1. If you feel comfortable, let the person know that what they did is not
-   appropriate and ask them to stop and/or edit or delete their message(s) or
-   comment(s).
-2. If the person does not immediately stop the behavior or correct the issue,
-   or if you're uncomfortable speaking up, flag a moderator and, if appropriate,
-   fill out the anonymous
-   [Code of Conduct violation form](https://airtable.com/shrl5mEF4Eun1aIDm).
-3. The Qiskit Community will open an investigation upon receiving your form
-   entry. When reporting, please include any relevant details, links,
-   screenshots, context, or other information that may be used to better
-   understand and resolve the situation.
-4. If the code of conduct violation occurs at an event and requires immediate
-   response or contains a concern about an individual attending an upcoming
-   event, contact the event's on-call Code of Conduct point of contact listed
-   in the event specific code of conduct document. If you don't feel comfortable
-   speaking to the point of contact in person, fill out a Code of Conduct
-   violation form entry and include the details of the event so that the Code of
-   Conduct enforcement board can contact the event's on-call Code of Conduct
-   point of contact.
-5. If an IBM employee witnesses a Code of Conduct violation at any time, such as
-   at events, in a Slack channel, or open source forums, it is their
-   responsibility to file a Code of Conduct violation report.
+----
 
-This Code of Conduct does not supersede existing IBM corporate policies, such as
-the IBM Business Conduct Guidelines and IBM Business Partner Code of Conduct.
-IBM employees must follow IBM's Business Conduct Guidelines. IBM's business
-partners must follow the IBM Business Partner Code of Conduct. IBM employees
-concerned with a fellow IBMer's behavior should follow IBM's own internal HR
-reporting protocols, which include engaging the offending IBMer's manager and
-involving IBM Concerns and Appeals. IBM employees concerned with an IBM
-business partner's behavior should notify tellibm@us.ibm.com.
+License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/),
+Copyright Contributors to Qiskit.

azure-pipelines.yml

@@ -36,10 +36,10 @@ steps:
     python -m pip install --upgrade pip setuptools wheel virtualenv
     virtualenv /tmp/docs_build
     source /tmp/docs_build/bin/activate
-    pip install -U qiskit jupyter sphinx nbsphinx sphinx_rtd_theme
-    pip install 'matplotlib<3.3'
-    pip install -U qiskit[visualization] cvxpy
-    pip install pyscf
+    pip install -c constraints.txt -U qiskit jupyter sphinx nbsphinx sphinx_rtd_theme
+    pip install -c constraints.txt 'matplotlib<3.3'
+    pip install -c constraints.txt -U qiskit[visualization] cvxpy
+    pip install -c constraints.txt pyscf
     sudo apt-get install -y pandoc graphviz
   displayName: 'Install dependencies'
 - bash: |

conf.py

@@ -73,7 +73,8 @@
 exclude_patterns = ['*.ipynb', '_build', 'legacy_tutorials',
                     '**.ipynb_checkpoints']
 
-nbsphinx_timeout = 180
+cell_timeout = int(os.getenv('QISKIT_CELL_TIMEOUT', 180))
+nbsphinx_timeout = cell_timeout
 nbsphinx_execute = 'always'
 nbsphinx_execute_arguments = [
     "--InlineBackend.figure_formats={'png', 'pdf'}",

constraints.txt

@@ -0,0 +1,2 @@
+docplex==2.15.194
+cvxpy<1.1.8

index.rst

@@ -8,12 +8,14 @@ Qiskit Tutorials
 
   Circuits <tutorials/circuits/index.rst>
   Advanced Circuits <tutorials/circuits_advanced/index.rst>
-  Pulse <tutorials/pulse/index.rst>
   High-Performance Simulators <tutorials/simulators/index.rst>
   Quantum System Error Analysis <tutorials/noise/index.rst>
+  Algorithms <tutorials/algorithms/index.rst>
+  Operators <tutorials/operators/index.rst>
   Optimization <tutorials/optimization/index.rst>
   Finance <tutorials/finance/index.rst>
   Chemistry <tutorials/chemistry/index.rst>
+  Machine Learning <tutorials/machine_learning/index.rst>
 
 
 .. Hiding - Indices and tables