orchestra issueshttps://gitlab.inria.fr/apere/orchestra/-/issues2019-10-22T14:14:06+02:00https://gitlab.inria.fr/apere/orchestra/-/issues/17Add a `search` subcommand to runaway2019-10-22T14:14:06+02:00PERE AlexandreAdd a `search` subcommand to runawayThe parasearch project will aim at implementing optimization procedure in rust. This will allow a fast(er) selection of parameters.
Since bayesian optimization is far from being a technology, I'm concerned user may want to develop thei...The parasearch project will aim at implementing optimization procedure in rust. This will allow a fast(er) selection of parameters.
Since bayesian optimization is far from being a technology, I'm concerned user may want to develop their own search logic. For this reason, I'd like to implement a new `search` subcommand in runaway. This subcomand would be used with something like:
```bash
runaway search some_cluster my_script search_script.py -- --learning_rate=[0;1] --version={'a', 'b'}
```
We would provide a search script (here `search_script.py`), along with its own parameters (here `--learning_rate=[0;1] --version={'a', 'b'}`) that would be started and executed as a child process.
I'm not yet sure about the way communicate between the runaway logic and the script logic.V0.3.0PERE AlexandrePERE Alexandrehttps://gitlab.inria.fr/apere/orchestra/-/issues/15Add structured logging2019-10-31T17:17:36+01:00PERE AlexandreAdd structured loggingWhen logging information, we don't specifically show where it happens (which remote connection, which thread, etc...).
This would help a lot in debugging the application.When logging information, we don't specifically show where it happens (which remote connection, which thread, etc...).
This would help a lot in debugging the application.V0.3.0https://gitlab.inria.fr/apere/orchestra/-/issues/5Make outputs interactive2019-08-20T14:45:29+02:00PERE AlexandreMake outputs interactiveIn runaway, stdout, stderr and ecode are copied after the execution was done.
It would be nice to be able to show stdout and stderr messages to the user as they arrive on the remote end.In runaway, stdout, stderr and ecode are copied after the execution was done.
It would be nice to be able to show stdout and stderr messages to the user as they arrive on the remote end.V0.2.0https://gitlab.inria.fr/apere/orchestra/-/issues/3Ctrl-C Handling for Runaway2019-08-08T11:41:08+02:00PERE AlexandreCtrl-C Handling for RunawayRunaway should have a proper Ctrl-C handling, that cancels the allocation on the remote host.Runaway should have a proper Ctrl-C handling, that cancels the allocation on the remote host.V0.2.0https://gitlab.inria.fr/apere/orchestra/-/issues/1Leave tar option2019-08-22T11:54:33+02:00PERE AlexandreLeave tar optionIn runaway, there is no way to check what was sent and fetched after execution.
We should have a command line argument for that.In runaway, there is no way to check what was sent and fetched after execution.
We should have a command line argument for that.V0.2.0