Ghislain Vaillant

Dissociate task cmdline from validation

2

As part of the process of designing task packages, I find myself providing some doctest of style: ```python """ Examples -------- >>> task = MyTask(...) >>> task.cmdline 'cmd ...' """...

Cannot use attrs post init or factory to compute a fallback value to a field

2

EDIT: See [post](https://github.com/nipype/pydra/issues/640#issuecomment-1534228181) below with an alternative solution using `@attrs.field.default` I am trying to compute a fallback value for an `output_basename` field based on an `input_image`. ```python @attrs.define(kw_only=True) class MySpec(pydra.specs.ShellSpec):...

Support for dataclasses at a surface level

3

I am a big advocate for class-based definition of input and output task specifications over dynamic constructs via `pydra.specs.SpecInfo(..., fields=[...])`. One annoying thing though is that class-based specifications aren't working...

Formatter argument can bypass xor and mandatory in input spec

7

Usage of `formatter` together with `xor` and `mandatory` metadata may yield inconsistent command-line output. Given the following spec: ```python import pydra input_spec = pydra.specs.SpecInfo( name="Input", fields=[ ( "foo", bool, {...

Support for aliases in ShellCommandTask specifications

2

Whilst working on [pydra-freesurfer](https://github.com/aramis-lab/pydra-freesurfer), I came across some FreeSurfer interfaces where one could legitimately wonder what the appropriate name for a given field should be. For instance, `recon-all` provides [4...

[FIX] Use `scipy.interpolate` namespace

1

Instead of the `scipy.interpolate.ndgriddata` namespace which is now deprecated.

Fails to build with a modern toolchain on conda-forge

1

Convert3D used to build on `conda-forge` but no longer does. I was trying to provide packages for the new `osx-arm64` architecture (for the new Mac M-series), which requires a refresh...

Get CI to run as much of the test suite as possible with the latest version of Pydra Issues found so far: - [ ] https://github.com/nipype/pydra/pull/739 - [ ] https://github.com/nipype/pydra/issues/740

Highlighting for model components

1

See the example `build.gradle` in the official [documentation](https://docs.gradle.org/current/userguide/software_model_extend.html). Would perhaps make sense to add some visual aids for: ```gradle model { components { ... ``` Does `sublime-gradle` handle this?