Common DAQ Issues

On this page, you'll find some common DAQ issues I've come across, and how to solve them.

The run number on the VNC doesn't match the run number on Grafana

Sometimes, you (or the shifter) might see that the run number on the DAQ VNC doesn't match the run number on Grafana. There are different cases where you may or may not need to take action.

Another expert is taking a DAQ run

If you see this, you don't need to do anything.

The reason this happens

Suppose another expert (for example, the CRT expert) is doing a DAQ run, and there's a current shifter run going on on a different partition. In that case, the VNC picks up the highest run number regardless of the partition. This is normal, and the VNC run number will match the Grafana run number once the expert run has finished.

Some runs aren't showing up in the database

Sometimes, you might see that there are missing runs in the run logs.

If you see this, you can run a script to fix it.

The reason this happens

If an expert is running test DAQ runs without using the GUI, and therefore the database, the runs won't be uploaded to the database.

To add these missing runs to the database, you need to run the following command, which will run the importRunHistory2ArtdaqDB.sh script:

~/cronjobs/importRunHistory2ArtdaqDB.sh

It just looks at recent run data and uploads the information to the run records database for any that were missing.

The VNC isn't responding (not a DAQ problem)

If you see this, contact the slow controls expert! This is not a DAQ expert thing to fix, as you need specific permissions (root permissions).