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

Running the CMS workload from LCG_10X #160

Open
sciaba opened this issue Jun 15, 2023 · 1 comment
Open

Running the CMS workload from LCG_10X #160

sciaba opened this issue Jun 15, 2023 · 1 comment

Comments

@sciaba
Copy link

sciaba commented Jun 15, 2023

To be able to run the workload from SWAN using Dask to scale out to HTCondor, ideally all dependencies should be satisfied by a given LCG configuration, as the remote Dask workers will have that. Would it make sense to create the minimal requirements.txt to be used on top of the latest LCG configuration (103) to enable this use case?

@matthewfeickert
Copy link
Member

Ideally all dependencies should be satisfied by a given LCG configuration

I don't think this is a reasonable thing to try to do. LCG views are (in my view) for Python a bit of a nightmare as they become environments that are not well defined in terms of requirements and fragile to build upon.

While I'm sure this is possible to do, I think it would just be painful and lead to lots of headaches compared to just fully defining the environment.

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

2 participants