[Clas12_calcom] [EXTERNAL] Re: Instructions RGF Hardware Statustable upload for data and MC

[Florian Hauenstein]

Hi Mohammad,

all important subsystems for RGF (CTOF,FTOF,DC,HTCC, LTCC, ECAL) uploaded their combined hardware status tables for MC.

Best,
Florian
________________________________
Von: Clas12_calcom <clas12_calcom-bounces at jlab.org> im Auftrag von L Smith via Clas12_calcom <clas12_calcom at jlab.org>
Gesendet: Mittwoch, 6. März 2024 12:20
An: mhattawy at odu.edu <mohammad.hattawy at gmail.com>
Cc: clas12_calcom at jlab.org <clas12_calcom at jlab.org>
Betreff: Re: [Clas12_calcom] [EXTERNAL] Re: Instructions RGF Hardware Statustable upload for data and MC

Hi Mohammad,

The ‘default’ tables were loaded on Feb. 7.

https://logbooks.jlab.org/entry/4249220

Regards,
Cole

On Mar 6, 2024, at 12:17 PM, mhattawy--- via Clas12_calcom <clas12_calcom at jlab.org> wrote:

Hello Cole,
   Thanks for the support. Can you please confirm that you have pushed the tables for real data cooking under the "default" variation.

Best regards,
Mohammad.

On Wed, Mar 6, 2024 at 12:08 PM L Smith via Clas12_calcom <clas12_calcom at jlab.org<mailto:clas12_calcom at jlab.org>> wrote:
Dear Florian,

Done.

https://logbooks.jlab.org/entry/4262096

Regards,
Cole

On Mar 5, 2024, at 11:58 PM, Florian Hauenstein via Clas12_calcom <clas12_calcom at jlab.org<mailto:clas12_calcom at jlab.org>> wrote:

Dear Subsystem Experts,

as discussed during last weeks CALCOM meeting, here are instructions to upload status tables for the RGF Spring 2020 (runs 11620-12282) and Summer 2020 (runs 12389-12951) run periods.
Tables have to be uploaded separately for data and MC.


  1.
For data cooking we will use run-by-run tables in default variation! Therefore, please upload as many tables as necessary depending on the number of hardware issues during the run and make a logbook entry for your detector. Some detector systems already completed that task during the assessment of the status tables in the last couple of weeks.
  2.
For MC we will use one table for each of the RGF run periods. This has to be done since run-by-run MC is not available yet. Please devise a suitable table for your subsystem similar to what you did for RGA/B/K pass2. Therefore, the table can have channels to be knocked-out which were only partly problematic during the run.


     The MC tables have to be uploaded in the following way. NOTE the "_mc"-variations in the commands!

  *
RGF Spring 2020:
     *
ccdb add <name_of_table> -v rgf_spring2020_mc -r 0- table.txtfile
  *
RGF Summer 2020:
     *
ccdb add <name_of_table> -v rgf_summer2020_mc -r 0- table.txtfile
  *


RGF would appreciate if you can upload the tables until Friday March 8.

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

Best,
Florian

Note: If your detector was not used during RGF, you dont have to upload anything for this rungroup.
_______________________________________________
Clas12_calcom mailing list
Clas12_calcom at jlab.org<mailto:Clas12_calcom at jlab.org>
https://mailman.jlab.org/mailman/listinfo/clas12_calcom

_______________________________________________
Clas12_calcom mailing list
Clas12_calcom at jlab.org<mailto:Clas12_calcom at jlab.org>
https://mailman.jlab.org/mailman/listinfo/clas12_calcom


--
Best regards,
Mohammad Hattawy.
_______________________________________________
Clas12_calcom mailing list
Clas12_calcom at jlab.org
https://mailman.jlab.org/mailman/listinfo/clas12_calcom

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/clas12_calcom/attachments/20240311/81584295/attachment-0001.html>