Metadata-Version: 2.1
Name: qprof
Version: 1.3.0
Summary: A quantum circuit profiling tool.
Home-page: UNKNOWN
Author: Adrien Suau
Author-email: adrien.suau@cerfacs.fr
License: UNKNOWN
Project-URL: Bug Reports, https://gitlab.com/qcomputing/qprof/qprof/issues
Project-URL: Source, https://gitlab.com/qcomputing/qprof/qprof
Project-URL: Collaborator, https://cerfacs.fr/en
Keywords: quantum,performance,gprof,profiling
Platform: UNKNOWN
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: Education
Classifier: Intended Audience :: Science/Research
Classifier: Topic :: Scientific/Engineering
Classifier: Topic :: Scientific/Engineering :: Mathematics
Classifier: License :: CeCILL-B Free Software License Agreement (CECILL-B)
Classifier: Natural Language :: English
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3 :: Only
Description-Content-Type: text/x-rst
Requires-Dist: qprof-interfaces
Provides-Extra: all_plugins
Requires-Dist: qprof-myqlm ; extra == 'all_plugins'
Requires-Dist: qprof-qiskit ; extra == 'all_plugins'
Provides-Extra: dev
Requires-Dist: black ; extra == 'dev'
Requires-Dist: pygments ; extra == 'dev'
Requires-Dist: setuptools ; extra == 'dev'
Requires-Dist: wheel ; extra == 'dev'
Requires-Dist: twine ; extra == 'dev'
Provides-Extra: myqlm
Requires-Dist: qprof-myqlm ; extra == 'myqlm'
Provides-Extra: qat
Requires-Dist: qprof-myqlm ; extra == 'qat'
Provides-Extra: qiskit
Requires-Dist: qprof-qiskit ; extra == 'qiskit'

**qprof**
=========

``qprof`` stands for **q**\ uantum **prof**\ iler and aims at providing a
unique tool to profile quantum circuits.

For the moment, ``qprof`` is able to understand quantum circuits generated with
`qiskit <https://qiskit.org>`_ and `myQLM <https://myqlm.github.io>`_ and can
generate profiling results only in a
`gprof <https://sourceware.org/binutils/docs/gprof/>`_-compatible format.

Installation
------------

``qprof`` being a Python module, it is installable with ``pip``.

From Gitlab
~~~~~~~~~~~

.. code:: bash

   git clone https://gitlab.com/qcomputing/qprof/qprof.git
   pip install qprof/

From PyPi
~~~~~~~~~

``qprof`` is now available on PyPi! To download and install the last version, just
type

.. code:: bash

   pip install qprof

Plugins for library support are not installed by default in order to avoid pulling
silently huge dependencies like ``qiskit`` in your project. In order to install the plugins
you can either do it afterwards with pip:

.. code:: bash

   pip install qprof_qiskit  # other libraries are supported

or use the appropriate target when installing ``qprof``:

.. code:: bash

   pip install qprof[qiskit]
   pip install qprof[myqlm]
   pip install qprof[all_plugins]

For developers
~~~~~~~~~~~~~~

Developers might want to install ``qprof`` as an editable project.
To do so you need to clone the git repository and install the library in
editable mode with the `-e` option:

.. code:: bash

   git clone https://gitlab.com/qcomputing/qprof/qprof.git
   pip install -e qprof/

Note that the dependencies will **not** be installed in editable mode. If you want
all the ``qprof`` stack in editable mode, you need to clone and install everything
"by hand":

.. code:: bash

   git clone https://gitlab.com/qcomputing/qprof/qprof.git
   git clone https://gitlab.com/qcomputing/qprof/qprof_interfaces.git
   # Plugins?
   # git clone https://gitlab.com/qcomputing/qprof/qprof_qiskit.git
   pip install -e qprof_interfaces/
   pip install -e qprof/
   # Plugins?
   # pip install -e qprof_qiskit/

Usage
-----

Plugin organisation
~~~~~~~~~~~~~~~~~~~

The ``qprof`` library is organised as follow:

#. A main ``qprof`` library containing all the code related to computing routine
   execution time, call graph, exporting, ...
#. A ``qprof_interfaces`` plugin providing interfaces for the data structures used
   by ``qprof`` to communicate with the plugins.
#. Several ``qprof_XXX`` libraries that are used to adapt a library ``XXX`` to
   ``qprof`` by implementing the interfaces of ``qprof_interfaces``.

Plugins are automatically discovered the first time ``qprof.frameworks`` is imported
and are arranged in a dictionary-like data-structure with the following structure:

.. code:: python

    frameworks = {
        "interfaces": <module 'qprof_interfaces' from '[path]'>, # always present
        "plugin1": <module 'qprof_plugin1' from '[path]'>,
        # ...
        "pluginN": <module 'qprof_pluginN' from '[path]'>,
    }

Plugins are lazy-imported, meaning that the plugin module is imported at the
first access to the dictionary key.

Profiling
~~~~~~~~~

The profiling is performed with the ``qprof.profile`` function.

The ``qprof.profile`` function needs a quantum routine implemented with one of the
supported frameworks along with the "base" gate times, provided as a dictionary, and
an exporter, given either as a string or as an instance of ``BaseExporter``.

Example of profiling:

.. code:: python

    # Import the qprof tools
    from qprof import profile

    # Import the framework tools to generate a quantum routine
    from qiskit.aqua.algorithms import Grover
    from qiskit.aqua.components.oracles import LogicalExpressionOracle


    # Generate the routine to benchmark.
    input_3sat = """
    c example DIMACS-CNF 3-SAT
    p cnf 3 5
    -1 -2 -3 0
    1 -2 3 0
    1 2 -3 0
    1 -2 -3 0
    -1 2 3 0
    """

    oracle = LogicalExpressionOracle(input_3sat)
    grover = Grover(oracle)
    circuit = grover.construct_circuit()

    # Hard-coded gate times retrieved by hand
    gate_times = {"U1": 0, "U2": 89, "U3": 178, "CX": 930, "BARRIER": 0}

    # Profile the resulting quantum routine and use the "gprof" exporter
    qprof_out = profile(circuit, gate_times, "gprof")

    # Print to stdout the analysis report
    print(qprof_out)

Full profiling example
----------------------

Requirements for the example
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You should have the ``dot`` tool installed on your machine, along with the
`gprof2dot <https://github.com/jrfonseca/gprof2dot>`_ tool that can be installed
with ``pip install gprof2dot``.

Profile the code
~~~~~~~~~~~~~~~~

Let save the code of the previous section in a file `profile.py`.

You can generate the following graph with the command

.. code:: bash

    python3 profile.py | gprof2dot | dot -Tpng -o profiling_result.png

.. image:: docs/images/profile_result.png


Limitations
-----------

* ``qprof`` is not able to analyse recursive routine calls yet. If your quantum circuit
  contains calls to recursive routines, expect the unexpected.

Troubleshooting
---------------

"Unknown" routines shows up in reports
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

If "Unknown" routines are showing up in the reports, check that you named
correctly all the routines you defined.

If the problem is still present, open an issue.

Reported times using ``gprof`` output format are false
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The ``gprof`` output format has a very limited precision of 10 milli-seconds when
dealing with timings. This means that routines running in less than 5 milli-seconds
will, due to rounding error, appear as taking 0 milli-seconds.

In order to circumvent this issue, the ``qprof.exporters.GprofExporter`` takes an
optional parameter ``default_time`` in its constructor. This ``default_time``
will be used to scale all the execution times such that the longest routine will
take exactly ``default_time`` seconds on the report.

By default, the value of ``default_time`` is 10 seconds. In order to change it
you need to instantiate the exporter yourself:

.. code::python

    from qprof import profile
    from qprof.exporters import GprofExporter

    routine = # ...
    gate_times = # ...
    exporter = GprofExporter(default_time=100) # 100 seconds for default_time

    result = profile(routine, gate_times, exporter)

Note that giving ``None`` to ``default_time`` will disable the execution time
scaling.


