0.10.0
Upgrade Instructions
Interface Changes
- Add a new function to analyzer:
Analyzer(circuit).analyzer_app()
.
- Solve a ground state problem described by the GroundStateProblem object using GroundStateSolver.solve().
See Executing a Ground State Problem.
- Determine the creation of the circuit image using the
draw_image
field of the model preferences. If not set explicitly, the image is not created for big circuits.
Bug Fixes
- Fix the naming of instances in user-defined composite functions. This caused issues when calling the same composite function more than once.
- Fix a bug in the analyzer.
- Fix a synthesis bug that prevented the engine from using some of the available implementations.
New Features
- Add support for execution on Nvidia's cuQuantum simulator.
Note: To use this feature, contact Classiq support.
This feature is available via the Classiq SDK's
NvidiaBackendPreferences
.
To use this feature in the Classiq VSCode extension, use these backend preferences:
{
"backend_preferences": {
"backend_service_provider": "Nvidia",
"backend_name": "statevector"
}
}
- Add support for functions written in OpenQASM 3.0. See:
OpenQASM3.0 support in user-defined functions.
- Accept Parameter type for Rotation gates.
See Standard Gates user guide.
- Add a fourth implementation to the Multi-Control-X function, based on the Maslov(2015) algorithm. See:
Multi-Control-X.
- Introduce custom initial states to QAOA solvers.
See QAOA Solver customization.
- Add Azure hardware partial support in the Analyzer dashboard to support Ionq and Quantinuum hardware.
- Add the exact_solve() method to the GroundStateSolver class. See: chemistry documentation.
- Add the Suzuki-Trotter function. Refer to Suzuki Trotter user guide.
- Add details to errors in the textual model (
.qmod
file).
In the VSCode extension, the errors include the line and column number of the erroneous attribute.