You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just an idea... When we build the container for a tool, such as FreeSurfer, we also know the way to run this tool in a more ReproNim compliant fashion, such that all the provenance is captured, and the output is expressed in its semantically enriched form.
Is there any value for, when a ReproNim flag is added, we add to the container the necessary packages (i.e. PyNIDM), and an 'entry point' that runs the freesurfer fs2nidm combo 'automatically?
I think we may know the same ReproNim configuration for ANTS, FSL, etc.
Opening this issue for discussion of this topic...
The text was updated successfully, but these errors were encountered:
In theory and principle, yes -- we could augment / append to successful execution of a known tool some additional execution of additional routine.
If I get it right: A little tricky aspect is actually our need to "inject" our functionality so we know what command line argument was specified e.g. for output directory, so pretty much to either "patch" the tool to run our thing from within, or provide an additional parser which is aware of original tool command line structure/options and then parse ourselves in addition to that tool...
In addition to neurodocker, and potentially a little easier since there they should be all "BIDS-Apps" compliant interfaces, we could add similar functionality to https://github.com/ReproNim/containers collection.
there is perhaps an interesting custom config layer to consider that could be automated to add different kinds of interfaces. across a few projects there are needs for standardized CLI interfaces (e.g., BIDS-Apps, Nobrainer/BBQS model zoo), additional functionality (e.g., prov extraction, derivative modeling), and services (e.g. pushing to repropond/lake). if indeed these could be abstracted away when building a container it would be very helpful to the user.
since neurodocker is quite generic, it may be more challenging to set up these interfaces in an easy to use way, but we can look into it. perhaps repronim containers is the more appropriate place to automatically have some of these flags turned on.
Just an idea... When we build the container for a tool, such as FreeSurfer, we also know the way to run this tool in a more ReproNim compliant fashion, such that all the provenance is captured, and the output is expressed in its semantically enriched form.
Is there any value for, when a ReproNim flag is added, we add to the container the necessary packages (i.e. PyNIDM), and an 'entry point' that runs the freesurfer fs2nidm combo 'automatically?
I think we may know the same ReproNim configuration for ANTS, FSL, etc.
Opening this issue for discussion of this topic...
The text was updated successfully, but these errors were encountered: