Declare Input and Inout ports of NativeFunctionDefinition without a size expression. Their size will be deduced from calls to it.
Add parsed_counts attribute to ExecutionDetails, where the states are
parsed according to their arithmetic information.
Change transpile_to_hardware field in the ExecutionPreferences to
receive an optimization level and use it.
Add Hadamard transform as a new built-in function. See [HadamardTransform]
(../user-guide/function-library/builtin-functions/hadamard-transform.md).
Improve detection of auxiliary qubits for visualization in the IDE.
Add the initial_point member to OptimizerConfig which is used in construct_combinatorial_optimization_model to specify an initial value to the optimization algorithm.
The execution chart received after execution of circuits in the IDE, can now be filtered by list of results. See Filtering results
Automatically parse the value field of SavedResult according to
its type, with no need to call parse_obj to parse execution results.
Introduce the strict_zero_ios flag in the function call. This gives you
(rather than the engine) responsibility for memory management.
Previously, this was done by the assign_zero_ios flag, which is
deprecated. The logic has been reversed: previously setting assign_zero_ios=True now corresponds to strict_zero_ios=False, and vice
versa.
The default value of OptimizerConfig.alpha_cvar is now 1.0
Change the qubit order of the fields counts and state_vector on ExecutionDetails. They are now returned with lsb right qubit order.
The endianness terminology in ExecutionDetails is changed to qubit order, such that the result 0b10 in qubit order lsb right refers to the number 2.
Provide default values for IBM hardware execution configuration fields: hub, group, and project.
Make the default job name the circuit name. To access to the job's ID - expand it in the Jobs History window.
Introduce the aer_simulator_statevector, aer_simulator_density_matrix and aer_simulator_matrix_product_state to the IDE.
Academic users can now choose to run circuits on Azure with their own credentials instead of through Classiq-Azure integration. More details in the user guide: User guide instructions
Extend the "Advanced Usage > Qubit Release" section and rename it as "Memory Management".
It thoroughly explains the Classiq engine's capabilities of allocating and releasing
qubits and illustrates how user-provided input can aid the synthesis
engine in improving the circuit performance. See Memory Management.