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

Understand what samples are needed to get to a full 200 TB #5

Closed
gordonwatts opened this issue Mar 30, 2024 · 1 comment · Fixed by #16
Closed

Understand what samples are needed to get to a full 200 TB #5

gordonwatts opened this issue Mar 30, 2024 · 1 comment · Fixed by #16
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@gordonwatts
Copy link
Member

ATLAS has this very annoying habit of deleting p-tags out from under one - especially with modern PHYSLITE samples as they are evolving so quickly. So it behoves us to get a list of samples that we can pin at Chicago.

  • List of the rucio samples that we will use below that total about 200 TB of overall data.
  • Place the samples in the README.md at the root directory.

Once this is done, then we can have UChicago pin them.

@gordonwatts gordonwatts added the enhancement New feature or request label Mar 30, 2024
@alexander-held
Copy link
Member

alexander-held commented Apr 5, 2024

We decided to go with Run-2 PHYSLITE now (mc20a/d/e), I'll put together a standard set of samples for this. We'll want to store both container names and paths to files including respective XCache instances.

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

Successfully merging a pull request may close this issue.

2 participants