# 0.10.0

## Interface Changes¶

1. Add a new function to analyzer: Analyzer(circuit).analyzer_app().
2. Solve a ground state problem described by the GroundStateProblem object using GroundStateSolver.solve(). See Executing a Ground State Problem.
3. 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¶

1. Fix the naming of instances in user-defined composite functions. This caused issues when calling the same composite function more than once.
2. Fix a bug in the analyzer.
3. Fix a synthesis bug that 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, 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"
}
}

1. Add support for functions written in OpenQASM 3.0. See: OpenQASM3.0 support in user-defined functions.
2. Accept Parameter type for Rotation gates. See Standard Gates user guide.
3. Add a fourth implementation to the Multi-Control-X function, based on the Maslov(2015) algorithm. See: Multi-Control-X.
4. Introduce custom initial states to QAOA solvers. See QAOA Solver customization.
5. Add Azure hardware partial support in the Analyzer dashboard to support Ionq and Quantinuum hardware.
6. Add the exact_solve() method to the GroundStateSolver class. See: chemistry documentation.
7. Add the Suzuki-Trotter function. Refer to Suzuki Trotter user guide.
8. 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.