This page was generated from docs/examples/DataSet/Working-With-Pandas-and-XArray.ipynb. Interactive online version: .
Working with Pandas and XArray¶
This notebook demonstrates how Pandas and XArray can be used to work with the QCoDeS DataSet. It is not meant as a general introduction to Pandas and XArray. We refer to the official documentation for Pandas and XArray for this. This notebook requires that both Pandas and XArray are installed.
Setup¶
First we borrow an example from the measurement notebook to have some data to work with. We split the measurement in two so we can try merging it with Pandas.
[1]:
%matplotlib inline
from pathlib import Path
import matplotlib.pyplot as plt
import numpy as np
import pandas as pd
import qcodes as qc
from qcodes.dataset import (
Measurement,
initialise_or_create_database_at,
load_or_create_experiment,
)
from qcodes.instrument_drivers.mock_instruments import (
DummyInstrument,
DummyInstrumentWithMeasurement,
)
qc.logger.start_all_logging()
Logging hadn't been started.
Activating auto-logging. Current session state plus future input saved.
Filename : /home/runner/.qcodes/logs/command_history.log
Mode : append
Output logging : True
Raw input log : False
Timestamping : True
State : active
Qcodes Logfile : /home/runner/.qcodes/logs/241121-19310-qcodes.log
Activating auto-logging. Current session state plus future input saved.
Filename : /home/runner/.qcodes/logs/command_history.log
Mode : append
Output logging : True
Raw input log : False
Timestamping : True
State : active
Qcodes Logfile : /home/runner/.qcodes/logs/241121-19310-qcodes.log
[2]:
# preparatory mocking of physical setup
dac = DummyInstrument("dac", gates=["ch1", "ch2"])
dmm = DummyInstrumentWithMeasurement("dmm", setter_instr=dac)
station = qc.Station(dmm, dac)
[3]:
initialise_or_create_database_at(Path.cwd() / "working_with_pandas")
exp = load_or_create_experiment(
experiment_name="working_with_pandas", sample_name="no sample"
)
[4]:
meas = Measurement(exp)
meas.register_parameter(dac.ch1) # register the first independent parameter
meas.register_parameter(dac.ch2) # register the second independent parameter
meas.register_parameter(
dmm.v2, setpoints=(dac.ch1, dac.ch2)
) # register the dependent one
[4]:
<qcodes.dataset.measurements.Measurement at 0x7f31dd371b90>
We then perform a very basic experiment. To be able to demonstrate merging of datasets in Pandas we will perform the measurement in two parts.
[5]:
# run a 2D sweep
with meas.run() as datasaver:
for v1 in np.linspace(-1, 0, 200, endpoint=False):
for v2 in np.linspace(-1, 1, 201):
dac.ch1(v1)
dac.ch2(v2)
val = dmm.v2.get()
datasaver.add_result((dac.ch1, v1), (dac.ch2, v2), (dmm.v2, val))
dataset1 = datasaver.dataset
Starting experimental run with id: 1.
[6]:
# run a 2D sweep
with meas.run() as datasaver:
for v1 in np.linspace(0, 1, 201):
for v2 in np.linspace(-1, 1, 201):
dac.ch1(v1)
dac.ch2(v2)
val = dmm.v2.get()
datasaver.add_result((dac.ch1, v1), (dac.ch2, v2), (dmm.v2, val))
dataset2 = datasaver.dataset
Starting experimental run with id: 2.
Two methods exists for extracting data to pandas dataframes. to_pandas_dataframe
exports all the data from the dataset into a single dataframe. to_pandas_dataframe_dict
returns the data as a dict from measured (dependent) parameters to DataFrames.
Please note that the to_pandas_dataframe
is only intended to be used when all dependent parameters have the same setpoint. If this is not the case for the DataSet then to_pandas_dataframe_dict
should be used.
[7]:
df1 = dataset1.to_pandas_dataframe()
df2 = dataset2.to_pandas_dataframe()
Working with Pandas¶
Lets first inspect the Pandas DataFrame. Note how both dependent variables are used for the index. Pandas refers to this as a MultiIndex. For visual clarity, we just look at the first N points of the dataset.
[8]:
N = 10
[9]:
df1[:N]
[9]:
dmm_v2 | ||
---|---|---|
dac_ch1 | dac_ch2 | |
-1.0 | -1.00 | 0.000689 |
-0.99 | -0.000358 | |
-0.98 | 0.000236 | |
-0.97 | 0.000271 | |
-0.96 | 0.000646 | |
-0.95 | -0.000590 | |
-0.94 | -0.001055 | |
-0.93 | -0.000257 | |
-0.92 | 0.000086 | |
-0.91 | -0.000429 |
We can also reset the index to return a simpler view where all data points are simply indexed by a running counter. As we shall see below this can be needed in some situations. Note that calling reset_index
leaves the original dataframe untouched.
[10]:
df1.reset_index()[0:N]
[10]:
dac_ch1 | dac_ch2 | dmm_v2 | |
---|---|---|---|
0 | -1.0 | -1.00 | 0.000689 |
1 | -1.0 | -0.99 | -0.000358 |
2 | -1.0 | -0.98 | 0.000236 |
3 | -1.0 | -0.97 | 0.000271 |
4 | -1.0 | -0.96 | 0.000646 |
5 | -1.0 | -0.95 | -0.000590 |
6 | -1.0 | -0.94 | -0.001055 |
7 | -1.0 | -0.93 | -0.000257 |
8 | -1.0 | -0.92 | 0.000086 |
9 | -1.0 | -0.91 | -0.000429 |
Pandas has built-in support for various forms of plotting. This does not, however, support MultiIndex at the moment so we use reset_index
to make the data available for plotting.
[11]:
df1.reset_index().plot.scatter("dac_ch1", "dac_ch2", c="dmm_v2")
[11]:
<Axes: xlabel='dac_ch1', ylabel='dac_ch2'>
Similarly, for the other dataframe:
[12]:
df2.reset_index().plot.scatter("dac_ch1", "dac_ch2", c="dmm_v2")
[12]:
<Axes: xlabel='dac_ch1', ylabel='dac_ch2'>
Merging two dataframes with the same labels is fairly simple.
[13]:
df = pd.concat([df1, df2], sort=True)
[14]:
df.reset_index().plot.scatter("dac_ch1", "dac_ch2", c="dmm_v2")
[14]:
<Axes: xlabel='dac_ch1', ylabel='dac_ch2'>
It is also possible to select a subset of data from the datframe based on the x and y values.
[15]:
df.loc[(slice(-1, -0.95), slice(-1, -0.97)), :]
[15]:
dmm_v2 | ||
---|---|---|
dac_ch1 | dac_ch2 | |
-1.000 | -1.00 | 0.000689 |
-0.99 | -0.000358 | |
-0.98 | 0.000236 | |
-0.97 | 0.000271 | |
-0.995 | -1.00 | -0.000177 |
-0.99 | -0.000281 | |
-0.98 | -0.000403 | |
-0.97 | -0.000021 | |
-0.990 | -1.00 | 0.000580 |
-0.99 | -0.000115 | |
-0.98 | 0.000201 | |
-0.97 | -0.000156 | |
-0.985 | -1.00 | 0.000271 |
-0.99 | 0.000139 | |
-0.98 | -0.000486 | |
-0.97 | -0.000414 | |
-0.980 | -1.00 | 0.000355 |
-0.99 | -0.000304 | |
-0.98 | 0.000044 | |
-0.97 | 0.001407 | |
-0.975 | -1.00 | 0.000658 |
-0.99 | -0.000052 | |
-0.98 | 0.000329 | |
-0.97 | 0.000688 | |
-0.970 | -1.00 | 0.000428 |
-0.99 | -0.000444 | |
-0.98 | 0.000426 | |
-0.97 | -0.000728 | |
-0.965 | -1.00 | -0.000496 |
-0.99 | -0.001200 | |
-0.98 | 0.001178 | |
-0.97 | -0.000474 | |
-0.960 | -1.00 | 0.000383 |
-0.99 | -0.000452 | |
-0.98 | 0.000518 | |
-0.97 | 0.000438 | |
-0.955 | -1.00 | -0.000541 |
-0.99 | 0.000225 | |
-0.98 | -0.000537 | |
-0.97 | 0.000238 | |
-0.950 | -1.00 | -0.000505 |
-0.99 | -0.000233 | |
-0.98 | -0.000458 | |
-0.97 | 0.000017 |
Working with XArray¶
In many cases when working with data on rectangular grids it may be more convenient to export the data to a XArray Dataset or DataArray. This is especially true when working in multi-dimentional parameter space.
Let’s setup and rerun the above measurment with the added dependent parameter dmm.v1
.
[16]:
meas.register_parameter(
dmm.v1, setpoints=(dac.ch1, dac.ch2)
) # register the 2nd dependent parameter
[16]:
<qcodes.dataset.measurements.Measurement at 0x7f31dd371b90>
[17]:
# run a 2D sweep
with meas.run() as datasaver:
for v1 in np.linspace(-1, 1, 200):
for v2 in np.linspace(-1, 1, 201):
dac.ch1(v1)
dac.ch2(v2)
val1 = dmm.v1.get()
val2 = dmm.v2.get()
datasaver.add_result(
(dac.ch1, v1), (dac.ch2, v2), (dmm.v1, val1), (dmm.v2, val2)
)
dataset3 = datasaver.dataset
Starting experimental run with id: 3.
The QCoDeS DataSet can be directly converted to a XArray Dataset from the to_xarray_dataset
method. This method returns the data from measured (dependent) parameters to an XArray Dataset. It’s also possible to return a dictionary of XArray DataArray’s if you were only interested in a single parameter using the to_xarray_dataarray
method. For convenience we will access the DataArray’s from XArray’s Dataset directly.
Please note that the to_xarray_dataset
is only intended to be used when all dependent parameters have the same setpoint. If this is not the case for the DataSet then to_xarray_dataarray
should be used.
[18]:
xaDataSet = dataset3.to_xarray_dataset()
[19]:
xaDataSet
[19]:
<xarray.Dataset> Size: 646kB Dimensions: (dac_ch1: 200, dac_ch2: 201) Coordinates: * dac_ch1 (dac_ch1) float64 2kB -1.0 -0.9899 -0.9799 ... 0.9799 0.9899 1.0 * dac_ch2 (dac_ch2) float64 2kB -1.0 -0.99 -0.98 -0.97 ... 0.97 0.98 0.99 1.0 Data variables: dmm_v1 (dac_ch1, dac_ch2) float64 322kB 6.0 6.23 6.006 ... 4.173 4.118 dmm_v2 (dac_ch1, dac_ch2) float64 322kB 0.0008876 0.0006174 ... 0.0004802 Attributes: (12/14) ds_name: results sample_name: no sample exp_name: working_with_pandas snapshot: {"station": {"instruments": {"dmm": {"functions... guid: 0f1a3a90-0000-0000-0000-01934d84be8e run_timestamp: 2024-11-21 06:59:25 ... ... captured_counter: 3 run_id: 3 run_description: {"version": 3, "interdependencies": {"paramspec... parent_dataset_links: [] run_timestamp_raw: 1732172365.4650059 completed_timestamp_raw: 1732172375.786777
As mentioned above it’s also possible to work with a XArray DataArray directly from the DataSet. The DataArray can only contain a single dependent variable and can be obtained from the Dataset by indexing using the parameter name.
[20]:
xaDataArray = xaDataSet["dmm_v2"] # or xaDataSet.dmm_v2
[21]:
xaDataArray
[21]:
<xarray.DataArray 'dmm_v2' (dac_ch1: 200, dac_ch2: 201)> Size: 322kB array([[ 8.87613466e-04, 6.17389328e-04, -3.43904122e-04, ..., -9.69426587e-05, 4.79469760e-04, 4.44712061e-04], [-1.87254244e-05, 5.07445833e-04, -4.43330280e-04, ..., -6.28193687e-05, -5.05939335e-04, 5.39751309e-04], [ 1.12136520e-04, -2.36084597e-04, 1.03568771e-03, ..., 6.42016801e-04, -1.25547855e-04, 4.17653887e-05], ..., [-1.97682962e-04, -1.13319376e-04, -7.59532771e-05, ..., 3.31558653e-04, -8.29296577e-04, -1.55020541e-04], [ 2.94557177e-05, -2.63518874e-05, -1.36377656e-05, ..., -1.52308049e-04, 2.36150746e-04, -1.21166946e-04], [-7.73791024e-04, 7.49397640e-04, 3.12029669e-04, ..., 3.09348527e-04, 1.40653402e-04, 4.80219895e-04]]) Coordinates: * dac_ch1 (dac_ch1) float64 2kB -1.0 -0.9899 -0.9799 ... 0.9799 0.9899 1.0 * dac_ch2 (dac_ch2) float64 2kB -1.0 -0.99 -0.98 -0.97 ... 0.97 0.98 0.99 1.0 Attributes: name: dmm_v2 paramtype: numeric label: Gate v2 unit: V inferred_from: [] depends_on: ['dac_ch1', 'dac_ch2'] units: V long_name: Gate v2
[22]:
fig, ax = plt.subplots(2, 2)
xaDataSet.dmm_v2.plot(ax=ax[0, 0])
xaDataSet.dmm_v1.plot(ax=ax[1, 1])
xaDataSet.dmm_v2.mean(dim="dac_ch1").plot(ax=ax[1, 0])
xaDataSet.dmm_v1.mean(dim="dac_ch2").plot(ax=ax[0, 1])
fig.tight_layout()
Above we demonstrated a few ways to index the data from a DataArray. For instance the DataArray can be directly plotted, the extracted mean or a specific row/column can also be plotted.
Working with XArray on non gridded data.¶
Sometimes your data does not fit well on a regular grid. Perhaps you are sweeping 2 parameters at the same time or you are messuring at random points.
[23]:
# run a 2D sweep
with meas.run() as datasaver:
for v1, v2 in zip(np.linspace(-1, 1, 200), np.linspace(-1, 1, 201)):
dac.ch1(v1)
dac.ch2(v2)
val1 = dmm.v1.get()
val2 = dmm.v2.get()
datasaver.add_result(
(dac.ch1, v1), (dac.ch2, v2), (dmm.v1, val1), (dmm.v2, val2)
)
dataset4 = datasaver.dataset
Starting experimental run with id: 4.
[24]:
xaDataSet = dataset4.to_xarray_dataset()
If this is the case QCoDeS will export the data using a XArray MultiIndex.
[25]:
xaDataSet
[25]:
<xarray.Dataset> Size: 8kB Dimensions: (multi_index: 200) Coordinates: * multi_index (multi_index) object 2kB MultiIndex * dac_ch1 (multi_index) float64 2kB -1.0 -0.9899 -0.9799 ... 0.9899 1.0 * dac_ch2 (multi_index) float64 2kB -1.0 -0.99 -0.98 ... 0.97 0.98 0.99 Data variables: dmm_v1 (multi_index) float64 2kB 6.218 6.142 5.93 ... 4.151 4.08 4.186 dmm_v2 (multi_index) float64 2kB 0.0002085 0.0004548 ... -0.0006164 Attributes: (12/14) ds_name: results sample_name: no sample exp_name: working_with_pandas snapshot: {"station": {"instruments": {"dmm": {"functions... guid: 798b0536-0000-0000-0000-01934d84ea6f run_timestamp: 2024-11-21 06:59:36 ... ... captured_counter: 4 run_id: 4 run_description: {"version": 3, "interdependencies": {"paramspec... parent_dataset_links: [] run_timestamp_raw: 1732172376.6925702 completed_timestamp_raw: 1732172376.7373831
Note how the expected coordinates can be seen above along with a coordinate called multi_index
QCoDeS has build in support for exporting such datasets to NetCDF files using cf_xarray to compress and decompress the data. Note however, that if you manually export or import such XArray datasets to / from NetCDF you will be responsible for compressing / decompressing as needed.
[ ]: