-
-
Notifications
You must be signed in to change notification settings - Fork 662
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
[Bug] output_subdir: null
does not work for multirun
#1773
Comments
output_subdir: null
does not work for multirunoutput_subdir: null
does not work for multirun
Hello @nkueng, |
output_dir is controlling the creation of the .hydra directory. |
So I guess this is more of a feature request than a bug report... |
Yes, and it's intertwined with #910 and is most likely what the author is really after. |
Thanks for the quick action! Indeed it goes along the lines of #910, but unlike stated there, there is currently no workaround to disable the |
You are correct that there is no workaround for multirun.yaml right now. Working directory management will get some attention in the next version. |
Anyways, thanks for developing such a nice tool! Even if I don't want to use the auto-generated outputs, it's heaps cool! ;) |
🐛 Bug
Description
Disabling the ouput of a
.yaml
file viahydra.output_subdir: null
works for the standard use-case but not inmultirun
. This still produces an undesiredmultirun.yaml
.Checklist
To reproduce
Following the intro tutorial should reproduce the issue with the following
conf/config.yaml
:This yields the unwanted
multirun.yaml
in directory.
.Expected Behavior
No output at all.
System information
Additional context
On a side note, the description for
output_subdir
mentionesNone
instead ofnull
.The text was updated successfully, but these errors were encountered: