The calibration reports for Friday's and today's sensing function measurements have been uploaded (arx committed) to the LHO cluster under the cal account. The report directories can be viewed directly from the cluster at the links below.

Friday (06/16/2023): https://ldas-jobs.ligo-wa.caltech.edu/~cal/archive/H1/reports/20230616T161654Z/
Tuesday (06/20/2023): https://ldas-jobs.ligo-wa.caltech.edu/~cal/archive/H1/reports/20230620T234012Z/

===== Logs

Today's calibration report taken by TJ (LHO 70635)
Friday's calibration report taken by Ryan Short (LHO 70520)


===== How to commit reports to the cluster
At Jeff's request, I'm including some short instructions for committing new calibration reports to the LHO cluster's cal account. This can be done by anyone in the control room with access to a control room workstation, but, for now, this should be reserved for members of the calibration group. 

The calibration group's uncertainty estimates, which are produced hourly at each site's cluster, depend on the latest GPR results (among other things). The GPR results are bundled within every calibration report [directory] each time new measurements are taken and processed. So every time new calibration measurements are taken and a new report exists, the report and all of its associated files (i.e. the "report directory") need to be 1.) inspected by a member of the calibration group, 2.) tagged as "valid" to let the GPR routine know that it should include the measurement, and 3.) "[arx] committed" to the site cluster's cal account.

Calibration report directory tags are simply empty files located in the report's tags sub-directory. To tag a report as "[GPR] valid]" use:
touch /ligo/groups/cal/H1/reports/<report id>/tags/valid

where <report_id> should be replaced by the report's timestamp. For example, to tag today's report, which has report id 20230620T234012Z, as valid I used the command below.
touch /ligo/groups/cal/H1/reports/20230620T234012Z/tags/valid

Finally, to commit (sync or push) the new report to the site cluster, we use the arx tool:
arx commit 20230620T234012Z

The arx output will display the command's progress as it rsync's each file within the report directory to the appropriate place. Once that's done the report will visible on directly on the site cluster at ldas-jobs.ligo-[w,l]a.caltech.edu/~cal/archive/[H,L]1/reports/<report id>.