07/28/2014 pm

Attending: Adam, Nate, Joao, Ryan, Matthew, Dominick, Satish, Kirk, Gavin,

Jon not available today…
We have a chaotic dataset to deal with — difficult to match all of the configurations.

What is the advantage in baking in the time stamps to the Sim file?
—> Very simply to make sure POT scaling matches exactly.
—> Better to use POT re-weighting according to Ryan?

For simulation: should we bake in the time/run information at simulation level?

How do we mask off some of the detector in the data?
What happens if we request data for a time that isn’t in the database? Talk to Jon.
Can we do this by Run Number? Use the smallest diblock configuration.
LiveGeometry will use bad channels. Joao’s list doesn’t use Live Geometry.
—> Kirk and Joao have been discussing how to make it totally consistent.
—> Joao uses “bad channels” plus another requirement. One bad DCM makes a diblock bad.

Must be done in BadChannels so that cell hits get killed. Or CalHit?
Ryan will make sure that we are not killing much data by using the most restrictive sub run configuration.
What about POT estimation? How do we take into account the masked off data.
We now agree that we should do run-dependent MC — Run list with POT weights required.

We will follow up at next production group meeting.