Data processing config for 2016 - L1T inputs

[rekovic]

On Mon, Feb 22, 2016 at 5:03 PM, Slava Krutelyov [email protected] wrote:
On 2/22/16 3:13 AM, Michael Mulhearn wrote:

Ooops, forgot to include Vladimir!

-Mike

On Mon, Feb 22, 2016 at 12:09 PM, Michael Mulhearn
[email protected] wrote:

Vladimir has agreed to handle coordinating this one as well.

For the first part, I think you can simply use our L1REPACK:Full
functionality, like this:

cmsDriver.py TEST -s L1REPACK:Full --era=Run2_2016
--filein=/store/data/Run2015D/MuonEG/RAW/v1/000/256/677/00000/80950A90-745D-E511-92FD-02163E011C5D.root

I'm assuming 80X_dataRun2_Prompt_v0 is good.

to produce a RAW data file with new Stage-2 payloads.

I didn't check what is happening inside FEDRawData after this L1REPACK.
Is the new trigger hardware coming in separate FED IDs?
If it does, this RAW file would look like it has both old and new, I guess.
I see that both the 2015 and 2016 configs run on this file OK without
obvious noise of missing products etc.

            --slava

cheers,
Mike, Vladimir

On Fri, Feb 19, 2016 at 4:29 PM, David Lange [email protected] wrote:

Hi Slava
Thanks for the connection - yes, keep me in the loop. I can help with eras either ~now (maybe) or Sunday night.

david

On Feb 19, 2016, at 4:21 PM, Slava Krutelyov [email protected] wrote:

[added David]
On 2/19/16 7:20 AM, Slava Krutelyov wrote:

Hi Mike and Pierluigi,

I think I will need the following:

• a data file with new trigger FEDs (and as much of the rest of the
  detector)
• an MC file (if available) with appropriate emulations
• cmsDriver command that you think pick up the right things for L1 for data
• cmsDriver command that does it for MC
• release version + whatever else you think is missing from that for the
  trigger software (IIRC, not all PRs are fully integrated).

The MC part is optional, but better be there.

Thank you.

I'll try to get the data processing setup with eras, but that may fall
off the list of the first things to do on MWGR#2 time scale (some fix in
the next ~24 hrs)

Cheers

         --slava

[rekovic]

@slava77 Hi, what is the status of this. Do we still need to look into it?

[slava77]

@rekovic
I think the questions are still valid.
Is this L1REPACK generating a RAW file with only new trigger data or with both the old and new.
Ideally, for testing of 2016 setup we need a RAW with only new trigger data.

I'm not sure it really matters much for operations just to be able to process data (it seems like it doesn't).
The question may be somewhat academical.