pydra
                                
                                 pydra copied to clipboard
                                
                                    pydra copied to clipboard
                            
                            
                            
                        Pydra Dataflow Engine
Hi, I would like to create a task which receives as input a "complex" object and (possibly) a function as following: ```` @pydra.mark.task def wrapping_task(object, function): result = function(object) return...
## Acknowledgment - [ ] I acknowledge that this contribution will be available under the Apache 2 license. ## Types of changes - [ ] Bug fix (non-breaking change which...
I've been debugging code created by @harveyaa, and there is an issue when `FunctionalImage` is passed as an input. Even if we make sure that the image doesn't change during...
```Python In [19]: @pydra.mark.task ...: def f(a, b=1): ...: return a + b ...: In [20]: g = f() In [21]: g(a=3).output.out Out[21]: 4 In [22]: g(a=3, b=2).output.out Out[22]: 5...
Working with latest `master`... I'm trying to add an `update_spec(spec, dict)` function that would make it easier to separate initialization and argument population and solve issues like #417 by simply...
Logging the outputs of interfaces has been a long-standing issue for Nipype 1.0 since its origins. Although I believe it currently solves the problem in a pretty acceptable way, I...
## Types of changes - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix...
It would be good to start work on a migration guide for Nipype 1 users to Pydra. Some ideas for sections: * How to rewrite your existing interface as a...
`func` as function input variable name creates conflict with `mark.task(func)` Pydra version: 0.14 Minimal example to recreate the bug: ```python import nibabel as nb import numpy as np import pydra...
In discussions at the Brainhack, the question of conditional tasks came up again, so it seems worth reviving. I think the most comprehensive previous discussion was in https://github.com/nipy/nipype/issues/2539, but I...