sqdtoolz 0.9.0.dev1__tar.gz

sqdtoolz-0.9.0.dev1/LICENSE

@@ -0,0 +1,203 @@
+Copyright 2026 NQCT Australia
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute
+          must include a readable copy of the attribution notices
+          contained within such NOTICE file, excluding those notices
+          that do not pertain to any part of the Derivative Works,
+          in at least one of the following places: within a NOTICE text
+          file distributed as part of the Derivative Works; within the
+          Source form or documentation, if provided along with the
+          Derivative Works; or, within a display generated by the
+          Derivative Works, if and wherever such third-party notices
+          normally appear. The contents of the NOTICE file are for
+          informational purposes only and do not modify the License.
+          You may add Your own attribution notices within Derivative
+          Works that You distribute, alongside or as an addendum to
+          the NOTICE text from the Work, provided that such additional
+          attribution notices cannot be construed as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing
+      the origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

sqdtoolz-0.9.0.dev1/PKG-INFO

@@ -0,0 +1,125 @@
+Metadata-Version: 2.4
+Name: sqdtoolz
+Version: 0.9.0.dev1
+Summary: toolbox to control and run experiments
+Author-email: Prasanna Pakkiam <p.pakkiam@uq.edu.au>, Rohit Beriwal <r.beriwal@uq.edu.au>
+Project-URL: Homepage, https://github.com/sqdlab/sqdtoolz
+Keywords: control toolbox,timing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: numpy
+Requires-Dist: matplotlib
+Requires-Dist: scipy
+Requires-Dist: bokeh
+Requires-Dist: openqasm3
+Requires-Dist: openpulse
+Requires-Dist: pandas==2.3.3
+Requires-Dist: h5py
+Provides-Extra: full
+Requires-Dist: qcodes>=0.21.0; extra == "full"
+Requires-Dist: pyvisa-py; extra == "full"
+Requires-Dist: resonator-tools; extra == "full"
+Requires-Dist: ply; extra == "full"
+Requires-Dist: laboneq; extra == "full"
+Requires-Dist: laboneq-applications; extra == "full"
+Dynamic: license-file
+
+# SQDToolz
+
+[![UnitTests](https://github.com/sqdlab/SQDToolz/actions/workflows/UnitTests.yaml/badge.svg)](https://github.com/sqdlab/SQDToolz/actions/workflows/UnitTests.yaml)
+
+This is a toolbox to control instruments to run a general lab experiments. This was designed to supersede *UQTools*, keeping simplicity, scalability and efficiency in check. It currently uses QCoDeS to communicate with the instruments, while providing higher level functionality such as timing control, pulse generation, automatic parameter updates and data/configuration storage.
+
+There are two classes of documentation provided for this stack:
+
+- [User documentation](docs/User/Readme.md)
+    - [Driver-specific documentation](docs/User/InstrumentSpecific/Readme.md)
+    - [Custom device documentation](docs/User/CustomDevices/Readme.md)
+    - [Measurement methods](docs/User/MeasurementMethods/Readme.md)
+- [Developer documentation](docs/Developer/Readme.md)
+
+
+## Installation instructions:
+
+Although SQDToolz is on PyPI to satisfy other dependency chains, it is typically installed by cloning the repository and running the setup file via pip as an editable installation. Note that it is done in the editable mode so that one may modify the stack and push changes to GIT without upsetting the pip package manager. If the goal is to simply install the latest standalone release, then just run `pip install sqdtoolz[full]` after activating the venv (i.e. no need to clone the repository etc.). Omit `[full]` if the instrumentation/control stack need not be installed.
+
+Run Anaconda prompt and run the following command to create an environment (in this example, the name is sqdtoolz_env):
+
+```
+conda create -n sqdtoolz_env python=3.10
+```
+
+Now activate the environment:
+
+```
+activate sqdtoolz_env
+```
+
+Now choose a folder to house the SQDToolz stack (idea is to create an editable folder such that the code can be modified and pushed without upsetting the pip package manager). Once navigating to this folder, run the usual GIT clone:
+
+```
+cd C:/Users/....../myFolder/
+git clone https://github.com/sqdlab/sqdtoolz.git
+```
+
+Now there is a sqdtoolz folder in the current directory. Do not enter this new folder. Simply run:
+
+```
+pip install -e sqdtoolz[full]
+```
+
+This should install all required dependencies.
+
+## Updating new required packages
+
+Just log into the virtual environment, navigate to the sqdtoolz folder and then run:
+
+```
+python -m pip install -e sqdtoolz[full]
+```
+
+## Basic design overview:
+
+The stack is structured as follows:
+
+1. Laboratory - highest level object that holds experiment parameters, runs experiments and handles saving of data and experiment+instrument configurations
+
+2. Experiment - an object when run will generate a set of input gates (e.g. to a qubit) while receiving output signals (e.g. qubit readout). The language here is generic and agnostic to the underlying implementation.
+
+3. Experiment-Configuration - sets up the trigger relations between the HAL instruments and handles the translations of generic pulse sequences into the actual AWG channels (e.g. mapping a qubit gate-sequence onto two AWG channels when using IQ modulation).
+
+4. HAL - the Hardware-Abstraction-Layer is used to package raw instruments (e.g. DDG, AWG and ACQ instruments) for use in describing trigger relationships and to send commands (e.g. programming waveforms) in an instrument-agnostic manner (i.e. the interface to command different AWGs is done so via the same object properties and interface functions). The HAL abstracts the specific device into a particular type; this standardisation enables easy browsing of parameters. For example, given two microwave sources from Tektronix and Keysight, both sources will use the associated HAL object `GENmwSource` to ensure a uniform API when handling said objects (e.g. to set the output frequency, one just sets the universal `Frequency` property of the `GENmwSource` object).
+
+5. QCoDeS-Drivers: This has all the vendor level drivers for the instruments. Most instruments have pyVISA implementation, while others use local APIs (e.g. HiSLIP or some DLL).
+
+## Overview
+
+Basic workflow involves:
+
+- A `Laboratory` object is created for a given experimental run. This specifies the output directory.
+- Devices that may be used are specified in the YAML (as per QCoDeS).
+- Devices desired for a given experimental run are loaded from the YAML and then housed inside HAL objects
+- Devices desired for a particular experiment are loaded into an `ExperimentConfiguration` object to store all HAL parameters and device settings (e.g. waveforms, frequencies, powers etc.) and trigger relationships for the timing diagram.
+- When running an experiment (whether it is a default one or a custom one), the given `ExperimentConfiguration` object is used to instantiate the `Experiment` object.
+
+When the experiment finishes, it creates a folder with the date and time-stamp. Said folder includes:
+
+- At least, one HDF5 file with the output data (usually updated in real-time to enable live-plotting)
+- `timing_diagram.png` - the timing diagram of instruments used in the current experiment highlighting the trigger relationships and the time-frames win which instruments output or acquire signals.
+- `laboratory_parameters.txt` - names and values of currently defined `Variable` objects in the current experimental run
+- `laboratory_configuration.txt` - a full dump of all HAL-level instrument parameters. This is used to easily browse the instrument parameters (e.g. frequency, power, sample-rates etc.). In fact, the `ExperimentViewer` UI uses this file to easily compare instrument parameters between two different experiments.
+- `instrument_configuration.txt` - a QCoDeS instrument parameter dump. Used as a last resort for it is heavily obfuscated with the device-specific parameters.
+
+Note that the folder may also include other files such as fitted plots if the derived `Experiment` object outputs said files. Other noteworthy features include:
+
+- Flexible waveform generation engine that includes auto-compression that utilises the sequencing functionality (in supported AWGs) to lower the waveform memory usage.
+- Live `ExperimentViewer` module that shows the current state of all HAL-level parameters in the experiment. It is useful to help ensure that the desired instruments are in the correct states during the experiment. It can be run via `lab.open_browser()`.
+- Live plotting engine when using SQDViz.
+- Structural types supported via `ExperimentSpecification`. For example, a qubit type can hold parameters such as its drive frequency, optimal drive amplitude/time for Pauli-X Gates, T1 time etc.
+
+It should be noted that experiments can automatically interface with parameters (either inside `ExperimentSpecification` or normal `Variable` objects). For example, a Rabi experiment will automatically fit the resulting oscillations to update the currently optimal drive amplitude and time for Pauli-X gates on a given qubit. Thus, one may run cascades of experiments in an automated sequence. A usual sequence might be to run a Rabi experiment (update the currently optimal tipping $\pi/2$ amplitude), run a more optimal Ramsey experiment (update the detuning frequency) and finally run a T1 experiment with the optimal qubit drive parameters. This three-experiment combination could be run in a loop with all **parameters being updated and saved automatically in real-time**. Using the experiment grouping functionality, one may group all said experiments into a single time-stamped folder with the data IO retrieval functionality present to automatically amalgamate all results across multiple experiments (e.g. this is useful when trying to collate all T1 values when generating T1-statistics).
+

sqdtoolz-0.9.0.dev1/README.md

@@ -0,0 +1,95 @@
+# SQDToolz
+
+[![UnitTests](https://github.com/sqdlab/SQDToolz/actions/workflows/UnitTests.yaml/badge.svg)](https://github.com/sqdlab/SQDToolz/actions/workflows/UnitTests.yaml)
+
+This is a toolbox to control instruments to run a general lab experiments. This was designed to supersede *UQTools*, keeping simplicity, scalability and efficiency in check. It currently uses QCoDeS to communicate with the instruments, while providing higher level functionality such as timing control, pulse generation, automatic parameter updates and data/configuration storage.
+
+There are two classes of documentation provided for this stack:
+
+- [User documentation](docs/User/Readme.md)
+    - [Driver-specific documentation](docs/User/InstrumentSpecific/Readme.md)
+    - [Custom device documentation](docs/User/CustomDevices/Readme.md)
+    - [Measurement methods](docs/User/MeasurementMethods/Readme.md)
+- [Developer documentation](docs/Developer/Readme.md)
+
+
+## Installation instructions:
+
+Although SQDToolz is on PyPI to satisfy other dependency chains, it is typically installed by cloning the repository and running the setup file via pip as an editable installation. Note that it is done in the editable mode so that one may modify the stack and push changes to GIT without upsetting the pip package manager. If the goal is to simply install the latest standalone release, then just run `pip install sqdtoolz[full]` after activating the venv (i.e. no need to clone the repository etc.). Omit `[full]` if the instrumentation/control stack need not be installed.
+
+Run Anaconda prompt and run the following command to create an environment (in this example, the name is sqdtoolz_env):
+
+```
+conda create -n sqdtoolz_env python=3.10
+```
+
+Now activate the environment:
+
+```
+activate sqdtoolz_env
+```
+
+Now choose a folder to house the SQDToolz stack (idea is to create an editable folder such that the code can be modified and pushed without upsetting the pip package manager). Once navigating to this folder, run the usual GIT clone:
+
+```
+cd C:/Users/....../myFolder/
+git clone https://github.com/sqdlab/sqdtoolz.git
+```
+
+Now there is a sqdtoolz folder in the current directory. Do not enter this new folder. Simply run:
+
+```
+pip install -e sqdtoolz[full]
+```
+
+This should install all required dependencies.
+
+## Updating new required packages
+
+Just log into the virtual environment, navigate to the sqdtoolz folder and then run:
+
+```
+python -m pip install -e sqdtoolz[full]
+```
+
+## Basic design overview:
+
+The stack is structured as follows:
+
+1. Laboratory - highest level object that holds experiment parameters, runs experiments and handles saving of data and experiment+instrument configurations
+
+2. Experiment - an object when run will generate a set of input gates (e.g. to a qubit) while receiving output signals (e.g. qubit readout). The language here is generic and agnostic to the underlying implementation.
+
+3. Experiment-Configuration - sets up the trigger relations between the HAL instruments and handles the translations of generic pulse sequences into the actual AWG channels (e.g. mapping a qubit gate-sequence onto two AWG channels when using IQ modulation).
+
+4. HAL - the Hardware-Abstraction-Layer is used to package raw instruments (e.g. DDG, AWG and ACQ instruments) for use in describing trigger relationships and to send commands (e.g. programming waveforms) in an instrument-agnostic manner (i.e. the interface to command different AWGs is done so via the same object properties and interface functions). The HAL abstracts the specific device into a particular type; this standardisation enables easy browsing of parameters. For example, given two microwave sources from Tektronix and Keysight, both sources will use the associated HAL object `GENmwSource` to ensure a uniform API when handling said objects (e.g. to set the output frequency, one just sets the universal `Frequency` property of the `GENmwSource` object).
+
+5. QCoDeS-Drivers: This has all the vendor level drivers for the instruments. Most instruments have pyVISA implementation, while others use local APIs (e.g. HiSLIP or some DLL).
+
+## Overview
+
+Basic workflow involves:
+
+- A `Laboratory` object is created for a given experimental run. This specifies the output directory.
+- Devices that may be used are specified in the YAML (as per QCoDeS).
+- Devices desired for a given experimental run are loaded from the YAML and then housed inside HAL objects
+- Devices desired for a particular experiment are loaded into an `ExperimentConfiguration` object to store all HAL parameters and device settings (e.g. waveforms, frequencies, powers etc.) and trigger relationships for the timing diagram.
+- When running an experiment (whether it is a default one or a custom one), the given `ExperimentConfiguration` object is used to instantiate the `Experiment` object.
+
+When the experiment finishes, it creates a folder with the date and time-stamp. Said folder includes:
+
+- At least, one HDF5 file with the output data (usually updated in real-time to enable live-plotting)
+- `timing_diagram.png` - the timing diagram of instruments used in the current experiment highlighting the trigger relationships and the time-frames win which instruments output or acquire signals.
+- `laboratory_parameters.txt` - names and values of currently defined `Variable` objects in the current experimental run
+- `laboratory_configuration.txt` - a full dump of all HAL-level instrument parameters. This is used to easily browse the instrument parameters (e.g. frequency, power, sample-rates etc.). In fact, the `ExperimentViewer` UI uses this file to easily compare instrument parameters between two different experiments.
+- `instrument_configuration.txt` - a QCoDeS instrument parameter dump. Used as a last resort for it is heavily obfuscated with the device-specific parameters.
+
+Note that the folder may also include other files such as fitted plots if the derived `Experiment` object outputs said files. Other noteworthy features include:
+
+- Flexible waveform generation engine that includes auto-compression that utilises the sequencing functionality (in supported AWGs) to lower the waveform memory usage.
+- Live `ExperimentViewer` module that shows the current state of all HAL-level parameters in the experiment. It is useful to help ensure that the desired instruments are in the correct states during the experiment. It can be run via `lab.open_browser()`.
+- Live plotting engine when using SQDViz.
+- Structural types supported via `ExperimentSpecification`. For example, a qubit type can hold parameters such as its drive frequency, optimal drive amplitude/time for Pauli-X Gates, T1 time etc.
+
+It should be noted that experiments can automatically interface with parameters (either inside `ExperimentSpecification` or normal `Variable` objects). For example, a Rabi experiment will automatically fit the resulting oscillations to update the currently optimal drive amplitude and time for Pauli-X gates on a given qubit. Thus, one may run cascades of experiments in an automated sequence. A usual sequence might be to run a Rabi experiment (update the currently optimal tipping $\pi/2$ amplitude), run a more optimal Ramsey experiment (update the detuning frequency) and finally run a T1 experiment with the optimal qubit drive parameters. This three-experiment combination could be run in a loop with all **parameters being updated and saved automatically in real-time**. Using the experiment grouping functionality, one may group all said experiments into a single time-stamped folder with the data IO retrieval functionality present to automatically amalgamate all results across multiple experiments (e.g. this is useful when trying to collate all T1 values when generating T1-statistics).
+

sqdtoolz-0.9.0.dev1/pyproject.toml

@@ -0,0 +1,64 @@
+[build-system]
+requires = ["setuptools>=61"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "sqdtoolz"
+version = "0.9.0.dev1"
+description = "toolbox to control and run experiments"
+readme = "README.md"
+requires-python = ">=3.10"
+authors = [
+    { name = "Prasanna Pakkiam", email = "p.pakkiam@uq.edu.au" },
+    { name = "Rohit Beriwal", email = "r.beriwal@uq.edu.au" }
+]
+keywords = ["control toolbox", "timing"]
+
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Programming Language :: Python :: 3 :: Only",
+    "Operating System :: OS Independent",
+]
+
+dependencies = [
+    "numpy",
+    "matplotlib",
+    "scipy",
+    "bokeh",
+    "openqasm3",
+    "openpulse",
+    "pandas==2.3.3",
+    "h5py"
+]
+
+[project.optional-dependencies]
+full = [
+    "qcodes>=0.21.0",
+    "pyvisa-py",
+    "resonator-tools",
+    "ply",
+    "laboneq",
+    "laboneq-applications",
+]
+
+[dependency-groups]
+dev = [
+    "build>=1.5.0",
+    "twine>=6.2.0",
+]
+
+[project.urls]
+Homepage = "https://github.com/sqdlab/sqdtoolz"
+
+[tool.setuptools]
+include-package-data = true
+license-files = ["LICENSE"]
+
+[tool.setuptools.packages.find]
+include = ["sqdtoolz*"]
+
+[tool.setuptools.package-data]
+sqdtoolz = [
+    "**/*.py",
+    "**/*.inc",
+]

sqdtoolz-0.9.0.dev1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+