Nils Homer
Nils Homer
This is from a `Pipe` task where I have `cores` set to a decimal value (ex `0.66` or `0.5` or `0.1`) for all tasks in the chain. I tried quickly...
It only updates the tasks that it creates.
1. As a developer, I would like `dagr` to stop executing as soon as any task fails. 2. As a production operator, I would like `dagr` to execute as many...
See: https://github.com/fulcrumgenomics/dagr/pull/83, Submitter: @tfenne I'd like to get rid of the `@CLP` annotation altogether. I think we could do this by having a `Program` trait in `sopt` that defines a...
See: https://github.com/fulcrumgenomics/dagr/pull/83, Submitter: @tfenne I also think that `ProgramGroup` becomes just a regular trait also that is extended with objects, e.g.: ``` scala trait ProgramGroup extends Ordered[ProgramGroup] { def name:...
Comments copied verbatim from https://github.com/fulcrumgenomics/dagr/pull/83 ### @tfenne comment ... I think that instead of `CommandLineParser` supporting `Clp` and `MainAndClp`, it should support nested `CommandLineParser`s. I haven't thought this all the...
... until you need to access their properties. See sopt/src/main/scala/dagr/sopt/cmdline/CommandLineParser.scala
Wouldn't it be nice if there was a simple web server that showed the status of all your tasks and pipelines? The first step would provide a REST API to...
Ideas: * could support with fixed-string matching * could internally translate to a regex * could use bit-masking