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

records: CMS 2012 double RECO HLT provenance #2641

Closed
tiborsimko opened this issue May 29, 2019 · 0 comments · Fixed by #2644
Closed

records: CMS 2012 double RECO HLT provenance #2641

tiborsimko opened this issue May 29, 2019 · 0 comments · Fixed by #2644

Comments

@tiborsimko
Copy link
Member

Check "double provenance" for RECO HLT step for the following datasets:

This may be because DAS contains four configuration IDs, while McM contains only two.

The data curation script should give preference to McM when available when detecting configuration files.

@tiborsimko tiborsimko added this to the CMS-Q4-Updates milestone May 29, 2019
@tiborsimko tiborsimko self-assigned this May 29, 2019
tiborsimko added a commit to tiborsimko/opendata.cern.ch that referenced this issue May 29, 2019
* Updates configuration file extraction by consulting McM first and DAS second.
  Sorts configuration files alphabetically. (closes cernopendata#2641)

Signed-off-by: Tibor Simko <tibor.simko@cern.ch>
tiborsimko added a commit to tiborsimko/opendata.cern.ch that referenced this issue May 31, 2019
* Updates configuration file extraction by consulting McM first and DAS second.
  Sorts configuration files alphabetically. (closes cernopendata#2641)

Signed-off-by: Tibor Simko <tibor.simko@cern.ch>
tiborsimko added a commit to tiborsimko/opendata.cern.ch that referenced this issue May 31, 2019
* Updates configuration file extraction by consulting McM first and DAS second.
  Sorts configuration files alphabetically. (closes cernopendata#2641)

* Updates CMS Run2 datascience related MINIAODSIM files as well.
  (addresses cernopendata#2613)

Signed-off-by: Tibor Simko <tibor.simko@cern.ch>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant