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

Promote non-cluster variables that have cluster dependencies #95

Closed
JamesWrigley opened this issue Sep 16, 2023 · 0 comments · Fixed by #286
Closed

Promote non-cluster variables that have cluster dependencies #95

JamesWrigley opened this issue Sep 16, 2023 · 0 comments · Fixed by #286
Labels
bug Something isn't working

Comments

@JamesWrigley
Copy link
Member

If we have a context file like this:

@Variable(cluster=True)
def foo(run):
    return 42

@Variable
def bar(run):
    return 3.14

Then both jobs will execute locally first because bar is not a cluster variable and so it pulls in foo too when DAMNIT is executing bar. What we should do instead is promote bar to being a cluster variable like we do for proc variables:

# Check for raw-data variables that depend on proc-data variables

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant