From baltzell at jlab.org  Mon Jun  2 08:52:08 2025
From: baltzell at jlab.org (Nathan Baltzell)
Date: Mon, 2 Jun 2025 12:52:08 +0000
Subject: [Alert_collaboration] RG-L RC meeting today
Message-ID: <BLAPR09MB6580088AB2BF6B302AB10DE2AF62A@BLAPR09MB6580.namprd09.prod.outlook.com>

Dear All,

We'll have a RG-L RC meeting today at 11:30 in CH200.  Here's the zoom:

https://jlab-org.zoomgov.com/j/1605705819

Regards,
Nathan as RC

From mpaolone at jlab.org  Mon Jun  2 09:17:03 2025
From: mpaolone at jlab.org (mpaolone)
Date: Mon, 02 Jun 2025 07:17:03 -0600
Subject: [Alert_collaboration] ALERT software meeting,
 Monday June 2nd at 10:30am ET
Message-ID: <0ad42c3dc9116e40a9bfa347067c3b39@jlab.org>

Hi All,

We will meet today at 10:30am ET

Please use the following zoom link:
https://nmsu.zoom.us/j/9399209893

You can see meeting minutes and upload/update here:
https://clasweb.jlab.org/wiki/index.php/Meeting_link_and_pages

The agenda will be:
Updates from all groups.

Best,
-Michael

From baltzell at jlab.org  Tue Jun  3 08:57:52 2025
From: baltzell at jlab.org (Nathan Baltzell)
Date: Tue, 3 Jun 2025 12:57:52 +0000
Subject: [Alert_collaboration] RG-L RC meeting today
In-Reply-To: <BLAPR09MB6580088AB2BF6B302AB10DE2AF62A@BLAPR09MB6580.namprd09.prod.outlook.com>
References: <BLAPR09MB6580088AB2BF6B302AB10DE2AF62A@BLAPR09MB6580.namprd09.prod.outlook.com>
Message-ID: <SJ0PR09MB658956A9901B6FDA0401A988AF6DA@SJ0PR09MB6589.namprd09.prod.outlook.com>


Dear All,

We'll have an RG-L RC meeting today, 11:30 in CH200.  Topics are at the bottom of the short term schedule tab, in particular changing to D2 target (during tomorrow's MD?):

https://wiki.jlab.org/clas12-run/index.php/Run_Group_L

https://jlab-org.zoomgov.com/j/1605705819

Regards,
Nathan as RC

________________________________________
From: Nathan Baltzell
Sent: Monday, June 2, 2025 8:52 AM
To: hallb; Raphael Dupre via Alert_collaboration; Stepan Stepanyan via clas_members
Subject: RG-L RC meeting today

Dear All,

We'll have a RG-L RC meeting today at 11:30 in CH200.  Here's the zoom:

https://jlab-org.zoomgov.com/j/1605705819

Regards,
Nathan as RC

From raphael.dupre at ijclab.in2p3.fr  Tue Jun  3 11:25:05 2025
From: raphael.dupre at ijclab.in2p3.fr (Raphael Dupre)
Date: Tue, 3 Jun 2025 17:25:05 +0200 (CEST)
Subject: [Alert_collaboration] [EXTERNAL] Fwd: alert geometry in GEMC
In-Reply-To: <8C922B9F-9025-4161-A5DB-C41137EDC801@jlab.org>
References: <A76D0AB1-2A1F-4C57-A041-90635F9B4E2A@jlab.org>
 <8C922B9F-9025-4161-A5DB-C41137EDC801@jlab.org>
Message-ID: <1221957473.31591252.1748964305508.JavaMail.zimbra@ijclab.in2p3.fr>

FYI 

--- 
Rapha?l Dupr? 
Laboratoire de Physique des 2 Infinis Ir?ne Joliot-Curie 
CNRS - IN2P3 
Universit? Paris-Saclay 


De: "Maurizio Ungaro" <ungaro at jlab.org> 
?: "Raphael Dupre" <dupre at jlab.org> 
Cc: "Mathieu Ouillon" <ouillon at jlab.org>, "Whitney Armstrong" <whit at jlab.org>, "Michael Paolone" <mpaolone at nmsu.edu>, "Nathan Baltzell" <baltzell at jlab.org> 
Envoy?: Mardi 3 Juin 2025 17:16:06 
Objet: Re: alert geometry in GEMC 

Hi all, 

I updated the Alert targets code to implement real run numbers (RRR). 

The variations have been renamed, for consistency and for RRR mapping: 

alertH2 -> rgl_spring2025_H2 
alertD2 -> rgl_spring2025_D2 
alertHe -> rgl_spring2025_He 

For now I?m using run numbers 21001, 21002 and 21003 respectively but of course once the run end the RRR will come from RCDB. 

In geometry_source I added 3 gcards for the 3 variations and a parameter file that specify the target position - hardcoded at 0 for now (let me know if we should use another value), but later on that one will be coming from CCDB. 

I verified nothing changed in the actual geometry. What?s changed in practice for you: basically nothing. These changes are only relevant in preparation for RRR simulations. 
3 new gcards have been added to clas12-config dev instead of the single one we had (w/o the target specifications). 

Best, 

Mauri 



Original Name 	

New Variation 	

Z Position (mm) 	

RUN 


alertH2 	

rgl_spring2025_H2 	

0 	

21001 


alertD2 	

rgl_spring2025_D2 	

0 	

21002 


alertHe 	

rgl_spring2025_He 	

0 	

21003 








On Jun 2, 2025, at 10:07 AM, Maurizio Ungaro <ungaro at jlab.org> wrote: 

Hi all: 

I will be updating the ALERT geometry in preparation for real run number simulations. 

Are these parts always together for alert: 

- hebag 
- alertshell 
- ahdc 
- atof 

If that?s the case it?s better to have them all in one system only, called ?alert? . 
I can do that work easily. 

Another question: inside alert shell there are two additional subdirs: 

- 10Dec_JulienUpdate 
- 25Oct_TomUpdate 

They seems not to be used - let me know if I can remove them. 

Best, 
Mauri 






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/alert_collaboration/attachments/20250603/de456c7b/attachment-0001.htm>

From baltzell at jlab.org  Tue Jun  3 19:13:15 2025
From: baltzell at jlab.org (Nathan Baltzell)
Date: Tue, 3 Jun 2025 23:13:15 +0000
Subject: [Alert_collaboration] target (trigger?) change tomorrow
Message-ID: <BLAPR09MB658012F378B8CB6D19BFE7B8AF6DA@BLAPR09MB6580.namprd09.prod.outlook.com>

Dear All,

I forgot to bring this up at today's RC meeting ...

Looks like the most recent D2 data used the old rgl_inb_v4.1_200MeV trigger:

https://clasweb.jlab.org/rcdb/runs/search?runFrom=21000&runTo=&q=event_count%3E100000+and+run_start_time

I'm assuming we should start with the latest and greatest v4.3 trigger.  And ideally only adjust prescales of non-primary triggers if appropriate/necessary.  Any thoughts?

Regards,
Nathan as RC

From raphael.dupre at ijclab.in2p3.fr  Wed Jun  4 04:47:28 2025
From: raphael.dupre at ijclab.in2p3.fr (Raphael Dupre)
Date: Wed, 4 Jun 2025 10:47:28 +0200 (CEST)
Subject: [Alert_collaboration] [EXTERNAL] News and next ALERT meeting
Message-ID: <1116225615.201543.1749026848582.JavaMail.zimbra@ijclab.in2p3.fr>

Hello everyone,

First, you probably seen the announcement that the run is extended by a couple of weeks up to the third of September. This is great news and will avoid having to make difficult choices on which data to take. 

On a related matter, we still have two RC weeks open: June 25th to July 2nd and July 9th to July 16th. Please let me know if you would be available for one of these.

Finally, we will meet tomorrow at the usual time 9 am (Chicago), 10 am (Newport News), 4 pm (Paris).

Please check the wiki page for the agenda and documents to be discussed: https://clasweb.jlab.org/wiki/index.php/ALERT_Meeting_2025 

Connection link: https://urldefense.proofpoint.com/v2/url?u=https-3A__ijclab.zoom.us_j_98179063617-3Fpwd-3DNjVTaisxY1d6eTVjM25LNFlMUW9QZz09&d=DwIFaQ&c=CJqEzB1piLOyyvZjb8YUQw&r=xvIrZb1p8HoRayKD1Sz8zPzqi4-qHfiBCWqgj3oMbOQ&m=DFzPdV9YooaxV3WaLG4Hz40nc9BYv7xUdk8dSFzbjdCQ0ogWeDUB2PXBJGGtRnSS&s=1_ZaQ5OkAawJrWQ3c58FEwX-ljeZLpSgxqR2N8ATssQ&e= 

Cheers,
Raphael

---
Rapha?l Dupr?
Laboratoire de Physique des 2 Infinis Ir?ne Joliot-Curie
CNRS - IN2P3
Universit? Paris-Saclay

From baltzell at jlab.org  Wed Jun  4 06:44:24 2025
From: baltzell at jlab.org (Nathan Baltzell)
Date: Wed, 4 Jun 2025 10:44:24 +0000
Subject: [Alert_collaboration] RG-L RC meeting today at 11:30
Message-ID: <BLAPR09MB6580600924BC06190F3211A8AF6CA@BLAPR09MB6580.namprd09.prod.outlook.com>

Dear All,

We've got a few small things to do during today's maintenance day, see the short term schedule tab:

https://wiki.jlab.org/clas12-run/index.php/Run_Group_L#tab=Short_Term_Schedule

And we'll have an RC meeting at 11:30 in CH200:

https://jlab-org.zoomgov.com/j/1605705819

Regards,
Nathan as RC