Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Aqua 0.7 planning doc into RfCs, add note about notebooks #7

Merged
merged 3 commits into from
Jan 28, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -72,3 +72,9 @@ site/

# pdf
*.pdf

# PyCharm
*.idea

#Mac OS X
.DS_Store
108 changes: 108 additions & 0 deletions 0002-Aqua_0.7_release_priorities_and_plan.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,108 @@
# Aqua 0.7 Release Priorities and Plan

| **Status** | **Accepted** |
|:------------------|:---------------------------------------------|
| **RFC #** | 0002 |
| **Authors** | Donny Greenberg (donny@ibm.com) |
| **Deprecates** | NA |
| **Submitted** | 2019-12-04 |
| **Updated** | 2020-01-23 |

_Release target: 17-Mar-2020_

## Design & Review Process

Socialization and consensus of large project designs are critical for a decentralized software team to function, especially working on such complicated and diverse code as Aqua. For this release cycle, Aqua will follow a standard Design Doc+Design Review process. For large projects, owners are expected to write a design doc, book a 30 minute slot in design review, and present their design. Broader members of the software or research team to which a particular design is relevant should be invited to the review. Owners and teams should attempt not to begin investing time in code and systems which have not been socialized and agreed upon in review.

## Prioritized Features

_If you are interested in joining any effort below, please reach out to [donny@ibm.com](mailto:donny@ibm.com) or to the project owner on Qiskit Slack._

### Aqua Core Primitives Redesign - Algorithm, Operator, Ansatz, Circuits

* QuantumAlgorithm Hierarchy - *Owner: Donny*
* Base Classes for QuantumAlgorithms of common purpose (e.g. MinEigensolver) to relate interchangeable algorithms and enforce consistent methods and properties
* Break up algorithms which rely on common code so each hold algorithm-primitive objects of more generic utility
* Operator Refactor 2.0 - *Owner: Donny, Chris Wood*
* Split Operator into Terra operators and ExpectationValue and Evolution Algorithms
* Coordinate with LadderOperator addition in Chemistry
* *Reach: Expectation Value Tomography reconciliation with Ignis Tomography*
* Aer ExpectationValue RemoteAlgorithm
* Laying the API groundwork for high priority RemoteAlgorithms (e.g. variational optimization, expectation values)
* Ansatz (FKA: VariationalForm / FeatureMap) refactor - *Owner: Julien*
* Hierarchy and structural flexibility: Ansatz Base Utility Class, TwoLocalAnsatz, OperatorEvolutionAnsatz
* Individual parameter access to shared parameters in Ansatze
* *Reach: Analytical Gradients expansion*
* Circuit Primitives Redesign - *Owner: Julien*
* Move arithmetic and primitive circuits into Terra, make into gates (including tests)
* Deprecate Circuit Factories (blocked on Terra introducing controlled gates)
* Replace QuantumRegister passing with Gate/Instruction passing across Aqua

### Improving Code Clarity and Navigability

* JSON Removal - *Owner: Manoel*
* Deprecation design
* Implementation across Aqua and tutorials
* Deprecation messages in code and GUI in minor version release (Dec 17)
* Repository structure redesign - *Owner: Donny, Manoel*
* Break out application-specific code into applications directories
* Modify nomenclature and directory navigation to match user expectations and canonical conventions
* Shard applications-specific components into applications stacks and move algorithmic primitives into the algorithm stack (e.g. QPE)
* Documentation Revamp - *Owner: Steve, Manoel*
* Long-term plan for Documentation and Docstrings
* _Out of scope: full documentation rewrite_

### Performance Improvements in Simulation and Hardware

* Performance Enhancements - *Owner: Donny, Chris Wood*
* Pass a parameterized Qobj rather than list of many deepcopied circuits for each parameterization when taking expectation values in Aer and BasicAer
* Replace “matrix mode” statevector simulation with QASM simulation so full statevector doesn’t need to be returned
* Error Mitigation - *Owner: Donny, George Barron*
* Clear and extensible interface for employing error mitigation, including possible combinations of techniques (Ignis)
* Gate-based Richardson Extrapolation (Ignis)
* Pulse-based Richardson Extrapolation Error Mitigation (Ignis)
* Submatrix Measurement Error Mitigation (Ignis)

### Physics Software Stack
*Owner: Panos*

* Support generic building blocks for Lattice Gauge Theory, including popular lattice models and Hamiltonian forms (e.g. QCD, Fermi-Hubbard)
* Light-matter interaction
* Magnetism
* Protein Folding


### Chemistry Software Stack
*Owner: Panos*

* Stack design v2
* LadderOperators refactor
* Z2 Symmetry Logic _(Steve)_
* Basis Optimization
* Rotated Hamiltonian Basis _(Pauline)_
* Q-UCCSD extension ansatze _(Igor)_
* Stack design - ElectronicGroundState, ElectronicExcitedState, DissociationCurve
* DFT Drivers


### Optimization Software Stack
*Owner: Stefan*

* Stack design v0 - CPLEX OptimizationProblem specification, QUBO/MBO Solver and Result interfaces, IsingQUBOSolver
* Driver interfaces - CPLEX and Convex Solver
* Slack variable MBO Solver


### Finance Software Stack
*Owner: Stefan*

* Stack design v0
* AmplitudeEstimation hierarchy


### ML Software Stack
*Owner: Donny*

* Stack design v0 - SVC, qGAN, HHL
* Recommendation Systems, qSVE Linear Solver
* Driver interfaces - Pytorch, Scikit
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,8 @@ projects. The committee is responsible for guiding, reviewing and finally
closing/approving the RFC.

# Template
Use the [Qiskit RFC template](0000-template.md) to prepare your RFC.
Use the [Qiskit RFC template](0000-template.md) to prepare your RFC. Jupyter
notebooks (.ipynb files) may also be used with the same template.

## License
[License]: #license
Expand Down