Accessing QC results from qc-async part of the QC CCDB


Looking at the qc-async “dir” in it seems that the timestamps of the validity ranges are based on the time the async QC was ran, and thus has no relationship with the time span of the corresponding (real) data. How one is supposed to access the async QC data for a given real data then ? By run number ?


Yes, by run number, or actually at least a combination of run number and pass name.

We want to start using the actualy SOR and EOR for QC object validity this year, but this is still in development.

ok. thanks. Any ETA for the [SOR,EOR] validity usage ?

Not very precise, but I aim June, maybe sooner for the new runs, but updating the old ones might take more time.