ketrew
ketrew copied to clipboard
Keep Track of Experimental Workflows
Attempted to follow install instructions from the README, switched to 4.0.3, tried to install Ketrew and got the following error: ``` $ opam install ketrew =-=- Synchronising pinned packages =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=...
This is often not a big issue, but when you are sequentially submitting more than 10 complete epidisco workflows to a single server, sending them all do take some time....
Allowing easy ssh into it and debugging. This should be supported at the Ketrew level, an optional capability of each backend, I think.
It would be nice if hackery (I mean that in the kindest way @tavinathanson) like https://github.com/hammerlab/discohorts/commit/ba08d1db9d7b9e4ce14e4ca0cda319fac588c85b was not necessary
Or something a little more explanatory.
Here: https://github.com/hammerlab/ketrew/blob/master/src/lib/configuration.ml#L346-L352 when the argument `~root` (most likely from `` `In_directory "/foo/bar"``) is provided we still check `KETREW_CONFIG(URATION)`.
The pagination and filtering by job names using the web UI quickly becomes harder and harder as the number of (sometimes repetitive) job submissions get higher and higher. It would...