[Alert_collaboration] [EXTERNAL] ALERT yaml flags

[efuchey]

Hello again Nathan, Mohammed, and all,

Thanks for the input. Based on this, I reckon that those flags are 
indeed not needed since, afaik, we will use the "distance" finding 
method for conventional track finding (I'm not even sure the other 
method works). I can try to add the change suggested by Nathan to 
determine the "simulation" flag with the existence of MC::Particle.

BTW: I had mentioned in a previous meeting that with the latest version 
of the code I did not seem to process the AHDC hits anymore - and I'm 
happy to report that I finally solved that, in part thanks to this 
conversation

Best regards,
Eric



On 2025-03-31 13:09, Nathan Baltzell wrote:
> Hello All,
> 
> One option is to get rid of the simulation flag and detect DATA vs MC
> based on whether MC::Particle or other exists.
> 
> And for the other defaults, I'd vote they should be maintained as the
> one (most) people (should) want to use for data from beam on target.
> 
> -Nathan
> 
> ________________________________________
> From: Alert_collaboration <alert_collaboration-bounces at jlab.org> on
> behalf of mhattawy--- via Alert_collaboration
> <alert_collaboration at jlab.org>
> Sent: Monday, March 31, 2025 12:08 PM
> To: efuchey
> Cc: Raffaella De Vita; alert collaboration; Mathieu Ouillon
> Subject: Re: [Alert_collaboration] [EXTERNAL] ALERT yaml flags
> 
> Hello Eric,
> Regarding
>    simulation    = false;
>    findingMethod = "distance";
> 
> They are hardcoded in the AHDCEngine. The engine must be edited to
> read them from the yam file. One has to add something like the
> following two lines in the AHDCEngine and push a merge request, and
> then we will need a new coatjava release.
>          simulation = this.getEngineConfigString("simulation");
>          findingMethod = this.getEngineConfigString("findingMethod");
> 
> Mohammad.
> 
> On Mon, Mar 31, 2025 at 11:58 AM efuchey
> <efuchey at jlab.org<mailto:efuchey at jlab.org>> wrote:
> Hello Mohammed, and all,
> 
> besides the flag for track finding suggested by Mathieu, I can think 
> of:
> * a "Simulation" boolean flag, to readout simulation files. It should 
> be
> set to 'false' by default.
> * a "FindingMethod" string flag to indicate what fitting method should
> be used for the conventional track finder. It should be set to
> 'distance' by default.
> Those are currently declared in AHDCEngine.
> https://github.com/JeffersonLab/coatjava/blob/development/reconstruction/alert/src/main/java/org/jlab/rec/service/AHDCEngine.java<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JeffersonLab_coatjava_blob_development_reconstruction_alert_src_main_java_org_jlab_rec_service_AHDCEngine.java&d=DwMFaQ&c=CJqEzB1piLOyyvZjb8YUQw&r=xvIrZb1p8HoRayKD1Sz8zPzqi4-qHfiBCWqgj3oMbOQ&m=gDCov_exuRAjDGvfx1D49aIgfSQMqds19gVBOnf_jn28sYtESSTnpdsdIeZFe3Ue&s=SrgSLvlp8vhlp01326sGK1IYa1C0t1Qcxiar-Pm4PCE&e=>
> 
> Best regards,
> Eric
> 
> On 2025-03-31 11:45, mhattawy at odu.edu<mailto:mhattawy at odu.edu> wrote:
>> Hello all,
>> 
>>     We are working on getting the yaml file ready to start looking
>> into the data once it is recorded.
>> Here you can find the draft of the current draft of the yaml file
>> 
>> /u/home/clas12-3/users/pilleux/yamls/rgl_calib.yaml
>> 
>> We need the input from the AHDC and AFOT software developers if their
>> reconstruction codes need any flags to be passed from the yaml
>> configuration file. So far, we got the feedback from Mathieu to pass
>> "Mode".
>> 
>> Mathieu, what reconstruction method should be requested,
>> AI_Track_Finding or CV_Track_Finding?
>> 
>> Best regards,
>> Mohammad.