-
-
Notifications
You must be signed in to change notification settings - Fork 634
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
Command line interpolations are not being evaluated lazily, leading to changed multirun behaviour #725
Comments
Here is my actual usecase: basically I have been using this functionality to couple variables, for eg, if I am running a model on 5 folds, and I want to load a pre-trained model corresponding to the specific fold, I would do something like this:
|
will take a look, for now you can use this as a possible workaround: Use a config group with this: things/model_per_fold.yaml fold_id: ???
pretrained: /checkpoint/${fold_id} and then from the command line do:
|
I'm experiencing an issue probably similar to this. Please let me know if it's better to open a separate issue for the following or if relates to the one above:
script:
if I call it like: the output is:
if I call it with multirun: the output (note the difference in the pretty print, now b is not handled lazily):
but if I have a real multirun: now b is not interpolated and not overriden:
|
I played around a bit more: i get the following error:
with just |
ok, I just realized that you have a pull request out for this already. Sorry for the noise :) |
I am working on it, the pull request is pending some deeper changes. |
Small update:
modified config.yaml:
results when called with
I circumvented this temporarily by using this in my actual code:
|
@egonuel thanks. I am not ready to push additional bugs onto this stack just yet. |
In v0.11, when I wanted to do multirun with certain parameters dependent on each other, I would do something like
and this would launch 3 jobs, with same values for param1 and param2.
With v1.0, this seems to be launching 3*3 = 9 jobs, with all possible combinations of param1 and param2. Wondering if that's expected behavior? My understanding was that the interpolations are evaluated lazily, so it should have the same behavior as in v0.11.
System information
The text was updated successfully, but these errors were encountered: