py-qua-tools v0.3.1

What's Changed

• change play_at() behavior - play_at() will now use the latest frame & detuning.

py-qua-tools v0.3.0

• Sampling rate is now tuneable within the baking
• Integration weights tool added
• Possibility to delete samples in the baking

py-qua-tools v0.2.2

Minor improvements:

• Clarification in the documentation (readme.md) about the need to declare the Quantum Machine after the baking of all waveforms to ensure they are runnable within the QUA program.

• Removed Entropy dependency from XEB example

py-qua-tools v0.2.1

• Updated docstrings describing the baking tool to make it more readable
• Extended the method get_Op_length() which does not require a quantum element anymore, as the output of the method will be the longest baked waveform across all involved quantum elements if none is provided (specifically useful for the example of 2 qubit RB in qua-libs)
• Refined the method b.align() which was padding 0s to all elements in the config instead of only aligning elements already involved in the baking context manager when no argument was provided. This is now corrected.

py-qua-tools v0.2.0

• Digital waveforms are now editable within the baking and can be attached to arbitrary baked waveforms (b.add_digital_waveform)
• Existing digital waveform can now be attached to a baked operation
• The possibility to update the config or not is now induced directly by the providing of a baking index to adapt the length of the baked reference pulse (no update_config boolean in baking initialization required anymore)
• One can delete a baked Operation from the config using delete_baked_Op (which deletes both analog and digital baked waveforms associated to the baking object)

py-qua-tools v0.1.1 license

fixed license metadata

py-qua-tools v0.1.0

Official first release

py-qua-tools v0.1.0-rc8

updated readme for pip installation

py-qua-tools v0.1.0-rc7

Adding pip release

add compiled

Baking compatibility with add_compiled (#12)

* Update of the config now optional+ possibility to retrieve baked wfs

Baking now allows a simple retrieval of baked waveforms, that can be created according under the constraint of being of a certain length (to ensure compatibility with overriding waveforms with add_compiled feature). Update of original config file no more compulsory, one can now also specify if update of the config should induce an overridable waveform or not

* Added example for pre_compile usage + changed the input parameters for b

Instead of declaring a matching length constraint, one has now to indicate a baking index that indicates which baked waveform should be overwritten (and ensure it matches its length for overriding it with add_compiled)

* Reformat

* Added method delete_baked_Op

This new method (called using b.delete_baked_Op(qe)) allows the direct removal from the input config of the baking object the associated baked operation and associated waveforms