From jrsteven at jlab.org  Mon Sep 30 04:08:23 2024
From: jrsteven at jlab.org (Justin Stevens)
Date: Mon, 30 Sep 2024 08:08:23 +0000
Subject: [Halld-online] New run range 130000+ for upcoming run
Message-ID: <2EAF1914-6752-40E7-93F1-F89841F983A0@jlab.org>

Hi Sergey, All,

Since we?re approaching a new run period in January 2025 with the new FCAL-II detector configuration, can we switch the DAQ to a new set of run numbers beginning with 130000?  This will help us separate the CCDB tables which are required for the new detector configuration, etc without affecting the previous period?s data.  I frankly don?t recall how we officially defined this separation of run numbers in previous years but we?re close to test runs with FCAL-II so it seems appropriate.

-Justin


From furletov at jlab.org  Mon Sep 30 16:35:33 2024
From: furletov at jlab.org (Sergey Furletov)
Date: Mon, 30 Sep 2024 16:35:33 -0400
Subject: [Halld-online] New run range 130000+ for upcoming run
In-Reply-To: <35E5F25B-D699-49D5-A7C0-7BB791A221DF@jlab.org>
References: <35E5F25B-D699-49D5-A7C0-7BB791A221DF@jlab.org>
Message-ID: <9a5b50d8-d3fe-4330-bb6c-78249a7bfda2@jlab.org>

Hi Justin, ALl,

I switched DAQ to a new run period: RunPeriod-2025-01 and run numbers now beginning with 130000.

Sergey


On 9/30/24 04:04, Justin Stevens wrote:
> Hi Sergey, All,
> 
> Since we?re approaching a new run period in January 2025 with the new FCAL-II detector configuration, can we switch the DAQ to a new set of run numbers beginning with 130000?  This will help us separate the CCDB tables which are required for the new detector configuration, etc without affecting the previous period?s data.  I frankly don?t recall how we officially defined this separation of run numbers in previous years but we?re close to test runs with FCAL-II so it seems appropriate.
> 
> -Justin