pydra
pydra copied to clipboard
nipype
Pydra Dataflow Engine
Running the test suite triggers this warning (I am on a Python 3.9 environment), which might become a problem for the future release of Python 3.11. From my limitted understanding,...
My 2 cents on a minor stylistic issue, but I feel like it might be more intuitive if fields in shell-command input/output specs were defined with dictionaries rather than tuples...
Use raw string path for reporting the crash report location instead of `PosixPath` as in: `ValueError: Task core raised an error, full crash report is here: [PosixPath('...')]`
As much as we would like people to move to Pydra and help build out the ecosystem, in many cases the short path is still to augment nipype 1. I...
## Types of changes - Bug fix (non-breaking change which fixes an issue) ## Summary when output use template to create the output path and value is `False` the field...
On the line https://github.com/nipype/pydra/blob/ac06f8cc691c62e3d56e9e94ef015a675c73851f/pydra/engine/helpers_file.py#L713, any string field containing '.' is treated as a path. This precludes passing a file extension as an input to be appended on the end of...
Hi, I'm new to pydra. I'd like to know if the ouputs of `DockerTask` remain in the container. Well, my goal is to build a pipeline where I have a...
Placeholder for comparing Nipype 1.0 PROV and proposed additions in the BEP028 document.
I mentioned to Dorota that it might be useful to implement an actual 'user' field that will return who ran each process. Locally, this is quite limited (e.g., my MacBook...
I would like to provide documentation (with doctests) for a `FunctionTask`, like: ```python @task @annotate({"return": {"sum": int}}) def add(x: int, y: int): """Add x to y. Examples ---------- >>> task...