<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Sent from my iPhone</div><div><br>Begin forwarded message:<br><br></div><blockquote type="cite"><div><b>From:</b> Raffaella De Vita <<a href="mailto:Raffaella.Devita@ge.infn.it">Raffaella.Devita@ge.infn.it</a>><br><b>Date:</b> September 10, 2016 at 06:24:11 EDT<br><b>To:</b> Franck Sabatie <<a href="mailto:fsabatie@cea.fr">fsabatie@cea.fr</a>>, Paul Stoler <<a href="mailto:stolep@rpi.edu">stolep@rpi.edu</a>>, Harut Avagyan <<a href="mailto:avakian@jlab.org">avakian@jlab.org</a>>, Ralf Gothe <<a href="mailto:gothe@sc.edu">gothe@sc.edu</a>>, Marco Battaglieri <<a href="mailto:battaglieri@ge.infn.it">battaglieri@ge.infn.it</a>>, Pawel Nadel-Turonski <<a href="mailto:turonski@jlab.org">turonski@jlab.org</a>>, Christian Weiss <<a href="mailto:weiss@jlab.org">weiss@jlab.org</a>>, "Daniel S. Carman" <<a href="mailto:carman@jlab.org">carman@jlab.org</a>>, Marco Mirazita <<a href="mailto:Marco.Mirazita@lnf.infn.it">Marco.Mirazita@lnf.infn.it</a>>, Silvia Pisano <<a href="mailto:pisanos@jlab.org">pisanos@jlab.org</a>>, Lei Guo <<a href="mailto:lguo@jlab.org">lguo@jlab.org</a>><br><b>Cc:</b> Sebastian Kuhn <<a href="mailto:kuhn@jlab.org">kuhn@jlab.org</a>>, Veronique Ziegler <<a href="mailto:ziegler@jlab.org">ziegler@jlab.org</a>>, Cole Smith <<a href="mailto:lcsmith@jlab.org">lcsmith@jlab.org</a>>, Derek Glazier <<a href="mailto:dglazier@ph.ed.ac.uk">dglazier@ph.ed.ac.uk</a>>, Jerry Gilfoyle <<a href="mailto:ggilfoyl@richmond.edu">ggilfoyl@richmond.edu</a>>, Latifa Elouadrhirs <<a href="mailto:latifa@jlab.org">latifa@jlab.org</a>><br><b>Subject:</b> <b>request of information for Run_group A</b><br><br></div></blockquote><blockquote type="cite"><div><span>Dear All,</span><br><span>the CLAS Coordinating Committee has appointed an Ad-Hoc committee to develop answers to the questions listed in the charge included below. The purpose of this initiative is to understand where the Collaboration should be focusing efforts in preparation for the first experiment, especially in the area of software development.</span><br><span>As members of this ad-hoc committee, we are in the process of gathering relevant information to help us in this task and we are contacting you as contact persons of the Run-Group A experiments.</span><br><span>The information we would like receive from you concerns how you plan to organize and contribute to the analysis of the first experiment data and is summarized in the following questions:</span><br><span>- has your group identified the most promising physics (“favorite reaction”) for a first, speedy publication after the conclusion of the first run of RG A? (which reaction?)</span><br><span>- how you plan to organize the analysis of your favorite reaction in terms of analysis software development, algorithms development, simulations, ... ?</span><br><span>- what manpower do you plan to involve and how you plan to coordinate it? How many people within your group are presently working on this? Who?</span><br><span>- what do you expect the CLAS12 reconstruction to provide in terms of data format and event/particle related information (4-vectors, pid, ...)</span><br><span>- are you or your collaborators using CLAS12 simulation, reconstruction or common tools software to study your preferred reaction at the present time?</span><br><span></span><br><span>We have been asked to provide a response to the charge before the next Collaboration meeting that will take place in the first week of November and for this reason, we would like to receive your input in a week from now, possibly before our next meeting that will take place on Friday 9/16. Please circulate these questions to the other spokespersons/leaders within your group to collect relevant information from them.</span><br><span></span><br><span>Thank you in advance for your help.</span><br><span>Best regards,</span><br><span> Cole</span><br><span> Derek</span><br><span> Raffaella</span><br><span> Sebastian</span><br><span> Veronique</span><br><span></span><br><span></span><br><span></span><br><span></span><br><span>------------</span><br><span>ad hoc committee on Common Tools</span><br><span></span><br><span>Raffaella De Vita <a href="mailto:devita@ge.infn.it">devita@ge.infn.it</a> (chair)</span><br><span>Cole Smith <a href="mailto:lcsmith@jlab.org">lcsmith@jlab.org</a></span><br><span>Veronique Ziegler <a href="mailto:ziegler@jlab.org">ziegler@jlab.org</a></span><br><span>Sebastian Kuhns <a href="mailto:kuhn@odu.edu">kuhn@odu.edu</a></span><br><span>Derek Glazier <a href="mailto:Derek.Glazier@glasgow.ac.uk">Derek.Glazier@glasgow.ac.uk</a></span><br><span></span><br><span></span><br><span>Charge to the committee</span><br><span></span><br><span>1. What reaction channels should we focus on now for CLAS12 validation, calibration, and publication of the first papers? The identified reaction channels should allow defining and validating the procedure to extract novel physics observables, determining for example fiducial cuts, kinematic corrections, cross section normalization, etc.</span><br><span> 2. Where should we draw the line for the tasks to perform with the Common Tools over the next fourteen months preceding the engineering run? More specifically:</span><br><span></span><br><span>2.1 In the long term, what parts of the analysis procedure applied to the reconstructed data to extract physics observables from CLAS12 data should be standardized and become part of a “Common Toolset” for the collaboration to use?</span><br><span></span><br><span>2.2 How these common procedure should be integrated into software tools?</span><br><span></span><br><span>2.3 What should be the priorities in the development of Common Tools over the next fourteen months preceding the engineering run? This requires some estimate of the number of developers necessary and a realistic timeline.</span><br><span> 3. What bottlenecks exist, hardware or software, that must be overcome before the start of the engineering run?</span><br><span></span><br><span></span><br></div></blockquote></body></html>