[Halld-offline] getting the right calibration in MC

[Paul Mattione]

setenv JANA_CALIB_CONTEXT "variation=mc"

Where needed, I sometimes check how many DMCThrowns are in the event.  If it's empty then it should be data.  

I don't know if this is a good idea though, at the level of applying calibration constants.  I only use this for high-level things (e.g. thrown-detected matching). 

 - Paul

----- Original Message -----
From: "Matthew Shepherd" <mashephe at indiana.edu>
To: "HallD Software Group" <HallD-Offline at jlab.org>
Sent: Monday, February 9, 2015 2:46:00 PM
Subject: [Halld-offline] getting the right calibration in MC

Hi all,

Two related questions:  one from a user standpoint and the
second from a reconstruction development standpoint.

First, how does one in general be sure to get proper calibration
when running over MC?  There is the potential for calibrations
to be applied to MC simulation that may cause problems
because the underlying quantities are not offset in a manner
that the calibration is intending to correct.  Is there a general
rule that one should use when running over MC, e.g., particular
flags to pass to CCDB?  

Second, as a developer can one detect some sort of global MC
flag and make decisions based on that?  For example, I
know there are constants in FCAL reconstruction that are
downstream of where the independent MC and data pipes
have merged.  Those constants should be different for
MC and data -- how do I detect whether a job is MC or
data and do the appropriate thing?  (Or is this forbidden
by design and I need to modify the MC stream appropriately?)

Matt

---------------------------------------------------------------------
Matthew Shepherd, Associate Professor
Department of Physics, Indiana University, Swain West 265
727 East Third Street, Bloomington, IN 47405

Office Phone:  +1 812 856 5808


_______________________________________________
Halld-offline mailing list
Halld-offline at jlab.org
https://mailman.jlab.org/mailman/listinfo/halld-offline