module-qc-tools 2.2.8__tar.gz → 2.4.0__tar.gz

{module_qc_tools-2.2.8 → module_qc_tools-2.4.0}/PKG-INFO

@@ -1,11 +1,11 @@
 Metadata-Version: 2.4
 Name: module_qc_tools
-Version: 2.2.8
+Version: 2.4.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.2/
+Project-URL: Documentation, https://atlas-itk-pixel-mqt.docs.cern.ch/2.4/
 Author-email: Jay Chan <jay.chan@cern.ch>
 Maintainer-email: Giordon Stark <gstark@cern.ch>
 License: Copyright (c) 2018 ATLAS ITk Pixel Modules
@@ -34,17 +34,18 @@ Classifier: Programming Language :: Python :: 3
 Requires-Python: >=3.7
 Requires-Dist: check-jsonschema
 Requires-Dist: importlib-resources; python_version < '3.9'
-Requires-Dist: module-qc-data-tools>=1.0.22
+Requires-Dist: module-qc-data-tools>=1.0.23
+Requires-Dist: module-qc-database-tools>=2.5.0rc0
 Requires-Dist: numpy
 Requires-Dist: pre-commit
 Requires-Dist: requests
 Requires-Dist: rich
 Requires-Dist: tabulate
 Requires-Dist: typer>=0.9.0
-Requires-Dist: urllib3<2,>=1.26.11; 'el7.x86_64' in platform_release
+Requires-Dist: urllib3<2,>=1.26.20; 'el7.x86_64' in platform_release
 Description-Content-Type: text/markdown
 
-# module-qc-tools v2.2.8
+# module-qc-tools v2.4.0
 
 A general python tool for running ITkPixV1.1 and ITkPixV2 module QC tests
 

{module_qc_tools-2.2.8 → module_qc_tools-2.4.0}/README.md

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

{module_qc_tools-2.2.8 → module_qc_tools-2.4.0}/docs/config.md

@@ -7,23 +7,33 @@ table tr td:first-of-type {
 
 # Configuration and external commands
 
-All the configuration/settings are defined in a single json file. The layer
-information needed for the different power settings is extracted from the
-module's serial number. Examples are provided in
-`$(module-qc-tools --prefix)/configs/`:
+All the configuration/settings are defined in two json files: one for the
+hardware and one for the measurements. The hardware config is specific to the
+site and needs to be modified, but the default measurement config should not
+modified when running standard module QC. Examples are provided in
+`$(module-qc-tools --prefix)/configs/`, such as:
 
-- `example_merged_vmux.json`
-- `example_merged_vmux_itkpixv2.json`
-- `example_separate_vmux.json`
+- `hw_config_example_merged_vmux_itkpixv2.json`
+- `meas_config.json`
 
 !!! note
 
-    the only difference between the normal config and the `_itkpixv2.json` lies in the paths for the chip-specific `lpm_digitalscan` and `read_ringosc_exe`. For more info see below.
+    There are 4 example hardware configs for the different combinations of V1 or V2 modules and a merged or separate VMUX:
+
+    - `hw_config_example_merged_vmux_itkpixv2.json`
+    - `hw_config_example_merged_vmux_v1.json`
+    - `hw_config_example_separate_vmux_itkpixv2.json`
+    - `hw_config_example_separate_vmux_v1.json`
+
+    The only difference between the `_v1.json` hw_config and the `_itkpixv2.json` lies in the paths for the chip-specific `lpm_digitalscan` and `read_ringosc_exe`. For more info see below.
 
 ??? abstract "reference json configuration"
 
-    ```json title="$(module-qc-tools --prefix)/configs/example_merged_vmux.json"
-    --8<-- "example_merged_vmux.json"
+    ```json title="$(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux_itkpixv2.json"
+    --8<-- "hw_config_example_merged_vmux_itkpixv2.json"
+    ```
+    ```json title="$(module-qc-tools --prefix)/configs/meas_config.json"
+    --8<-- "meas_config.json"
     ```
 
 The major blocks (e.g. `yarr`, `power_supply`, `multimeter`, `ntc`) correspond
@@ -33,28 +43,31 @@ following sections. The `task` block specifies the settings of each scan
 performed by the scripts, and will be explained in
 [measurements](measurements.md).
 
-## yarr
+## Hardware Configuration
+
+### yarr
 
 The `yarr` block specifies the path to the `YARR` repository as well as the
 corresponding YARR configuration files.
 
 **Configuration settings**
 
-| Name                 | Description                                                                                                                                                                                                                         |
-| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `run_dir`            | path (relative or absolute) to the directory where `YARR` commands should be run                                                                                                                                                    |
-| `controller`         | path (relative to `run_dir` or absolute) to the controller file                                                                                                                                                                     |
-| `scanConsole_exe`    | path (relative to `run_dir` or absolute) to the `scanConsole` executable                                                                                                                                                            |
-| `write_register_exe` | path (relative to `run_dir` or absolute) to the `write_register` executable                                                                                                                                                         |
-| `read_register_exe`  | path (relative to `run_dir` or absolute) to the `read_register` executable                                                                                                                                                          |
-| `read_adc_exe`       | path (relative to `run_dir` or absolute) to the `read_adc` executable                                                                                                                                                               |
-| `switchLPM_exe`      | path (relative to `run_dir` or absolute) to the `switchLPM` executable                                                                                                                                                              |
-| `lpm_digitalscan`    | path (relative to `run_dir` or absolute) to the low-power mode digital scan in YARR; for ITkPix v2, make sure that the path points to the correct scan config directory, e.g. `"configs/scans/itkpixv2/lpm_digitalscan.json"`       |
-| `read_ringosc_exe`   | path (relative to `run_dir` or absolute) to the `Rd53bReadRingosc` or `Itkpixv2ReadRingosc` executable in YARR; for ITkPix v2, make sure the path points to the executable for the correct chip, e.g. `"./bin/Itkpixv2ReadRingosc"` |
-| `eyeDiagram_exe`     | path (relative to `run_dir` or absolute) to the `eyeDiagram` executable in YARR                                                                                                                                                     |
-| `success_code`       | exit status that indicates success. The default is 0 besides `configure`, which has exit status 1 for success. The user do not need to set the `success_code` as the default in QC software is synchronized with YARR.              |
-
-## power_supply
+| Name                     | Description                                                                                                                                                                                                                         |
+| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `run_dir`                | path (relative or absolute) to the directory where `YARR` commands should be run                                                                                                                                                    |
+| `controller`             | path (relative to `run_dir` or absolute) to the controller file                                                                                                                                                                     |
+| `scanConsole_exe`        | path (relative to `run_dir` or absolute) to the `scanConsole` executable                                                                                                                                                            |
+| `write_register_exe`     | path (relative to `run_dir` or absolute) to the `write_register` executable                                                                                                                                                         |
+| `read_register_exe`      | path (relative to `run_dir` or absolute) to the `read_register` executable                                                                                                                                                          |
+| `read_adc_exe`           | path (relative to `run_dir` or absolute) to the `read_adc` executable                                                                                                                                                               |
+| `switchLPM_exe`          | path (relative to `run_dir` or absolute) to the `switchLPM` executable                                                                                                                                                              |
+| `lpm_digitalscan`        | path (relative to `run_dir` or absolute) to the low-power mode digital scan in YARR; for ITkPix v2, make sure that the path points to the correct scan config directory, e.g. `"configs/scans/itkpixv2/lpm_digitalscan.json"`       |
+| `read_ringosc_exe`       | path (relative to `run_dir` or absolute) to the `Rd53bReadRingosc` or `Itkpixv2ReadRingosc` executable in YARR; for ITkPix v2, make sure the path points to the executable for the correct chip, e.g. `"./bin/Itkpixv2ReadRingosc"` |
+| `eyeDiagram_exe`         | path (relative to `run_dir` or absolute) to the `eyeDiagram` executable in YARR                                                                                                                                                     |
+| `"dataMergingCheck_exe"` | path (relative to `run_dir` or absolute) to the `dataMergingCheck` executable in YARR                                                                                                                                               |
+| `success_code`           | exit status that indicates success. The default is 0 besides `configure`, which has exit status 1 for success. The user do not need to set the `success_code` as the default in QC software is synchronized with YARR.              |
+
+### power_supply
 
 The `power_supply` block specifies the path and the commands for handling the
 low voltage power supply
@@ -75,7 +88,7 @@ low voltage 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
+### high_voltage
 
 Similar to the `power_supply` block, the `high_voltage` block specifies the path
 and the commands for handling the high voltage power supply needed for leakage
@@ -90,7 +103,7 @@ current vs. bias voltage (IV) measurements.
 | `polarity`            | indicator if normal polarity (default 1) or reverse polarity (-1) is used. Can also take a command that returns a value, e.g. `"polarity": "echo 1"`. For power supplies that accept and output both positive and negative values of the bias voltage, the polarity is `1`. For power supplies that only accept and output a single polarity, this setting is `-1` and the wiring should be adapted accordingly. |
 | `checkTarget_timeout` | after each `set_cmd` call, `measV_cmd` is called to check if the target is reached, if not after `checkTarget_timeout` (in sec.), an exception is raised                                                                                                                                                                                                                                                         |
 
-## multimeter
+### multimeter
 
 The `multimeter` block specifies the path and the commands for handling the
 multimeter
@@ -104,7 +117,7 @@ multimeter
 | `n_try`        | number of re-tries in case the script fails to read from the multimeter                                                                                                                                                                                                                                                                         |
 | `success_code` | exit status that indicates success. The default is 0.                                                                                                                                                                                                                                                                                           |
 
-## ntc
+### ntc
 
 The `ntc` block specifies the path and the commands for handling the NTC
 
@@ -117,7 +130,9 @@ The `ntc` block specifies the path and the commands for handling the NTC
 | `n_try`        | number of re-tries in case the script fails to read from the ntc                                                                                                                                                                    |
 | `success_code` | exit status that indicates success. The default is 0.                                                                                                                                                                               |
 
-## tasks
+## Measurement Configuration
+
+### tasks
 
 The `tasks` block starts with the `GENERAL` section that specifies the
 layer-dependent power settings:

{module_qc_tools-2.2.8 → module_qc_tools-2.4.0}/docs/history.md

@@ -16,6 +16,52 @@ and this project adheres to
 
 **_Fixed:_**
 
+## [2.4.0](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.4.0) - 2025-03-11 ## {: #mqt-v2.4.0 }
+
+**_Changed:_**
+
+- reduce number of steps in VCAL calibration (!215)
+- increase voltage compliance during SLDO scan (!219)
+- improve compatibility of mqt with Felix (!186)
+
+**_Added:_**
+
+- add BOM information to output of SLDO, LP and ADC calibration (!220)
+- add ability to enable/disable LPM on targeted TX channels (!207)
+- add data merging substest to data transmission test (!218)
+- add Iref trim information to output of the AR test (!221)
+- add protection when ramping HV down (!211)
+- CLI to retrieve input current based on chip version (!210)
+
+**_Fixed:_**
+
+- fix write register issue when running with separate vmux (!208)
+- fixed number of points in SLDO (!213)
+
+## [2.3.0](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.3.0) - 2024-07-12 ## {: #mqt-v2.3.0 }
+
+**_Changed:_**
+
+**_Added:_**
+
+**_Fixed:_**
+
+## [2.2.8](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.2.8) - 2024-12-17 ## {: #mqt-v2.2.8 }
+
+**_Changed:_**
+
+**_Added:_**
+
+**_Fixed:_**
+
+## [2.2.7](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.2.7) - 2024-10-03 ## {: #mqt-v2.2.7 }
+
+**_Changed:_**
+
+**_Added:_**
+
+**_Fixed:_**
+
 ## [2.2.6](https://gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools/-/tags/v2.2.6) - 2024-07-12 ## {: #mqt-v2.2.6 }
 
 **_Changed:_**

{module_qc_tools-2.2.8 → module_qc_tools-2.4.0}/docs/install.md

@@ -92,7 +92,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.2.8
+$ python -m pip install -U pip module-qc-tools==2.4.0
 ```
 
 ### via uv
@@ -101,7 +101,7 @@ $ python -m pip install -U pip module-qc-tools==2.2.8
 $ python -m venv venv
 $ source venv/bin/activate
 $ python -m pip install uv
-$ uv pip install module-qc-tools==2.2.8
+$ uv pip install module-qc-tools==2.4.0
 ```
 
 # Usage

{module_qc_tools-2.2.8 → module_qc_tools-2.4.0}/docs/measurements.md

@@ -18,15 +18,16 @@ modules to be tested are already powered on.
 
 ### Time Estimates
 
-| Measurement     | Duration |
-| --------------- | -------- |
-| ADC calib       | 00:02:12 |
-| Analog Readback | 00:18:27 |
-| SLDO VI         | 00:08:45 |
-| Vcal calib      | 00:04:50 |
-| Injection Cap.  | 00:00:50 |
-| LP Mode         | 00:00:53 |
-| OVP             | 00:00:27 |
+| Measurement       | Duration |
+| ----------------- | -------- |
+| ADC calib         | 00:02:12 |
+| Analog Readback   | 00:18:27 |
+| SLDO VI           | 00:08:45 |
+| Vcal calib        | 00:04:50 |
+| Injection Cap.    | 00:00:50 |
+| LP Mode           | 00:00:53 |
+| OVP               | 00:00:27 |
+| DATA_TRANSMISSION | 00:00:26 |
 
 ### Local Filesystem
 
@@ -50,7 +51,7 @@ Measurements/
         └── ...
 ```
 
-The test-type of each measurement is the corresponding test-code used in the
+The test-type of each measurement is the corresponding test-mode used in the
 Production Data Base. The naming of each measurement script is chosen to be the
 same as the test-type. The timestamp is chosen to be the start time of the
 measurement.
@@ -95,7 +96,7 @@ Please use `mqdbt` to upload measurements to localDB.
 
 This script will test the sensor leakage current vs. reverse bias voltage
 (`task = IV_MEASURE`) as specified in the input configuration json file (i.e.
-`$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
+'$(module-qc-tools --prefix)/configs/meas_config.json').
 
 **Configuration settings**
 
@@ -110,13 +111,13 @@ This script will test the sensor leakage current vs. reverse bias voltage
 ??? example
 
     ```
-    measurement-IV-MEASURE -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_LP.json
+    measurement-IV-MEASURE -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_LP.json
     ```
 
 ??? example "emulator"
 
     ```
-    measurement-IV-MEASURE -c $(module-qc-tools --prefix)/configs/emulator_merged_vmux.json -o emulator/outputs
+    measurement-IV-MEASURE -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs
     ```
 
 ## Eye Diagram
@@ -144,8 +145,8 @@ For more information please refer to the
 - [`measurement-ADC-CALIBRATION`](reference/cli.md#mqt-measurement-adc-calibration)
 
 This script will run the ADC calibration (`task = ADC_CALIBRATION`) as specified
-in the input configuration json file (i.e.
-`$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
+in the input configuration json file (i.e. '$(module-qc-tools
+--prefix)/configs/meas_config.json').
 
 **Configuration settings**
 
@@ -158,13 +159,13 @@ in the input configuration json file (i.e.
 ??? example
 
     ```
-    measurement-ADC-CALIBRATION -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
+    measurement-ADC-CALIBRATION -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
     ```
 
 ??? example "emulator"
 
     ```
-    measurement-ADC-CALIBRATION -c $(module-qc-tools --prefix)/configs/emulator_merged_vmux.json -o emulator/outputs/
+    measurement-ADC-CALIBRATION -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs/
     ```
 
 ## Analog readback
@@ -176,9 +177,9 @@ in the input configuration json file (i.e.
 This script will measure all internal voltages available through VMUX and IMUX,
 measure the chip temperature, and measure VDDA/VDDD/ROSC vs Trim. channels. The
 scan settings are defined in the `task = ANALOG_READBACK` block of the input
-configuration file (i.e.
-`$(module-qc-tools --prefix)/configs/example_merged_vmux.json`). The NTC needs
-to be set in order to run this script, so that the temperature can be read.
+configuration file (i.e. '$(module-qc-tools
+--prefix)/configs/meas_config.json'). The NTC needs to be set in order to run
+this script, so that the temperature can be read.
 
 **Configuration settings**
 
@@ -201,13 +202,13 @@ to be set in order to run this script, so that the temperature can be read.
 ??? example
 
     ```
-    measurement-ANALOG-READBACK -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
+    measurement-ANALOG-READBACK -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
     ```
 
 ??? example "emulator"
 
     ```
-    measurement-ANALOG-READBACK -c $(module-qc-tools --prefix)/configs/emulator_merged_vmux.json -o emulator/outputs
+    measurement-ANALOG-READBACK -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs
     ```
 
 ## SLDO VI
@@ -217,8 +218,8 @@ to be set in order to run this script, so that the temperature can be read.
 - [`measurement-SLDO`](reference/cli.md#mqt-measurement-sldo)
 
 This script will run the VI scans (`task = SLDO`) as specified in the input
-configuration json file (i.e.
-`$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
+configuration json file (i.e. '$(module-qc-tools
+--prefix)/configs/meas_config.json').
 
 **Configuration settings**
 
@@ -234,13 +235,13 @@ configuration json file (i.e.
 ??? example
 
     ```
-    measurement-SLDO -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
+    measurement-SLDO -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
     ```
 
 ??? example "emulator"
 
     ```
-    measurement-SLDO -c $(module-qc-tools --prefix)/configs/emulator_merged_vmux.json -o emulator/outputs
+    measurement-SLDO -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs
     ```
 
 ## VCal Calibration
@@ -250,8 +251,8 @@ configuration json file (i.e.
 - [`measurement-VCAL-CALIBRATION`](reference/cli.md#mqt-measurement-vcal-calibration)
 
 This script will run the VCal calibration (`task = VCAL_CALIBRATION`) as
-specified in the input configuration json file (i.e.
-`$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
+specified in the input configuration json file (i.e. '$(module-qc-tools
+--prefix)/configs/meas_config.json').
 
 **Configuration settings**
 
@@ -266,13 +267,13 @@ specified in the input configuration json file (i.e.
 ??? example
 
     ```
-    measurement-VCAL-CALIBRATION -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
+    measurement-VCAL-CALIBRATION -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
     ```
 
 ??? example "emulator"
 
     ```
-    measurement-VCAL-CALIBRATION -c $(module-qc-tools --prefix)/configs/emulator_merged_vmux.json -o emulator/outputs/
+    measurement-VCAL-CALIBRATION -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs/
     ```
 
 ## Injection Capacitance
@@ -283,7 +284,7 @@ specified in the input configuration json file (i.e.
 
 This script will run the injection capacitance measurement
 (`task = INJECTION_CAPACITANCE`) as specified in the input configuration json
-file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
+file (i.e. '$(module-qc-tools --prefix)/configs/meas_config.json').
 
 **Configuration settings**
 
@@ -296,13 +297,13 @@ file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
 ??? example
 
     ```
-    measurement-INJECTION-CAPACITANCE -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
+    measurement-INJECTION-CAPACITANCE -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
     ```
 
 ??? example "emulator"
 
     ```
-    measurement-INJECTION-CAPACITANCE -c $(module-qc-tools --prefix)/configs/emulator_merged_vmux.json -o emulator/outputs/
+    measurement-INJECTION-CAPACITANCE -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs/
     ```
 
 ## Low Power Mode
@@ -312,8 +313,8 @@ file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
 - [`measurement-LP-MODE`](reference/cli.md#mqt-measurement-lp-mode)
 
 This script will run the low power mode test (`task = LP_MODE`) as specified in
-the input configuration json file (i.e.
-`$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
+the input configuration json file (i.e. '$(module-qc-tools
+--prefix)/configs/meas_config.json').
 
 **Configuration settings**
 
@@ -327,13 +328,13 @@ the input configuration json file (i.e.
 ??? example
 
     ```
-    measurement-LP-MODE -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_LP.json
+    measurement-LP-MODE -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_LP.json
     ```
 
 ??? example "emulator"
 
     ```
-    measurement-LP-MODE -c $(module-qc-tools --prefix)/configs/emulator_merged_vmux.json -o emulator/outputs/
+    measurement-LP-MODE -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs/
     ```
 
 ## Overvoltage Protection
@@ -344,7 +345,7 @@ the input configuration json file (i.e.
 
 This script will test the Overvoltage Protection (OVP)
 (`task = OVERVOLTAGE_PROTECTION`) as specified in the input configuration json
-file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
+file (i.e. '$(module-qc-tools --prefix)/configs/meas_config.json').
 
 **Configuration settings**
 
@@ -358,13 +359,13 @@ file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
 ??? example
 
     ```
-    measurement-OVERVOLTAGE-PROTECTION -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_LP.json
+    measurement-OVERVOLTAGE-PROTECTION -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_LP.json
     ```
 
 ??? example "emulator"
 
     ```
-    measurement-OVERVOLTAGE-PROTECTION -c $(module-qc-tools --prefix)/configs/emulator_merged_vmux.json -o emulator/outputs
+    measurement-OVERVOLTAGE-PROTECTION -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs
     ```
 
 ## Undershunt Protection
@@ -375,7 +376,7 @@ file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
 
 This script will test the Undershunt Protection (USP)
 (`task = UNDERSHUNT_PROTECTION`) as specified in the input configuration json
-file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
+file (i.e. '$(module-qc-tools --prefix)/configs/meas_config.json').
 
 **Configuration settings**
 
@@ -389,13 +390,13 @@ file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
 ??? example
 
     ```
-    measurement-UNDERSHUNT-PROTECTION -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_LP.json
+    measurement-UNDERSHUNT-PROTECTION -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_LP.json
     ```
 
 ??? example "emulator"
 
     ```
-    measurement-UNDERSHUNT-PROTECTION -c $(module-qc-tools --prefix)/configs/emulator_merged_vmux.json -o emulator/outputs
+    measurement-UNDERSHUNT-PROTECTION -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs
     ```
 
 ## Data Transmission
@@ -405,25 +406,26 @@ file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
 - [`measurement-DATA-TRANSMISSION`](reference/cli.md#mqt-measurement-data-transmission)
 
 This script will run the data transmission (`task = DATA_TRANSMISSION`) as
-specified in the input configuration json file (i.e.
-`$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
+specified in the input configuration json file (i.e. '$(module-qc-tools
+--prefix)/configs/meas_config.json').
 
 **Configuration settings**
 
-| Name       | Description                     |
-| ---------- | ------------------------------- |
-| `MonitorV` | list of VMUX channels to be set |
+| Name          | Description                             |
+| ------------- | --------------------------------------- |
+| `MonitorV`    | list of VMUX channels to be set         |
+| `DataMerging` | list of data merging modes to be tested |
 
 ??? example
 
     ```
-    measurement-DATA-TRANSMISSION -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
+    measurement-DATA-TRANSMISSION -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
     ```
 
 ??? example "emulator"
 
     ```
-    measurement-DATA-TRANSMISSION -c $(module-qc-tools --prefix)/configs/emulator_merged_vmux.json -o emulator/outputs/
+    measurement-DATA-TRANSMISSION -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs/
     ```
 
 ## Long-term stability DCS
@@ -434,7 +436,7 @@ specified in the input configuration json file (i.e.
 
 This adds the ability to run the long-term stability dcs measurement
 (`task = LONG_TERM_STABILITY_DCS`) as specified in the input configuration json
-file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
+file (i.e. '$(module-qc-tools --prefix)/configs/meas_config.json').
 
 **Configuration settings**
 
@@ -446,5 +448,11 @@ file (i.e. `$(module-qc-tools --prefix)/configs/example_merged_vmux.json`).
 ??? example
 
     ```
-    measurement-LONG-TERM-STABILITY-DCS -c $(module-qc-tools --prefix)/configs/example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
+    measurement-LONG-TERM-STABILITY-DCS -c $(module-qc-tools --prefix)/configs/hw_config_example_merged_vmux.json -m ~/module_data/20UPGR91301046/20UPGR91301046_L2_warm.json
+    ```
+
+??? example "emulator"
+
+    ```
+    measurement-LONG-TERM-STABILITY-DCS -c $(module-qc-tools --prefix)/configs/hw_config_emulator_merged_vmux.json -o emulator/outputs/
     ```

{module_qc_tools-2.2.8 → module_qc_tools-2.4.0}/mkdocs.yml

@@ -162,7 +162,11 @@ markdown_extensions:
       base_path:
         - docs/.snippets
         - README.md
-        - src/module_qc_tools/data/configs/example_merged_vmux.json
+        - src/module_qc_tools/data/configs/meas_config.json
+        - src/module_qc_tools/data/configs/hw_config_example_merged_vmux_itkpixv2.json
+        - src/module_qc_tools/data/configs/hw_config_example_separate_vmux_itkpixv2.json
+        - src/module_qc_tools/data/configs/hw_config_example_merged_vmux_v1.json
+        - src/module_qc_tools/data/configs/hw_config_example_separate_vmux_v1.json
       auto_append:
         - links.txt
         - abbrs.txt

{module_qc_tools-2.2.8 → module_qc_tools-2.4.0}/pyproject.toml

@@ -20,10 +20,11 @@ dependencies = [
     "tabulate",
     "pre-commit",
     "check-jsonschema",
-    "module-qc-data-tools >= 1.0.22",
+    "module-qc-data-tools >= 1.0.23",
+    "module-qc-database-tools >= 2.5.0rc0",
     'importlib_resources; python_version < "3.9"',
     "requests",
-    'urllib3>=1.26.11,<2; "el7.x86_64" in platform_release',
+    'urllib3>=1.26.20,<2; "el7.x86_64" in platform_release',
     "typer>=0.9.0",
     "rich",
 ]
@@ -37,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.2/"
+"Documentation" = "https://atlas-itk-pixel-mqt.docs.cern.ch/2.4/"
 
 [project.scripts]
 module-qc-tools = "module_qc_tools.cli:app"
@@ -47,6 +48,7 @@ emulator-write-register = "module_qc_tools.cli.hardware_emulator:run_write_regis
 emulator-read-register = "module_qc_tools.cli.hardware_emulator:run_read_register"
 emulator-read-adc = "module_qc_tools.cli.hardware_emulator:run_read_adc"
 emulator-read-ringosc = "module_qc_tools.cli.hardware_emulator:run_read_ringosc"
+emulator-data-merging-check = "module_qc_tools.cli.hardware_emulator:run_dataMergingCheck"
 emulator-eye-diagram = "module_qc_tools.cli.hardware_emulator:run_eyeDiagram"
 emulator-switch-lpm = "module_qc_tools.cli.hardware_emulator:run_switchLPM"
 emulator-control-ps = "module_qc_tools.cli.hardware_emulator:run_control_PS"

{module_qc_tools-2.2.8 → module_qc_tools-2.4.0}/src/module_qc_tools/_version.py

@@ -1,8 +1,13 @@
-# file generated by setuptools_scm
+# file generated by setuptools-scm
 # don't change, don't track in version control
+
+__all__ = ["__version__", "__version_tuple__", "version", "version_tuple"]
+
 TYPE_CHECKING = False
 if TYPE_CHECKING:
-    from typing import Tuple, Union
+    from typing import Tuple
+    from typing import Union
+
     VERSION_TUPLE = Tuple[Union[int, str], ...]
 else:
     VERSION_TUPLE = object
@@ -12,5 +17,5 @@ __version__: str
 __version_tuple__: VERSION_TUPLE
 version_tuple: VERSION_TUPLE
 
-__version__ = version = '2.2.8'
-__version_tuple__ = version_tuple = (2, 2, 8)
+__version__ = version = '2.4.0'
+__version_tuple__ = version_tuple = (2, 4, 0)