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
In neuroscout-cli, we fetch datasets using datalad, and then run fitlins on it.
Would it make sense to move that functionality into fitlins itself? I would imagine this could make it much easier for users to use FitLins on remote datasets without first having to muck w/ downloading and setting up the datasets themselves.
The text was updated successfully, but these errors were encountered:
What would it look like? As in allow somebody to say fitlins ///openneuro/ds000003 /out participant -d ///openneuro/ds000003-fmriprep ...? Or just run datalad get on files if we detect they're in a datalad dataset? And would that play nicely with being run inside datalad run ...?
I was thinking the former, but maybe it's putting too much onus on FitLins to do everything. It just seems like a lot of the neuroscout-cli set up work is fairly generic and could be generalized to other datasets available through datalad.
In
neuroscout-cli
, we fetch datasets using datalad, and then run fitlins on it.Would it make sense to move that functionality into fitlins itself? I would imagine this could make it much easier for users to use FitLins on remote datasets without first having to muck w/ downloading and setting up the datasets themselves.
The text was updated successfully, but these errors were encountered: