Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide Future Use of CaloConfig and DB writing. #69

Open
mulhearn opened this issue Oct 22, 2015 · 0 comments
Open

Decide Future Use of CaloConfig and DB writing. #69

mulhearn opened this issue Oct 22, 2015 · 0 comments
Assignees
Labels

Comments

@mulhearn
Copy link
Member

Three possibilities for short-term CaloConfig:

  1. Use Era-style configuration and continue to fill CaloConfig via local config file.

  2. Write using ESProducer two version of CaloConfig to DB, one for HI, one for PP. Then, in both data and MC GTs, use the appropriate table.

  3. Start O2O'ing the actual firmware versions used online. This requires some coordination between offline and online, as currently we simply have picked two version numbers to mark PP vs HI without checking what is actually online. Probably makes sense to record all firmware used in Calo system as well.

@mulhearn mulhearn added the Todo label Nov 12, 2015
@mulhearn mulhearn changed the title [TODO] Decide Future Use of CaloConfig and DB writing. Decide Future Use of CaloConfig and DB writing. Nov 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants