Skip to main content

qKIT quantum measurement suite in python

Project description

QKIT

Qkit - a quantum measurement suite in python

PyPI - Version PyPI - Python Version Release

Features:

  • a collection of ipython notebooks for measurement and data analysis tasks.
  • hdf5 based data storage of 1,2 and 3 dimensional data, including a viewer.
  • classes for data fitting, e.g. of microwave resonator data. This includes also a robust circle fit algorithm.
  • extended and maintained drivers for various low frequency and microwave electronics.

Platform:

The qkit framework has been tested under windows and with limits under macos x and linux. The gui requires h5py, qt and pyqtgraph, which work fine on these platforms. The core of the framework should run with python 2.7.x/3.4+

Configuration

There are three sources of configuration, which are used to set up your environment

  • qkit defaults (you shouldn't change those)
  • local config file
  • configuration in notebooks

Local config file

On import, qkit will look for a file called qkit_local_config.py or local.py in your current working directory or any of its parents. Note, that in case of a jupyter notebook, the current working directory is the directory in which your notebook is located.

If you can't put such a configuration file into a suitable location, you can set the environment variable QKIT_LOCAL_CONFIG with a path pointing to such a configuration file. This variable circumvents the search, and the file is directly loaded.

Installation Guide

Installing qkit is a two step process: First you need to obtain the qkit package, and then you need to setup your system to use it properly. This guide will provide you with the required steps.

Creating a Virtual Environment

It is mandatory to use a virtual environment if you want to use automatic installation. This isolates this local environment from your global packages. This way, version conflicts can be avoided. You need to activate the virtual environment before using qkit. Otherwise, qkit and its dependencies will not be available.

NOTE: WE DO NOT GUARANTEE COMPATIBILITY WITH ANACONDA/MINICONDA/CONDA! USE AT YOUR OWN RISK!

First, create a virtual environment:

python -m virtualenv venv

And then activate it on Linux:

source venv/bin/activate

or Windows:

.\venv\bin\activate.bat

Obtaining the qkit package

You have two choices, based on whether you want to modify qkit (development) or only want to use it.

Install qkit for usage only

Create a virtual environment, as described above. Then use pip to install qkit:

pip install qkit[jupyter,analysis]

If you are simply using qkit, changes to files in src/ should not be necessary. If you find things you need to change there, this might be a bug. Please report this.

Install qkit for development

Clone this repository to wherever is convenient.

git clone https://github.com/qkitgroup/qkit

Create a virtual environment, as described above.

Now, you can install qkit as an editable package. This means, that you can change files in the cloned repository. Changes will affect your python setup.

The brackets contain optional dependencies. This pulls the libraries needed for jupyter lab.

pip install --editable '.[jupyter,analysis]'

Configuring your system

In order to make .h5-files clickable and to configure qkit globally, run

qkit-install

On Windows, some of the changes require editing the registry. qkit-install can do that automatically, if run with elevated priviledges (as an Admin). To do so, run in a PowerShell

Start-Process qkit-install -Verb runAs

This will associate .h5-files with qkit, and set the environment variables QKIT_LOCAL_CONFIG and QKIT_VENV to the correct values. It will also create the required directories for data, notebooks and logs, and it will instantiate the configuration files for Jupyter Lab and Qkit.

If the notebooks folder this creates does not match your needs, you can change it by modifiying jupyter_lab_config.py:

# Set Notebook directory
notebook_dir = r'C:\notebooks' # Change this line

Launching Jupyter Lab

On Linux, qkit-install will install a desktop file to launch Qkit. Look for "Qkit Jupyter Lab". On Windows, qkit-install will create a batch script launch.bat. You can create a shortcut to it to launch it from the desktop.

Upgrading

If you use an existing installation of qkit, there might be some breaking changes. They are not major, but need to be taken care of.

Migrating Configuration

Previously, the configuration of qkit was located in qkit/config/local.py. As this directory is now a child of src/, you are probably not supposed to touch this file. This method is deprecated (you will receive warnings).

Instead, in a parent directory, a file named qkit_local_config.py is used to configure your environment.

To migrate, copy the code in your old local.py into the new qkit_local_config.py file. Do note, however, that the datadir and logdir paths have changed. It is recommended to use the new values. Conflicting entries in your config may need to be deleted.

"My changes to the configuration are not applied after upgrading"

If your notebooks do not reside in a child directory of qkit, the qkit_local_config.py may not be found, as each notebook launches a Python process in its location running itself. Thus qkit_local_config.py may not be in any of the notebooks parent directories. In this case, either set the environment variable QKIT_LOCAL_CONFIG to your configuration, or place the configuration in your notebook directory instead.

Migrating Notebooks

The new setup assumes, that notebooks are located in notebooks/. This way, qkit_local_config.py is in a parent directory of your notebooks and is thus loaded when you initialize qkit in your notebooks.

On measurement computers, it is recommended to move your notebooks into that directory. Alternatively, update jupyter_lab_config.py to point to the notebook directory:

# Set Notebook directory
notebook_dir = 'notebooks' # Change this line

On Windows, this might be set to:

# Set Notebook directory
notebook_dir = r'C:\notebooks' # Change this line

Also, you will need to migrate your local config to a parent directory of your notebooks, or point to it using the environment variable QKIT_LOCAL_CONFIG. It is possible to set this environment variable in jupyter_lab_config.py, as environment variables are inherited to process children.

Requirements

This project uses python. An up to date installation of python is expected to be present.

Library Usage
pyqt5 GUI
numpy, scipy, uncertainties General Usage
pyqtgraph, matplotlib Plotting
h5py Data Stroage
jupyterlab Interactive Notebooks
jupyterlab-templates Notebook Templating
pyvisa, pyvisa-py Communication with Devices
zhinst Drivers for Zurich Instruments devices
zeromq Messaging
toml Configuration

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

qkit-0.5.4.tar.gz (9.3 MB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

qkit-0.5.4-py3-none-any.whl (5.3 MB view details)

Uploaded Python 3

File details

Details for the file qkit-0.5.4.tar.gz.

File metadata

  • Download URL: qkit-0.5.4.tar.gz
  • Upload date:
  • Size: 9.3 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: python-httpx/0.27.2

File hashes

Hashes for qkit-0.5.4.tar.gz
Algorithm Hash digest
SHA256 ed83b1dfeb7a70856253fda09ce166d91d8b54be1c6dee730929a3df3766f2f5
MD5 d7b230714e4c30d50bca046f28b2f72e
BLAKE2b-256 2f31e5222c29a1caf4e2c598352a1c8ef608bb7e455febe714e7afc2899b2e1d

See more details on using hashes here.

File details

Details for the file qkit-0.5.4-py3-none-any.whl.

File metadata

  • Download URL: qkit-0.5.4-py3-none-any.whl
  • Upload date:
  • Size: 5.3 MB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: python-httpx/0.27.2

File hashes

Hashes for qkit-0.5.4-py3-none-any.whl
Algorithm Hash digest
SHA256 a0f432adddedc4a08e302eceaadc4df537bbd1da69abd7c34af47ccbb7929bc8
MD5 3a3a5f919e07a8844e63fd44c3d075d7
BLAKE2b-256 94ee05811c7222953229c586a657732cf83312004d86fc86dd77f01ce013e44b

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page