Simon Sadedin

This looks like a great start, and certainly helps to manage the issue. I have cloned / built the feature branch and will try and exercise it over the next...

Interesting that you are the first to run into this (or at least the first to report it). I guess it must be unusual for SLURM clusters to not have...

@nemartins I have just put in [a commit](https://github.com/ssadedin/bpipe/commit/eeb24e4ea2959e0415150e691aed85b172c83b0d) that I think should fix the SLURM issue at least in a basic sense. I was able to create a test cluster...

that's a very clever way to try and solve it - would be interesting to see it if you are interested to share. It could allow us to used the...

hi @Mercilena the bpipe.config file is not a configure file. If you would like to build from source, take a look at the [Developer Setup Instructions](https://docs.bpipe.org/Guides/DevelopmentSetup/). Let me know if...

Hi @L-of-IOS - the "probe mode" is a purely internal part of how bpipe works. When it is given an "exec" statement, before it really runs it, it "pretend" executes...

Hmm, I see - this indeed was re-introduced as the basis for a feature / enhancement. The enhancement enables you to queue up bpipe pipelines to run in a directory...

Hmm, unfortunately the output of the actual error isn't captured above so I can't tell if it's an installation type error (ExomeDepth not installed, working, etc) or a problem with...

I'm not sure if they are both related, but I think definitely your problems in the first case are because of some issues with capitalisation in the config. - `cn.MOPs`...

Sorry for the slow response! What's happening is that when you install it creates a `bpipe.config` file in `eval/pipeline/bpipe.config`. This seems to have gone wrong and produced a file that...