[Hybrid baryons] [EXTERNAL] Re: RG-K pass1 readiness review

[Francois-Xavier Girod]

I am personally surprised that the review committee felt that their first
general remark should be about what we intend to publish in the upcoming
months
As we noted during the review this question was not among the charges we
were asked to address

It is simply false that we did not discuss plans for publications. In
reality several members of RGK are leading key efforts to make the
CLAS12 First Publication a possibility at all
Although this was not a charge we proactively included in our presentation
a statement explaining that the RGK data plays a central role in the plans
for this First Publication

In addition I personally (as I am sure others in RGK) had gone through the
exercise of extrapolating how many exclusive events we should expect for
DVCS, pi0, phi, rho, and omega depending on whether we use the CD or not
We chose not to present this work precisely because it was not a charge,
and when confronted with this forgotten charge by the Committee during the
Review, we explicitly told them that we had proactively performed this
homework and that the numbers were already at their disposal
We explained how we can publish DVCS without momentum measurement in the CD
using only proton identification

The Committee should realize that this publication strategy is identical to
the neutron DVCS strategy which they evaluate as having a clear and
demonstrated plan

I am personally not interested in fighting against other run groups for
shared resources and I find it regrettable that this is the framework
presented to us by the collaboration leadership. I think we should foster
an environment of working together instead.
We should have the technical capability of cooking several runs in
parallel, if necessary by having different fair shares for different
groups.
This seems rather important given the overhead we have accumulated, we can
predict that the issue of sharing resources between run groups is not going
to decrease in the near future.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/hybrid_baryons/attachments/20200609/eda480fa/attachment.html>