[Clas12_calcom] Upload of RGB Fall2019/Winter2020 hardware status tables

[Florian Hauenstein]

Dear Subsystem Experts,


Here are the instructions for the upload of hardware status tables for RGB Fall2019/Winter2020 run period. The details are at the end of my email as usual.
As discussed and decided in last weeks CALCOM meetings, we will have a separate table for the Fall 2019 data period (11014-11309) and the Winter 2020 period (11323-11571). Note that the run range will be from 0 to inf in the variations.

Please complete the upload of the tables (if required) for your subsystem by Friday this week (Oct 27). We will test the new tables in the following week. Let us know when you complete the work preferably with a logbook entry.

If your detector was not used during a run group, you dont have to upload anything for this rungroup.

Please let me know if you complete the task and if you have further questions.

Best,
Florian

Instructions on uploading:


  *   If status = 0 for all detector elements, you do NOT need to upload a table and keep default table (you could do of course upload a table to the variations as mentioned below).
  *   If some components are faulty i.e status > 0, define ONE table with all problematic channels which needs to be knocked-out during the run period (this can include components which are only partly problematic during a run)
     *   upload this table to CCDB with run group variation and run range from 0 to infinity (see below)
     *   RGB Fall 2019:
        *   ccdb add <name_of_table> -v rgb_fall2019 -r 0- table.txtfile
     *   RGB Winter 2020:
        *   ccdb add <name_of_table> -v rgb_spring2020 -r 0- table.txtfile


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/clas12_calcom/attachments/20231024/3996cf92/attachment.html>