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

Production data file and dataset name conventions don't allow heterogeneous datasets #217

Open
brownd1978 opened this issue Nov 11, 2022 · 1 comment
Assignees

Comments

@brownd1978
Copy link
Collaborator

Current Mu2e file and dataset name conventions require that the configuration fields of those match exactly. This precludes datasets formed of files that have equivalent but different configurations, ie if they were produced using different versions of the database. A more flexible dataset naming convention which allows heterogeneous files, and tools to create those in a consistent and correct manner, are needed.

@rlcee
Copy link
Collaborator

rlcee commented Nov 11, 2022

SAM dataset definitions are the obvious tool for this. Still plenty of details to work out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants