Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Foreign Function Tasks #287

Open
effigies opened this issue Jun 17, 2020 · 1 comment
Open

Foreign Function Tasks #287

effigies opened this issue Jun 17, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@effigies
Copy link
Contributor

In Nipype 1.x, we have the MatlabCommand interface, for running MATLAB scripts.

More broadly, we can think of this as a foreign function interface (FFI) that allows us to pass values to a node, which are converted to the input form expected by the foreign function, and run with that scripting engine/interpreter.

I think we can aim for something broad, like ForeignFunctionTask, that could be easily subclassed into RTask, MatlabTask (possibly a separate OctaveTask?), JuliaTask or whatever scripting language people need. I would suggest the base class go here, and MatlabTask go in something like pydra-matlab.

@effigies effigies added the enhancement New feature or request label Jun 17, 2020
@satra
Copy link
Contributor

satra commented Jun 18, 2020

i think specialized tasks could have their own package, but i think pydra should have some basic notion of a generic script executor whether python/r/octave/matlab or anything else. perhaps along snakefile or cwl lines. tell me how to create the commandline for you and how to grab/glob outputs from named ports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants