rMIDAS seems to immediately try to set up python after loading the library (and not at the first call to train() or complete())
We are unable to call set_python_env or decline automatic installation of rMIDAS python and because we have a self-signed certificate chain due to corporate policies, this automatic installation always fails and causes the library to not be loaded (even though we have a working conda env correctly set up).
Workaround: use option("python_custom"=TRUE) before running library(rMIDAS) pending proper fix
rMIDAS seems to immediately try to set up python after loading the library (and not at the first call to train() or complete())
We are unable to call set_python_env or decline automatic installation of rMIDAS python and because we have a self-signed certificate chain due to corporate policies, this automatic installation always fails and causes the library to not be loaded (even though we have a working conda env correctly set up).
Workaround: use option("python_custom"=TRUE) before running library(rMIDAS) pending proper fix