Peter Van Dyken
Peter Van Dyken
I think this feature would be quite useful, but not a priority before 1.0.
See also #109, use of a plugin like this would probably supersede any reference to those variables
I'm fine with that. AFAIK this would have no effect when using a database, but it at least creates the option. In principle snakebids could take on the reading of...
Yeah, the only thing I can think of is if you have an optional component of your workflow that's triggered by having files present. But that's a fairly rickety way...
Just wanted to note a problem with the current workaround is that one cannot easily control the order of the keys. This has come up as a problem for me...
#154 stalled because it wasn't clear what's the best way to approach this. Thinking about it now, my preferred approach would be to make `dataset_description.json` files using a rule within...
Re required arguments, I was hoping there would be some latitude here... To me, if you have to supply the input dir, that goes against the point of a rerun....
Just an idea for another way to approach this: we could do something like ```bash snakebids rerun /path/to/output [arg overrides] ``` So in this world, we'll assume snakebids is available...
Yeah, so it would do the following: 1. Check the pipeline version and snakemake version previously used and compare with the present. Error out if they differ, unless the user...
> * Set up the top-level logger in `__init__.py` (with `logging.getLogger(__name__)`) to make its existence explicit to anyone who looks there. I'm not familiar enough with the details of python...