← Go back to Advanced Topics | ↑ Go to the Table of Content ↑
See here.
They are here.
See here.
We use standard CMake and you should get acquainted with this tool. In the CMakeLists.txt of your module, add the missing dependency to the command target_link_libraries
(i.e. the name of the library without "lib" and ".so".
For AliceO2 libraries see the next question.
Add the library name to the list O2_LIBRARIES_NAMES
in FindAliceO2.cmake
When running o2-qc
or other qc binaries, the system will show that the processes use 100% of the CPU. This is due to the DPL default rate for the event loop of devices with inputs.
Simply start your binary with --rate 10000
and it should solve the problem. The rate might have to be adapted to your workflow :
o2-qc-run-producer | o2-qc --config json://${QUALITYCONTROL_ROOT}/etc/basic.json --rate 10000
The easiest is to use the QCG (QC GUI). If you use the central test CCDB, you can use the central test QCG. Simply direct your browser to https://qcg-test.cern.ch.
If for some reason you don't want or can't use the QCG, the CCDB provides a web interface accessible at http://ccdb-test.cern.ch:8080/browse/.
By accessing http://ccdb-test.cern.ch:8080/truncate/path/to/folder you will delete all the objects at the given path. Careful with that please ! Don't delete data of others.
In production it will of course not be possible to do so.
← Go back to Advanced Topics | ↑ Go to the Table of Content ↑