Open brownd1978 opened 6 months ago
Is this fixed?
partially. I'd still like to review the infos and the info code coherently for all the products.
On Fri, Sep 20, 2024 at 7:56 AM Sophie Middleton @.***> wrote:
Is this fixed?
— Reply to this email directly, view it on GitHub https://github.com/Mu2e/REve/issues/158#issuecomment-2363927495, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAH576342F7E5IC5VHZMPDZXQZSDAVCNFSM6AAAAABHPE5672VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRTHEZDONBZGU . You are receiving this because you authored the thread.Message ID: @.***>
-- David Brown @.*** Office Phone (510) 486-7261 Lawrence Berkeley National Lab M/S 50R5008 (50-6026C) Berkeley, CA 94720
OK, I'll leave it open then
As KalSeed collections can include fits for different particle types (DeM, DeP) the PDG code needs to be printed. The helix parameters (beyond t0) are probably not of much interest to most people, maybe they could be made optional (with a fcl flag)? Reproduce with: mu2e -c REve/examples/nominal_example.fcl /pnfs/mu2e/tape/phy-sim/mcs/mu2e/CeEndpointOnSpillTriggered/MDC2020ae_best_v1_3/art/74/86/mcs.mu2e.CeEndpointOnSpillTriggered.MDC2020ae_best_v1_3.001210_00000000.art