Migrate pit 'database' files to be properly accessed instead from Condition DB
Whilst working on !363 (merged) I stumbled over an issue which was one of the monitor algorithms had a hardcoded assumption that certain 'database' text files would be available at a certain location, that only exists at the pit...
There are a few issues here
- The code would not run anywhere else (e.g. in a ci test), only at the pit.
- The information in the text files should be accessed from the Conditions DB, and not some random text files. A
Tel40
condition already exists, and if needed the information in this can be extended to include what is needed. e.g.
which is read at the C++ level by the handler
I have added a work around for point 1. in !363 (merged), the task will now still run if the text files are not found (and not fill the plots).
Point 2. though should be addressed.
Edited by Christopher Rob Jones