Provide Run::isRealData() and SubRun::isRealData()
Is there some technical reason why these don't exist? Is there an experiment that wants to mix data and MC within the same run?
Otherwise, mirroring Event::isRealData(), they'd be very useful.
#1 Updated by Christopher Green over 7 years ago
- Status changed from New to Feedback
- Start date deleted (
- Experiment NOvA added
- Experiment deleted (
- SSI Package art added
- SSI Package deleted (
In the past, experiments have run data challenges with simulation events inserted into data runs, or vice versa. To be honest, providing the ability for information in two places to be inconsistent or be dealt with in different ways makes us uneasy. It would always be up to the input source to set this information, and the information would have to be obtained somewhere. Please chat to your stakeholders meeting representatives and we will discuss this issue amongst the stakeholders to attempt to obtain a consensus.
#3 Updated by Christopher Backhouse over 7 years ago
I would argue that for such a data challenge, the MC events should be labelled as data. Otherwise the analysis can (accidentally) treat them differently, which defeats the point of the challenge.
I would make setting the isData property for a run require that the constituent subruns and events matched.
I'll contact Brian and have him say something in the stakeholders meeting.