# 0.10.0

## Interface Changes¶

1. Add new function to analyzer: Analyzer(circuit).analyzer_app().
2. In order to solve a ground state problem described by the GroundStateProblem object use GroundStateSolver.solve(). For more details see: Executing a Ground State Problem.
3. The creation of the circuit image is now determined by the draw_image field of the model preferences. If not set explicitly, the image is not created for big circuits.

## Bug Fixes¶

1. Fix naming of instances within user defined composite functions, which caused issues with calling the same composite function more than once.
2. Fixed a bug in the analyzer.
3. Fix synthesis bug which prevented the engine from using some of the available implementations.

## New Features¶

1. Add support for execution on Nvidia's cuQuantum simulator. Note, to use this feature, please contact Classiq support. This feature is available via the Classiq SDK's NvidiaBackendPreferences. To use this feature in the Classiq VSCode extension, use the following backend preferences:
{
"backend_preferences": {
"backend_service_provider": "Nvidia",
"backend_name": "statevector"
}
}

1. Add support for functions written in OpenQASM 3.0. For more details see: OpenQASM3.0 support in user-defined functions
2. Rotation gates can now accept Parameter type. For more information please refer to Standard Gates user guide.
3. Add a fourth implementation to the Multi-Control-X function, based on the Maslov(2015) algorithm. For more details see: Multi-Control-X
4. Introduce custom initial states to QAOA solvers. For more details see: QAOA Solver customization.
5. Add Azure hardware partial support in the Analyzer dashboard - we now support Ionq and Quantinuum hardware.
6. Add exact_solve() method to GroundStateSolver class. For more details see: chemistry documentation
8. Errors in the textual model (.qmod file) are now more detailed. In the VSCode extension, the errors include the line and column number of the erroneous attribute.