You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, ReBACH just uses the default config file that bagger returns. It would be useful to be able to specify in the main ReBACH config which bagger config to use. This is useful to more explicitly switch between e.g. production and testing configs.
Suggested Implementation
L51 of Integration.py should explicitly pass in the config to the get_args function, as read from the main ReBACH config. If the config is not specified, then it will fall back to the current implementation (not passing in any arguments to get_args
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Description
Currently, ReBACH just uses the default config file that bagger returns. It would be useful to be able to specify in the main ReBACH config which bagger config to use. This is useful to more explicitly switch between e.g. production and testing configs.
Suggested Implementation
L51 of Integration.py should explicitly pass in the config to the
get_args
function, as read from the main ReBACH config. If the config is not specified, then it will fall back to the current implementation (not passing in any arguments toget_args
The text was updated successfully, but these errors were encountered: