<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<h2 style="background-image: none; background-color: rgb(255, 255, 255); font-weight: normal; margin: 0px 0px 0.6em; overflow: hidden; padding-top: 0.5em; padding-bottom: 0.17em; border-bottom-width: 1px; border-bottom-style: solid; border-bottom-color: rgb(170, 170, 170); font-family: sans-serif; font-variant-ligatures: normal; orphans: 2; widows: 2; text-decoration-thickness: initial;" class="">
<span style="font-size: 12px;" class="">Hi All,</span></h2>
<div class=""><br class="">
</div>
<div class=""> Here are minutes from today’s CPP software meeting.</div>
<div class=""><br class="">
</div>
<div class=""><a href="https://halldweb.jlab.org/wiki/index.php/Π_polarizability_Software_Meeting_Mar_31,_2022" class="">https://halldweb.jlab.org/wiki/index.php/%CE%A0_polarizability_Software_Meeting_Mar_31,_2022</a></div>
<div class=""><br class="">
</div>
<div class=""><span class="mw-headline"><br class="">
</span></div>
<div class=""><span class="mw-headline">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Regards,<br class="">
-David<br class="">
<br class="">
-------------------------------------------------------------<br class="">
David Lawrence Ph.D.</div>
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Staff Scientist - - EPSCI Group Lead<br class="">
Thomas Jefferson National Accelerator Facility<br class="">
Newport News, VA<br class="">
<a href="mailto:davidl@jlab.org" class="">davidl@jlab.org</a></div>
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="">
</div>
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="">
</div>
</span></div>
<h2 style="background-image: none; background-color: rgb(255, 255, 255); font-weight: normal; margin: 0px 0px 0.6em; overflow: hidden; padding-top: 0.5em; padding-bottom: 0.17em; border-bottom-width: 1px; border-bottom-style: solid; border-bottom-color: rgb(170, 170, 170); font-size: 19.05px; font-family: sans-serif; font-variant-ligatures: normal; orphans: 2; widows: 2; text-decoration-thickness: initial;" class="">
<span class="mw-headline" id="Minutes">Minutes</span><span class="mw-editsection" style="font-size: small; margin-left: 1em; vertical-align: baseline; line-height: 1em; display: inline-block;"><span class="mw-editsection-bracket">[</span><a href="https://halldweb.jlab.org/wiki/index.php?title=%CE%A0_polarizability_Software_Meeting_Mar_31,_2022&action=edit§ion=6" title="Edit section: Minutes" style="text-decoration: none; color: rgb(0, 43, 184); background: none;" class="">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<div style="margin: 0.4em 0px 0.5em; line-height: 1.5em; font-family: sans-serif; font-size: 12.7px; font-variant-ligatures: normal; orphans: 2; widows: 2; background-color: rgb(255, 255, 255); text-decoration-thickness: initial;" class="">
Attendees: David L., Beni Z., Alex A., Simon T., Andrew S., Rory M., Ilya L.</div>
<ul style="line-height: 1.5em; list-style-type: square; margin: 0.3em 0px 0px 1.6em; padding: 0px; list-style-image: url("data:image/gif;base64,R0lGODlhBQANAIAAAGOMnP///yH5BAEAAAEALAAAAAAFAA0AAAIJjI+pu+APo4SpADs="); font-family: sans-serif; font-size: 12.7px; font-variant-ligatures: normal; orphans: 2; widows: 2; background-color: rgb(255, 255, 255); text-decoration-thickness: initial;" class="">
<li style="margin-bottom: 0.1em;" class="">Meeting schedule will be shifted by one week to allow Elton to participate since he is only working every other Thursday. We decided to skip two meetings and meet next on April 21st. Important/pressing issues can be
handled at weekly CPP meetings
<dl style="margin-top: 0.2em; margin-bottom: 0.5em;" class=""><dd style="line-height: 1.5em; margin-left: 1.6em; margin-bottom: 0.1em; margin-right: 0px;" class="">
</dd></dl>
</li><li style="margin-bottom: 0.1em;" class="">We took a look at the halld_recon repository and there was one PR for the BCAL pending. This is not CPP related. Alex said he would merge it soon.
<dl style="margin-top: 0.2em; margin-bottom: 0.5em;" class=""><dd style="line-height: 1.5em; margin-left: 1.6em; margin-bottom: 0.1em; margin-right: 0px;" class="">
</dd></dl>
</li><li style="margin-bottom: 0.1em;" class="">CTOF
<ul style="line-height: 1.5em; list-style-type: square; margin: 0.3em 0px 0px 1.6em; padding: 0px; list-style-image: url("data:image/gif;base64,R0lGODlhBQANAIAAAGOMnP///yH5BAEAAAEALAAAAAAFAA0AAAIJjI+pu+APo4SpADs=");" class="">
<li style="margin-bottom: 0.1em;" class="">Much of the code is in place, but Simon cannot test the digihits aspect yet since we have no data with raw hits. This triggered a larger discussion:
<ul style="line-height: 1.5em; margin: 0.3em 0px 0px 1.6em; padding: 0px; list-style-image: url("data:image/gif;base64,R0lGODlhBQANAIAAAGOMnP///yH5BAEAAAEALAAAAAAFAA0AAAIJjI+pu+APo4SpADs=");" class="">
<li style="margin-bottom: 0.1em;" class="">The best way to get digihits is to run the DAQ, but this cannot be done at the moment since they need a fiber optic installed in order to integrate the new crate into the trigger system. Sasha has to do this.</li><li style="margin-bottom: 0.1em;" class="">We will also need a fiber for the CTOF muon trigger. The muon trigger will use one of the TS front panel bits and will therefore show up in the fp_mask member of the trigger object. This will be useful for triggering
on cosmics in the CTOF in order to check out the readout chain. This also requires Sasha. Beni will speak with Sergey and together they will encourage Sasha to get both fibers installed soon.</li><li style="margin-bottom: 0.1em;" class="">We need the coordinates for the CTOF and FMWPC in the translation table. Beni was speaking with Justin recently on a related issue regarding the scalers. Alex noted that he and Sean had created the needed structure
for a single chamber as part of the chamber testing. Alex will contact Justin to pass on this structure on so it can be copied for the 6 layers of the full FMWPC.</li></ul>
</li><li style="margin-bottom: 0.1em;" class="">Locations of the paddles in lab coordinates are needed in order to match them with track projections. We will need to get these from Tim. Beni noted that rough numbers obtained via tape measure would likely be good
as placeholders for now. (possibly forever given the projected track resolution at the CTOF).</li></ul>
<dl style="margin-top: 0.2em; margin-bottom: 0.5em;" class=""><dd style="line-height: 1.5em; margin-left: 1.6em; margin-bottom: 0.1em; margin-right: 0px;" class="">
</dd></dl>
</li><li style="margin-bottom: 0.1em;" class="">DBeamPhoton
<ul style="line-height: 1.5em; list-style-type: square; margin: 0.3em 0px 0px 1.6em; padding: 0px; list-style-image: url("data:image/gif;base64,R0lGODlhBQANAIAAAGOMnP///yH5BAEAAAEALAAAAAAFAA0AAAIJjI+pu+APo4SpADs=");" class="">
<li style="margin-bottom: 0.1em;" class="">Elton reported to David that a recent simulation he did resulted in DBeamPhoton objects only in the (new) microscope region. This suggested that the overlapping microscope/hodoscope regions may need some special handling
in the DBeamPhoton code.</li><li style="margin-bottom: 0.1em;" class="">David reported and Alex confirmed that the current code was mostly written by people no longer involved in GlueX. After some discussion, David volunteered to look into it a bit more and report back at a future meeting
on how and who would best address making sure the code was properly working given the physical configuration change.</li></ul>
<dl style="margin-top: 0.2em; margin-bottom: 0.5em;" class=""><dd style="line-height: 1.5em; margin-left: 1.6em; margin-bottom: 0.1em; margin-right: 0px;" class="">
</dd></dl>
</li><li style="margin-bottom: 0.1em;" class="">FMWPC Timing Calibration
<ul style="line-height: 1.5em; list-style-type: square; margin: 0.3em 0px 0px 1.6em; padding: 0px; list-style-image: url("data:image/gif;base64,R0lGODlhBQANAIAAAGOMnP///yH5BAEAAAEALAAAAAAFAA0AAAIJjI+pu+APo4SpADs=");" class="">
<li style="margin-bottom: 0.1em;" class="">Alex reported that Sean was asking about timing offsets and resolution of the FMWPC.
<ul style="line-height: 1.5em; margin: 0.3em 0px 0px 1.6em; padding: 0px; list-style-image: url("data:image/gif;base64,R0lGODlhBQANAIAAAGOMnP///yH5BAEAAAEALAAAAAAFAA0AAAIJjI+pu+APo4SpADs=");" class="">
<li style="margin-bottom: 0.1em;" class="">Rory noted the hit resolution is 2-4 ns.</li><li style="margin-bottom: 0.1em;" class="">David noted that since we don't use drift times, he is likely interested in matching hits to events</li><li style="margin-bottom: 0.1em;" class="">Simon noted that the chambers can be calibrated to the leading edge.</li><li style="margin-bottom: 0.1em;" class="">Beni noted the matching will need the full range of the timing window which will be roughly 300ns.</li><li style="margin-bottom: 0.1em;" class="">Alex wrote down the relevant numbers and will communicate them to Sean.</li></ul>
</li></ul>
<dl style="margin-top: 0.2em; margin-bottom: 0.5em;" class=""><dd style="line-height: 1.5em; margin-left: 1.6em; margin-bottom: 0.1em; margin-right: 0px;" class="">
</dd></dl>
</li><li style="margin-bottom: 0.1em;" class="">David reported on the status of the DFMWPCMatchedTrack factory.
<ul style="line-height: 1.5em; list-style-type: square; margin: 0.3em 0px 0px 1.6em; padding: 0px; list-style-image: url("data:image/gif;base64,R0lGODlhBQANAIAAAGOMnP///yH5BAEAAAEALAAAAAAFAA0AAAIJjI+pu+APo4SpADs=");" class="">
<li style="margin-bottom: 0.1em;" class="">Changes were made that now use the DFMWPCCluster objects. Code has not been pushed to Github yet, but will be soon.</li><li style="margin-bottom: 0.1em;" class="">Some changes were made to DFMWPCCluster to facilitate matching. These included adding x/y min/max values in global coordinates. David later decided this was not the right way to do it and used an alternative method.
The question came up as to whether the x/y min/max members should be removed to clean up the code or be left in just in case a future use is found. It was decided the extraneous code should be removed.</li></ul>
<dl style="margin-top: 0.2em; margin-bottom: 0.5em;" class=""><dd style="line-height: 1.5em; margin-left: 1.6em; margin-bottom: 0.1em; margin-right: 0px;" class="">
</dd></dl>
</li><li style="margin-bottom: 0.1em;" class="">K+K-: Andrew reminded us of an analysis of GlueX data he reported last year that showed significant contamination of the K+K- for phi decay in the pi+pi- invariant mass spectrum in our region of interest. At the time
he explored trying to remove the K+K- events with some strategic cuts. These did not lead to a clean spectrum so more work was (and still is) needed.
<ul style="line-height: 1.5em; list-style-type: square; margin: 0.3em 0px 0px 1.6em; padding: 0px; list-style-image: url("data:image/gif;base64,R0lGODlhBQANAIAAAGOMnP///yH5BAEAAAEALAAAAAAFAA0AAAIJjI+pu+APo4SpADs=");" class="">
<li style="margin-bottom: 0.1em;" class="">Simon offered to include K+K- kinfit values in his existing class that already has e+e- and pi+pi- values.</li><li style="margin-bottom: 0.1em;" class="">Alex noted that for his exclusive rho analysis, he had success cutting on the kinfit confidence level. It was not clear if this would work for inclusive events, but it might given the heavy Pb target CPP will use.</li></ul>
<dl style="margin-top: 0.2em; margin-bottom: 0.5em;" class=""><dd style="line-height: 1.5em; margin-left: 1.6em; margin-bottom: 0.1em; margin-right: 0px;" class="">
</dd></dl>
</li><li style="margin-bottom: 0.1em;" class="">We only briefly touched on monitoring plots. Rory had sent some suggestions in an e-mail last week and David copied these into this meeting page for easy reference.
<ul style="line-height: 1.5em; list-style-type: square; margin: 0.3em 0px 0px 1.6em; padding: 0px; list-style-image: url("data:image/gif;base64,R0lGODlhBQANAIAAAGOMnP///yH5BAEAAAEALAAAAAAFAA0AAAIJjI+pu+APo4SpADs=");" class="">
<li style="margin-bottom: 0.1em;" class="">Rory noted that Elton responded to his question on the helicity frame with details on how to calculate values in it.</li><li style="margin-bottom: 0.1em;" class="">Andrew noted he has code that does transform into the helicity frame and offered to provide it for the monitoring plots.</li></ul>
</li></ul>
<h3 style="background-image: none; background-color: rgb(255, 255, 255); margin: 0px 0px 0.3em; overflow: hidden; padding-top: 0.5em; padding-bottom: 0.17em; border-bottom-style: none; font-size: 16.764px; font-family: sans-serif; font-variant-ligatures: normal; orphans: 2; widows: 2; text-decoration-thickness: initial;" class="">
<span class="mw-headline" id="Action_Items">Action Items</span><span class="mw-editsection" style="user-select: none; font-size: small; font-weight: normal; margin-left: 1em; vertical-align: baseline; line-height: 1em; display: inline-block;"><span class="mw-editsection-bracket">[</span><a href="https://halldweb.jlab.org/wiki/index.php?title=%CE%A0_polarizability_Software_Meeting_Mar_31,_2022&action=edit§ion=7" title="Edit section: Action Items" style="text-decoration: none; color: rgb(0, 43, 184); background: none;" class="">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<ul style="line-height: 1.5em; list-style-type: square; margin: 0.3em 0px 0px 1.6em; padding: 0px; list-style-image: url("data:image/gif;base64,R0lGODlhBQANAIAAAGOMnP///yH5BAEAAAEALAAAAAAFAA0AAAIJjI+pu+APo4SpADs="); font-family: sans-serif; font-size: 12.7px; font-variant-ligatures: normal; orphans: 2; widows: 2; background-color: rgb(255, 255, 255); text-decoration-thickness: initial;" class="">
<li style="margin-bottom: 0.1em;" class="">Merge in BCAL PR (Alex)</li><li style="margin-bottom: 0.1em;" class="">Contact Sergey + Sasha about installing fibers soon for CTOF+FMWPC readout (Beni)</li><li style="margin-bottom: 0.1em;" class="">Provide Justin with data structure for FMWPC addition to Translation table (Alex)</li><li style="margin-bottom: 0.1em;" class="">Add values with global coordinated of CTOF paddles to be used for matching (Simon)</li><li style="margin-bottom: 0.1em;" class="">Review DBeamPhoton code and report back on needed changes (David + Elton)</li><li style="margin-bottom: 0.1em;" class="">Finalize list of FMWPC calibration constants and create items in CCDB (Alex)</li><li style="margin-bottom: 0.1em;" class="">Add DCTOFPoint objects to DFMWPCMatchedTrack (David)</li><li style="margin-bottom: 0.1em;" class="">Provide FMWPC timing calibration numbers to Sean (Alex)</li><li style="margin-bottom: 0.1em;" class="">Remove x/y min/max from DFMWPCMatchedTrack and push changes to GitHub CPP (David)</li><li style="margin-bottom: 0.1em;" class="">Add K+K- to DEpEm factory of kinfit values (Simon)</li><li style="margin-bottom: 0.1em;" class="">Dig out helicity frame code for reuse in monitoring (Andrew)</li></ul>
<div class=""><br class="">
</div>
<br class="">
<br class="">
<br class="">
</body>
</html>