FAQ

Why does the installation script take so long to run? The older one was faster.

The older installation script relied on precompiled libraries and tools being available for downloading to the target operating system, including ROOT. Since those precompiled packages are not maintained anymore, this build procedure is done by the script, which adds a considerable amount of extra time to its execution time.

Is there an installation package available for Python X.Y or ROOT X.Y.Z or DMQM/Deployment HGXXYYz?

We only support the versions you can see under Releases. If you need any other version of any package or Python, please consider creating a custom installation package or contact [email protected]. For DQM maintainers, see here.

Will ROOT need to be re-built every time I reinstall DQMGUI?

No, if you already built ROOT, and you're reinstalling DQMGUI in the same directory, you will not have to build ROOT again, and the installation script will skip this step automatically (by checking the existence of the thisroot.sh file in the location $INSTALLATION_DIR/root, by default: /data/srv/root/bin/thisroot.sh).

A ROOT rebuild is required for the following cases:

• You're deploying DQMGUI with a different Python version than the one used to build ROOT the first time.
• You're deploying a new version of ROOT.

When do I need to re-trigger the GitHub actions of this repository?

Two cases:

1. You want to create a new release, which you cannot find under Releases. This usually means that you want to change the version of the packages downloaded, e.g. DQMGUI, or DMWM's deployment (e.g. a newer HG tag).

2. You want to update an existing release (less common, probably for debugging reasons): The release you are looking for exists, but some of the packages downloaded in this release have been updated, using the same tag/reference/branch name. For example, if you want to include a development branch of DQMGUI (e.g. dev128), the DQMGUI dev128 branch may be updated, but the installation package that has been created cloned an older version of the dev128 branch.

Why are you not using the RHEL8-supplied root package?

This package is built for python3.6, making it incompatible with python3.8. Hence, we need to build it from source with python3.8.

How do I get access to the DQMGUI's python environment and/or the root executable?

Find the env.sh file inside your DQMGUI installation and source it.

To do so, run:

source $(find /data/srv/current/ -name "env.sh" | head -1)

Note

You will need to modify /data/srv/current if you chose a custom INSTALLATION_DIR during installation.