module-qc-tools 2.2.7__tar.gz → 2.3.0__tar.gz

module_qc_tools-2.3.0/.gitlab-ci.yml

@@ -0,0 +1,189 @@
+stages:
+  - autoupdate
+  - check
+  - test
+  - build
+  - deploy
+
+variables:
+  # see https://docs.gitlab.com/ee/ci/caching/#cache-python-dependencies
+  PIP_CACHE_DIR: "$CI_PROJECT_DIR/.cache/pip"
+  PRE_COMMIT_HOME: "$CI_PROJECT_DIR/.cache/pre-commit"
+
+cache:
+  paths:
+    - .cache/pip
+    - .cache/pre-commit
+    - venv/
+
+image: registry.cern.ch/docker.io/library/python:3.11-buster
+before_script:
+  # want to set up a virtualenv to cache
+  - apt-get install -y --no-install-recommends git
+  - python -V
+  - git config --global credential.helper 'cache'
+  - |
+    echo "protocol=https
+    host=gitlab.cern.ch
+    username=gitlab-ci-token
+    password=${CI_JOB_TOKEN}
+    " | git credential approve
+  - python -m venv venv
+  - source venv/bin/activate
+  - python -m pip install -U pip pipx
+  - python -m pipx ensurepath
+  - python -m pip freeze --local
+
+# NB: repo-review requires python>=3.10
+review:
+  image: registry.cern.ch/docker.io/library/python:3.10-buster
+  stage: check
+  script:
+    - pipx run 'sp-repo-review[cli]' .
+
+lint:
+  stage: check
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "push"
+  script:
+    - pipx run hatch run lint
+
+pre-commit:
+  stage: check
+  variables:
+    PRE_COMMIT_HOME: "$CI_PROJECT_DIR/.cache/pre-commit"
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "push"
+  script:
+    - pipx run pre-commit run --hook-stage manual --all-files
+  cache:
+    key:
+      files:
+        - .pre-commit-config.yaml
+    paths:
+      - .cache/pre-commit
+
+pre-commit-autoupdate:
+  stage: autoupdate
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "schedule"
+      when: always
+    - if:
+        $CI_PIPELINE_SOURCE == "push" && $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
+      when: manual
+      # manual jobs need allow_failure? https://gitlab.com/gitlab-org/gitlab/-/issues/233876
+      allow_failure: true
+  script:
+    - python -m pip install pre-commit
+    - python -m pip freeze --local
+    - ci/pre-commit-update.sh
+
+  cache:
+    key:
+      files:
+        - .pre-commit-config.yaml
+    paths:
+      - .cache/pre-commit
+
+tests:
+  stage: test
+  image: $IMAGE
+  script:
+    - git clone
+      https://gitlab-ci-token:${CI_JOB_TOKEN}@gitlab.cern.ch/atlas-itk/pixel/module/module-qc-tools
+    - pipx run hatch run +py=${PYTHON_VERSION} dev:test
+  parallel:
+    matrix:
+      - IMAGE: "registry.cern.ch/docker.io/library/python:3.8-buster"
+        PYTHON_VERSION: "3.8"
+      - IMAGE: "registry.cern.ch/docker.io/library/python:3.9-buster"
+        PYTHON_VERSION: "3.9"
+      - IMAGE: "registry.cern.ch/docker.io/library/python:3.10-buster"
+        PYTHON_VERSION: "3.10"
+      - IMAGE: "registry.cern.ch/docker.io/library/python:3.11-buster"
+        PYTHON_VERSION: "3.11"
+      - IMAGE: "registry.cern.ch/docker.io/library/python:3.12-bullseye"
+        PYTHON_VERSION: "3.12"
+
+.test:
+  image: registry.cern.ch/docker.io/library/python:3.8-buster
+  stage: test
+
+make-docs:
+  stage: test
+  image: registry.cern.ch/docker.io/library/python:3.11-bullseye
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "push"
+  script: pipx run hatch run docs:build-check
+
+package:
+  stage: build
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "push"
+  script:
+    - pipx run hatch run build-check
+  artifacts:
+    paths:
+      - dist/
+    expire_in: 1 day
+
+.deploy_package:
+  stage: deploy
+  dependencies:
+    - package
+  script:
+    - pipx run hatch run upload
+
+deploy_package_gitlab:
+  extends: .deploy_package
+  rules:
+    - if:
+        $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH && $CI_PIPELINE_SOURCE == "push"
+  variables:
+    TWINE_REPOSITORY_URL: "https://gitlab.cern.ch/api/v4/projects/${CI_PROJECT_ID}/packages/pypi"
+    TWINE_USERNAME: "gitlab-ci-token"
+    TWINE_PASSWORD: "${CI_JOB_TOKEN}"
+
+deploy_package_pypi:
+  extends: .deploy_package
+  only:
+    - tags
+  variables:
+    TWINE_REPOSITORY: pypi
+    TWINE_USERNAME: __token__
+    TWINE_PASSWORD: $PYPI_TOKEN
+
+deploy_docs_dev:
+  stage: deploy
+  resource_group: documentation
+  rules:
+    - if:
+        $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH && $CI_PIPELINE_SOURCE == "push"
+  script:
+    # the next three lines are just to commit and push pages to the project
+    - git config --global user.email
+      "project_139533_bot_52a0e9bbb1570326242e61cb6cd9d917@noreply.gitlab.cern.ch"
+    - git config --global user.name "pre-commit-ci"
+    - git remote set-url origin
+      "https://__pre-commit_ci_token:${PRE_COMMIT_CI_JOB_TOKEN}@${CI_SERVER_HOST}:${CI_SERVER_PORT}/${CI_PROJECT_PATH}.git"
+    # this is the script
+    - pipx run hatch run docs:deploy dev
+
+deploy_docs_latest:
+  stage: deploy
+  resource_group: documentation
+  only:
+    - tags
+  script:
+    # the next three lines are just to commit and push pages to the project
+    - git config --global user.email
+      "project_139533_bot_52a0e9bbb1570326242e61cb6cd9d917@noreply.gitlab.cern.ch"
+    - git config --global user.name "pre-commit-ci"
+    - git remote set-url origin
+      "https://__pre-commit_ci_token:${PRE_COMMIT_CI_JOB_TOKEN}@${CI_SERVER_HOST}:${CI_SERVER_PORT}/${CI_PROJECT_PATH}.git"
+    # this is the script
+    - VERSION=$(cut -d '.' -f 1,2 <<< "${CI_COMMIT_TAG}")
+    - IS_LATEST=$([[ "${CI_COMMIT_TAG}" == *"rc"* ]] && echo "" || echo
+      "latest")
+    - echo "Building and deploying docs for ${VERSION}"
+    - pipx run hatch run docs:deploy "${VERSION}" ${IS_LATEST:+"$IS_LATEST"}

{module_qc_tools-2.2.7 → module_qc_tools-2.3.0}/PKG-INFO

@@ -1,11 +1,11 @@
-Metadata-Version: 2.3
+Metadata-Version: 2.4
 Name: module_qc_tools
-Version: 2.2.7
+Version: 2.3.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.3/
 Author-email: Jay Chan <jay.chan@cern.ch>
 Maintainer-email: Giordon Stark <gstark@cern.ch>
 License: Copyright (c) 2018 ATLAS ITk Pixel Modules
@@ -34,7 +34,8 @@ 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.14
+Requires-Dist: module-qc-data-tools>=1.0.22
+Requires-Dist: module-qc-database-tools>=2.4.8
 Requires-Dist: numpy
 Requires-Dist: pre-commit
 Requires-Dist: requests
@@ -44,7 +45,7 @@ Requires-Dist: typer>=0.9.0
 Requires-Dist: urllib3<2,>=1.26.11; 'el7.x86_64' in platform_release
 Description-Content-Type: text/markdown
 
-# module-qc-tools v2.2.7
+# module-qc-tools v2.3.0
 
 A general python tool for running ITkPixV1.1 and ITkPixV2 module QC tests
 

{module_qc_tools-2.2.7 → module_qc_tools-2.3.0}/README.md

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

{module_qc_tools-2.2.7 → module_qc_tools-2.3.0}/docs/config.md

@@ -7,23 +7,31 @@ 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

{module_qc_tools-2.2.7 → module_qc_tools-2.3.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.7
+$ python -m pip install -U pip module-qc-tools==2.3.0
 ```
 
 ### via uv
@@ -101,7 +101,7 @@ $ python -m pip install -U pip module-qc-tools==2.2.7
 $ python -m venv venv
 $ source venv/bin/activate
 $ python -m pip install uv
-$ uv pip install module-qc-tools==2.2.7
+$ uv pip install module-qc-tools==2.3.0
 ```
 
 # Usage

{module_qc_tools-2.2.7 → module_qc_tools-2.3.0}/docs/measurements.md

@@ -50,7 +50,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 +95,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 +110,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 +144,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 +158,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 +176,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 +201,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 +217,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 +234,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 +250,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 +266,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 +283,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 +296,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 +312,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 +327,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 +344,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 +358,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 +375,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 +389,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,8 +405,8 @@ 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**
 
@@ -417,13 +417,13 @@ specified in the input configuration json file (i.e.
 ??? 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 +434,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 +446,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.7 → module_qc_tools-2.3.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.7 → module_qc_tools-2.3.0}/pyproject.toml

@@ -20,7 +20,8 @@ dependencies = [
     "tabulate",
     "pre-commit",
     "check-jsonschema",
-    "module-qc-data-tools >= 1.0.14",
+    "module-qc-data-tools >= 1.0.22",
+    "module-qc-database-tools >= 2.4.8",
     'importlib_resources; python_version < "3.9"',
     "requests",
     'urllib3>=1.26.11,<2; "el7.x86_64" in platform_release',
@@ -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.3/"
 
 [project.scripts]
 module-qc-tools = "module_qc_tools.cli:app"
@@ -110,7 +111,7 @@ dependencies = [
 test = "pytest -ra {args}"
 
 [[tool.hatch.envs.dev.matrix]]
-python = ["3.7", "3.8", "3.9", "3.10", "3.11", "pypy3.8"]
+python = ["3.7", "3.8", "3.9", "3.10", "3.11", "3.12", "pypy3.8"]
 
 [tool.hatch.envs.docs]
 template = "docs"

{module_qc_tools-2.2.7 → module_qc_tools-2.3.0}/src/module_qc_tools/_version.py

@@ -12,5 +12,5 @@ __version__: str
 __version_tuple__: VERSION_TUPLE
 version_tuple: VERSION_TUPLE
 
-__version__ = version = '2.2.7'
-__version_tuple__ = version_tuple = (2, 2, 7)
+__version__ = version = '2.3.0'
+__version_tuple__ = version_tuple = (2, 3, 0)