module-qc-tools 2.7.1__tar.gz → 2.9.0__tar.gz

{module_qc_tools-2.7.1 → module_qc_tools-2.9.0}/.pre-commit-config.yaml

@@ -1,6 +1,7 @@
 ci:
   autoupdate_commit_msg: "chore: update pre-commit hooks"
   autofix_commit_msg: "style: pre-commit fixes"
+  autoupdate_schedule: "monthly"
 
 repos:
   - repo: https://github.com/pre-commit/pre-commit-hooks
@@ -43,7 +44,7 @@ repos:
         additional_dependencies: [black==22.3.0]
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.14.1
+    rev: v0.14.13
     hooks:
       - id: ruff-check
         args: ["--fix", "--show-fixes"]
@@ -57,7 +58,7 @@ repos:
       - id: rst-inline-touching-normal
 
   - repo: https://github.com/rbubley/mirrors-prettier
-    rev: "v3.6.2"
+    rev: "v3.8.0"
     hooks:
       - id: prettier
         types_or: [yaml, markdown, html, css, scss, javascript] #, json]
@@ -96,7 +97,7 @@ repos:
   #      additional_dependencies: ["repo-review[cli]"]
 
   - repo: https://github.com/asottile/pyupgrade
-    rev: v3.21.0
+    rev: v3.21.2
     hooks:
       - id: pyupgrade
         args: ["--py38-plus"]

{module_qc_tools-2.7.1 → module_qc_tools-2.9.0}/.zenodo.json

@@ -1,8 +1,8 @@
 {
     "description": " general python tool for running ITkPixV1.1 and ITkPixV2 module QC tests for the ATLAS ITk project",
     "license": "MIT",
-    "title": "atlas-itk-pixel-modules/mqt: v2.7.1",
-    "version": "v2.7.1",
+    "title": "atlas-itk-pixel-modules/mqt: v2.9.0",
+    "version": "v2.9.0",
     "upload_type": "software",
     "creators": [
     {
@@ -120,7 +120,7 @@
     "related_identifiers": [
         {
             "scheme": "url",
-            "identifier": "https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tree/v2.7.1",
+            "identifier": "https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tree/v2.9.0",
             "relation": "isSupplementTo"
         }
     ]

{module_qc_tools-2.7.1 → module_qc_tools-2.9.0}/CITATION.cff

@@ -77,6 +77,6 @@ keywords:
 license:
 - mit
 message: If you use this software, please cite it using the metadata from this file.
-title: 'atlas-itk-pixel-modules/mqt: v2.7.1'
+title: 'atlas-itk-pixel-modules/mqt: v2.9.0'
 type: software
-version: v2.7.1
+version: v2.9.0

{module_qc_tools-2.7.1 → module_qc_tools-2.9.0}/PKG-INFO

@@ -1,11 +1,11 @@
 Metadata-Version: 2.4
 Name: module_qc_tools
-Version: 2.7.1
+Version: 2.9.0
 Summary: Module qc tools
 Project-URL: Homepage, https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools
 Project-URL: Bug Tracker, https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/issues
 Project-URL: Source, https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools
-Project-URL: Documentation, https://atlas-itk-pixel-mqt.docs.cern.ch/2.7/
+Project-URL: Documentation, https://atlas-itk-pixel-mqt.docs.cern.ch/2.9/
 Author-email: Jay Chan <jay.chan@cern.ch>
 Maintainer-email: Giordon Stark <gstark@cern.ch>
 License: Copyright (c) 2018 ATLAS ITk Pixel Modules
@@ -33,8 +33,8 @@ Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3
 Requires-Python: >=3.9
 Requires-Dist: check-jsonschema
-Requires-Dist: module-qc-data-tools>=1.4.0
-Requires-Dist: module-qc-database-tools>=2.9.0
+Requires-Dist: module-qc-data-tools>=1.7.0
+Requires-Dist: module-qc-database-tools>=2.11.2
 Requires-Dist: numpy
 Requires-Dist: packaging
 Requires-Dist: pre-commit
@@ -45,7 +45,7 @@ Requires-Dist: typer>=0.18.0
 Requires-Dist: urllib3<2,>=1.26.20; 'el7.x86_64' in platform_release
 Description-Content-Type: text/markdown
 
-# module-qc-tools v2.7.1
+# module-qc-tools v2.9.0
 
 A general python tool for running ITkPixV1.1 and ITkPixV2 module QC tests
 

{module_qc_tools-2.7.1 → module_qc_tools-2.9.0}/README.md

@@ -1,4 +1,4 @@
-# module-qc-tools v2.7.1
+# module-qc-tools v2.9.0
 
 A general python tool for running ITkPixV1.1 and ITkPixV2 module QC tests
 

{module_qc_tools-2.7.1 → module_qc_tools-2.9.0}/docs/config.md

@@ -74,19 +74,20 @@ low voltage power supply
 
 **Configuration settings**
 
-| Name                  | Description                                                                                                                                                                                                                                 |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `run_dir`             | path (relative or absolute) to the directory where `power_supply` commands should be run                                                                                                                                                    |
-| `on_cmd`              | command to turn on the power supply with specified voltage and current. Use the syntax `{v}` and `{i}` to represent the voltage and current that are to be given as input arguments                                                         |
-| `off_cmd`             | command to turn off the power supply                                                                                                                                                                                                        |
-| `set_cmd`             | command to set voltage and current for power supply. Use the syntax `{v}` and `{i}` to represent the voltage and current that are to be given as input arguments                                                                            |
-| `getI_cmd`            | command to inquire the set current of the power supply. This command shall return a std output which represents the value of the current (float in the unit of [A]). For example, when I = 5.2A, `getI_cmd` returns std output = `5.2`.     |
-| `getV_cmd`            | command to inquire the set voltage of the power supply. This command shall return a std output which represents the value of the voltage (float in the unit of [V]). For example, when V = 1.8V, `getV_cmd` returns std output = `1.8`.     |
-| `measI_cmd`           | command to measure the output current of the power supply. This command shall return a std output which represents the value of the current (float in the unit of [A]). For example, when I = 5.2A, `measI_cmd` returns std output = `5.2`. |
-| `measV_cmd`           | command to measure the output voltage of the power supply. This command shall return a std output which represents the value of the voltage (float in the unit of [V]). For example, when V = 1.8V, `measV_cmd` returns std output = `1.8`. |
-| `n_try`               | number of re-tries in case the script fails to read from the power supply                                                                                                                                                                   |
-| `checkTarget_timeout` | after each `set_cmd` call, `measI_cmd` is called to check if the target is reached, if not after `checkTarget_timeout` (in sec.), an exception is raised                                                                                    |
-| `success_code`        | exit status that indicates success. The default is 0.                                                                                                                                                                                       |
+| Name                  | Description                                                                                                                                                                                                                                                      |
+| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `run_dir`             | path (relative or absolute) to the directory where `power_supply` commands should be run                                                                                                                                                                         |
+| `on_cmd`              | command to turn on the power supply with specified voltage and current. Use the syntax `{v}` and `{i}` to represent the voltage and current that are to be given as input arguments                                                                              |
+| `off_cmd`             | command to turn off the power supply                                                                                                                                                                                                                             |
+| `set_cmd`             | command to set voltage and current for power supply. Use the syntax `{v}` and `{i}` to represent the voltage and current that are to be given as input arguments                                                                                                 |
+| `getI_cmd`            | command to inquire the set current of the power supply. This command shall return a std output which represents the value of the current (float in the unit of [A]). For example, when I = 5.2A, `getI_cmd` returns std output = `5.2`.                          |
+| `getV_cmd`            | command to inquire the set voltage of the power supply. This command shall return a std output which represents the value of the voltage (float in the unit of [V]). For example, when V = 1.8V, `getV_cmd` returns std output = `1.8`.                          |
+| `getState_cmd`        | command to inquire the state of the output channel. This command shall return a std output which represents the state of the channel. When the output is turned on, `getState_cmd` shall return `ON`. When the output is off, `getState_cmd` shall return `OFF`. |
+| `measI_cmd`           | command to measure the output current of the power supply. This command shall return a std output which represents the value of the current (float in the unit of [A]). For example, when I = 5.2A, `measI_cmd` returns std output = `5.2`.                      |
+| `measV_cmd`           | command to measure the output voltage of the power supply. This command shall return a std output which represents the value of the voltage (float in the unit of [V]). For example, when V = 1.8V, `measV_cmd` returns std output = `1.8`.                      |
+| `n_try`               | number of re-tries in case the script fails to read from the power supply                                                                                                                                                                                        |
+| `checkTarget_timeout` | after each `set_cmd` call, `measI_cmd` is called to check if the target is reached, if not after `checkTarget_timeout` (in sec.), an exception is raised                                                                                                         |
+| `success_code`        | exit status that indicates success. The default is 0.                                                                                                                                                                                                            |
 
 ### high_voltage
 
@@ -179,6 +180,36 @@ the following:
     sys.exit(1)
     ```
 
+### LLS interlock
+
+The `lls_interlock` block specifies the path and the commands for reading
+information from the interlock system in a LLS setup. Always one module in a
+serial powering chain is connected directly to the interlock system to read the
+module NTC.
+
+**Configuration settings**
+
+| Name                            | Description                                                                                                                                                                                                                                                                                                                                                                     |
+| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `run_dir`                       | path (relative or absolute) to the directory where `lls_interlock` commands should be run                                                                                                                                                                                                                                                                                       |
+| `get_interlock_temperature_cmd` | command to read a temperature that is used as an input into the interlock system. This can be e.g. a module NTC from the interlock module of a serial powering chain. The command returns a std output which represents the value of measured temperature (float in the unit of [C]). For example: when T = 36.2C, `get_interlock_temperature_cmd` returns std output = `36.2`. |
+| `n_try`                         | number of re-tries in case the script fails to read from the interlock system                                                                                                                                                                                                                                                                                                   |
+| `success_code`                  | exit status that indicates success. The default is 0.                                                                                                                                                                                                                                                                                                                           |
+
+### MOPS
+
+The `mops_monitoring` block specifies the path and the commands for reading
+monitoring information from a MOPS chip
+
+**Configuration settings**
+
+| Name                                | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `run_dir`                           | path (relative or absolute) to the directory where `mops_monitoring` commands should be run                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `get_converted_adc_measurement_cmd` | command to measure temperature or voltage from the MOPS. Since several MOPS chips can be available in the setup, `{mops-id}` can be passed to the command, identifying the MOPS chip. The `{ch-id}` parameter is used to specify the ADC channel that is read. The command returns a std output which represents the ADC value for the specified channel converted into the measured temperature (float in the unit of [C]) or voltage (float in the unit of [V]). For example: when T = 36.2C, `get_converted_adc_measurement_cmd` returns std output = `36.2`. Note: When using an emulator, one can provide a `-C` flag for the temperature measurement or a `-V` flag for the voltage measurement (passed as the `{unit}` parameter). |
+| `n_try`                             | number of re-tries in case the script fails to read from the MOPS                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `success_code`                      | exit status that indicates success. The default is 0.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+
 ## Measurement Configuration
 
 ### tasks

{module_qc_tools-2.7.1 → module_qc_tools-2.9.0}/docs/history.md

@@ -16,6 +16,52 @@ and this project adheres to
 
 **_Fixed:_**
 
+## [2.9.0](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.9.0) - 2006-07-13 ## {: #mqt-v2.9.0 }
+
+**_Changed:_**
+
+- Update measurement times with current versions (!285)
+
+**_Added:_**
+
+- Add evaporatorPosition information to connectivity file and rename some fields
+  (!286)
+- HV group IV measure (!284)
+
+**_Fixed:_**
+
+- Remove writable-check for measuremnt config (!289)
+
+## [2.8.0](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.8.0) - 2006-03-06 ## {: #mqt-v2.8.0 }
+
+**_Added:_**
+
+- add checks into `IV_MEASURE` (!282)
+  - warning if measured points less than expected
+  - progress lock to protect from mixing progress output and measured values
+  - read current when HV not reached to trigger Keithley autorange - closes #177
+- Power supply emulator update (!283)
+- Add MOPS hardware class (!280)
+- Add LLS interlock hardware class (!281)
+- Allow sending channel identifier to power supply for fine-grained channel
+  selection (!275)
+- OB Cell Thermal performance measurement (!227)
+
+  !!! important
+
+        Requires module-qc-data-tools >= v1.5.0rc1,
+
+**_Fixed:_**
+
+- Upgrade versions of pre-commit hooks (!279)
+- fix CI (PC903 and PP304) (!273)
+
+## [2.7.1](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.7.1) - 2025-10-30 ## {: #mqt-v2.7.1 }
+
+**_Changed:_**
+
+- reverted file lock related changes in !265 and !270 (!271)
+
 ## [2.7.0](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.7.0) - 2025-10-29 ## {: #mqt-v2.7.0 }
 
 **_Changed:_**
@@ -36,6 +82,8 @@ and this project adheres to
     `mqt measurement sldo -c <hw config> -o <output dir> --npoints <int>`
   - a pipeline test `test_measurement_one_point_SLDO` was also added in
     `test_emulator.py` to check the implementation
+  - add fcntl capability to lock before calling yarr commands simultaneously
+    (!265)
 
 **_Fixed:_**
 

{module_qc_tools-2.7.1 → module_qc_tools-2.9.0}/docs/install.md

@@ -94,7 +94,7 @@ package.
 $ python -m venv venv
 $ source venv/bin/activate
 $ python -m pip install -U pip
-$ python -m pip install -U pip module-qc-tools==2.7.1
+$ python -m pip install -U pip module-qc-tools==2.9.0
 ```
 
 ### via uv
@@ -103,7 +103,7 @@ $ python -m pip install -U pip module-qc-tools==2.7.1
 $ python -m venv venv
 $ source venv/bin/activate
 $ python -m pip install uv
-$ uv pip install module-qc-tools==2.7.1
+$ uv pip install module-qc-tools==2.9.0
 ```
 
 # Usage

{module_qc_tools-2.7.1 → module_qc_tools-2.9.0}/docs/measurements.md

@@ -19,42 +19,44 @@ modules to be tested are already powered on.
 ### Time Estimates
 
 The following were measured using an old Keithley multimeter with
-[v2.4.2](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.4.2)
-running `run-full-qc`. The analysis includes uploading to localDB and
-downloading the results.
+[mqt v2.8.0](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.8.0)
+running `run-full-qc` with YARR v1.5.6. The analysis includes uploading to
+localDB v2.8.2 and downloading the results from a standalone database machine on
+the same network.
 
 | Measurement                | Duration (hh:mm:ss) |
 | -------------------------- | ------------------- |
 | update k-shunt             | 00:00:01            |
 | eye diagram                | 00:00:05            |
-| core column scan           | 00:00:27            |
-| **ADC calib**              | **00:02:32**        |
-| analysis                   | 00:00:09            |
+| core column scan           | 00:00:29            |
+| **ADC calib**              | **00:01:32**        |
+| analysis                   | 00:00:16            |
 | update chip config         | 00:00:04            |
-| **Analog Readback**        | **00:30:47**        |
-| analysis                   | 00:00:14            |
+| **Analog Readback**        | **00:30:56**        |
+| analysis                   | 00:00:22            |
 | update chip config         | 00:00:04            |
-| **SLDO VI**                | **00:19:30**        |
-| analysis                   | 00:00:12            |
+| eye diagram                | 00:00:05            |
+| **SLDO VI**                | **00:10:45**        |
+| analysis                   | 00:00:16            |
 | update chip config         | 00:00:02            |
-| **Vcal calib**             | **00:05:47**        |
-| analysis                   | 00:00:10            |
-| update chip config         | 00:00:04            |
-| **Injection Cap.**         | **00:02:29**        |
-| analysis                   | 00:00:09            |
-| update chip config         | 00:00:04            |
-| **LP Mode**                | **00:06:51**        |
-| analysis                   | 00:00:09            |
-| update chip config         | 00:00:01            |
-| **DATA_TRANSMISSION**      | **00:00:35**        |
-| analysis                   | 00:00:09            |
+| **Vcal calib**             | **00:02:55**        |
+| analysis                   | 00:00:13            |
+| update chip config         | 00:00:03            |
+| **Injection Cap.**         | **00:01:30**        |
+| analysis                   | 00:00:16            |
+| update chip config         | 00:00:02            |
+| **LP Mode**                | **00:01:37**        |
+| analysis                   | 00:00:08            |
+| update chip config         | 00:00:03            |
+| **DATA_TRANSMISSION**      | **00:00:31**        |
+| analysis                   | 00:00:14            |
 | update chip config         | 00:00:02            |
-| **Minimum Health Test**    | **00:06:40**        |
+| **Minimum Health Test**    | **00:07:09**        |
 | clear chip config          | 00:00:00            |
-| **Tuning**                 | **00:13:09**        |
-| **Pixel Failure Analysis** | **00:09:02**        |
+| **Tuning**                 | **00:14:26**        |
+| **Pixel Failure Analysis** | **00:09:39**        |
 | -------------------------- | ------------------- |
-| _total_                    | _01:39:29_          |
+| _total_                    | _01:24:01_          |
 
 ### Local Filesystem
 
@@ -487,3 +489,70 @@ file (i.e. '$(module-qc-tools --prefix)/configs/meas_config.json').
     ```
     measurement-LONG-TERM-STABILITY-DCS -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs/
     ```
+
+## Thermal Performance
+
+- [`mqt measurement thermal-performance`](reference/cli.md#mqt-measurement-thermal-performance)
+- [`module-qc-tools measurement thermal-performance`](reference/cli.md#mqt-measurement-thermal-performance)
+- [`measurement-THERMAL-PERFORMANCE`](reference/cli.md#mqt-measurement-thermal-performance)
+
+This adds the ability to run the thermal performance measurement
+(`task = THERMAL_PERFORMANCE`) as specified in the input configuration json file
+(i.e. '$(module-qc-tools --prefix)/configs/meas_config.json').
+
+**Configuration settings**
+
+| Name        | Description                                              |
+| ----------- | -------------------------------------------------------- |
+| `v_mux_ntc` | list of Vmux channels to be measured for ntc temperature |
+| `i_mux_ntc` | list of Imux channels to be measured for ntc temperature |
+| `v_mux_gnd` | list of Vmux channels to be measured for GND temperature |
+| `i_mux_gnd` | list of Imux channels to be measured for GND temperature |
+| `v_mux`     | list of Vmux channels to be measured                     |
+| `i_mux`     | list of Imux channels to be measured                     |
+
+??? example
+
+    ```
+    measurement-THERMAL-PERFORMANCE -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux_itkpixv2.json -m 20UPGM23xxxxxx_L2_warm.json
+    ```
+
+??? example "emulator"
+
+    ```
+    measurement-THERMAL-PERFORMANCE -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs/
+    ```
+
+## HV group IV measurement
+
+- [`mqt measurement hvgroup-iv-measure`](reference/cli.md#mqt-measurement-hvgroup-iv-measure)
+- [`module-qc-tools measurement hvgroup-iv-measure`](reference/cli.md#mqt-measurement-hvgroup-iv-measure)
+- [`measurement-HVGROUP-IV-MEASURE`](reference/cli.md#mqt-measurement-hvgroup-iv-measure)
+
+This adds the ability to run an IV measure of a group of modules biased in
+parallel within one high voltage (HV) group (`task = HVGROUP_IV_MEASURE`). The
+measurement configuration is specified in the input configuration json file
+(i.e. '$(module-qc-tools --prefix)/configs/meas_config.json'). Before the start
+of the measurement, it is assumed, that both LV and HV are turned ON for the
+modules.
+
+**Configuration settings**
+
+| Name            | Description                                                                                                           |
+| --------------- | --------------------------------------------------------------------------------------------------------------------- |
+| `v_min`         | the starting voltage of this measurement                                                                              |
+| `v_max`         | the end voltage of this measurement (**IMPORTANT:** This might need adjustment for every HV group)                    |
+| `n_points`      | how many points should be measured depending on the required voltage steps (i.e. 1V for 3D and 5V for planar modules) |
+| `settling_time` | delay in seconds between setting a bias voltage and reading the current                                               |
+
+??? example
+
+    ```
+    mqt measurement hvgroup-iv-measure --config-meas "$(module-qc-tools --prefix)/configs/meas_config.json" --config "$(module-qc-tools --prefix)/configs/hw_config_example_lls_qc_itkpixv2.json" --serial-number 20UPBVGxxxxxx --lls-connectivity path/to/connectivity.json --module-connectivity path/to/module/configs/directory --site SITE -o output/path
+    ```
+
+??? example "emulator"
+
+    ```
+    mqt measurement hvgroup-iv-measure --config "$(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json" --serial-number 20UPBVG1234567 --lls-connectivity "$(dirname "$(dirname "$(dirname "$(module-qc-tools --prefix)" )")")/tests/test_emulator/lls_connectivity_OB_preprod_longeron_M6.json" --module-connectivity "$(dirname "$(dirname "$(dirname "$(module-qc-tools --prefix)" )")")/tests/test_emulator/module_configs" --site TEST -o emulator/outputs
+    ```

{module_qc_tools-2.7.1 → module_qc_tools-2.9.0}/pyproject.toml

@@ -20,8 +20,8 @@ dependencies = [
     "tabulate",
     "pre-commit",
     "check-jsonschema",
-    "module-qc-data-tools >= 1.4.0",
-    "module-qc-database-tools >= 2.9.0",
+    "module-qc-data-tools >= 1.7.0",
+    "module-qc-database-tools >= 2.11.2",
     "requests",
     'urllib3>=1.26.20,<2; "el7.x86_64" in platform_release',
     "typer>=0.18.0",
@@ -38,7 +38,7 @@ classifiers = [
 "Homepage" = "https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools"
 "Bug Tracker" = "https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/issues"
 "Source" = "https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools"
-"Documentation" = "https://atlas-itk-pixel-mqt.docs.cern.ch/2.7/"
+"Documentation" = "https://atlas-itk-pixel-mqt.docs.cern.ch/2.9/"
 
 [project.scripts]
 module-qc-tools = "module_qc_tools.cli:app"
@@ -55,6 +55,11 @@ measurement-IV-MEASURE = "module_qc_tools.cli.IV_MEASURE:app"
 module-qc-tools-upload = "module_qc_tools.cli.upload_localdb:app"
 measurement-UNDERSHUNT-PROTECTION = "module_qc_tools.cli.UNDERSHUNT_PROTECTION:app"
 measurement-LONG-TERM-STABILITY-DCS = "module_qc_tools.cli.LONG_TERM_STABILITY_DCS:app"
+measurement-THERMAL-PERFORMANCE = "module_qc_tools.cli.THERMAL_PERFORMANCE:app"
+
+[dependency-groups]
+dev = [ { include-group = "test" } ]
+test = [ "pytest" ]
 
 [tool.hatch.version]
 source = "vcs"
@@ -207,6 +212,7 @@ messages_control.disable = [
   "design",
   "fixme",
   "line-too-long",
+  "too-many-lines",
   "wrong-import-position",
   # below are additional warnings to fix later
   "duplicate-code",
@@ -221,6 +227,7 @@ messages_control.disable = [
 ]
 
 [tool.pytest.ini_options]
+log_level = "INFO"
 minversion = "6.0"
 addopts = ["-ra", "--showlocals", "--strict-markers", "--strict-config"]
 xfail_strict = true

module_qc_tools-2.9.0/src/module_qc_tools/_version.py

@@ -0,0 +1,24 @@
+# file generated by vcs-versioning
+# don't change, don't track in version control
+from __future__ import annotations
+
+__all__ = [
+    "__version__",
+    "__version_tuple__",
+    "version",
+    "version_tuple",
+    "__commit_id__",
+    "commit_id",
+]
+
+version: str
+__version__: str
+__version_tuple__: tuple[int | str, ...]
+version_tuple: tuple[int | str, ...]
+commit_id: str | None
+__commit_id__: str | None
+
+__version__ = version = '2.9.0'
+__version_tuple__ = version_tuple = (2, 9, 0)
+
+__commit_id__ = commit_id = None