-
Notifications
You must be signed in to change notification settings - Fork 8
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
input_drops in yml file #34
Comments
The usage of These input spec are highly customised in the nipype interfaces, instead of something mapping directly to the original FSL CLI. |
okay, so it means if there is something in nipype but not in FSL CLI, then we should put it in |
hello, when I use the converter for
It means in this module, only the |
This is normal behaviour. When you ask the converter to convert a full module, it will show you the list of interfaces with no spec in the parameter file and warn you nothing has been done for things you didn't provide details with. If you want to convert
|
ah I see, thank you. Yes, I was converting |
hello @htwangtw I'm starting working on using the converter for interfaces in
fsl.model
.In
fsl_model_param.yml
, I notice that there is a field calledinput_drops
. You mentioned this field here #11 . What do you mean bynot compatible with pydra
?I guess that
inputs_drop
is not mandatory, and I found one example herepydra-fsl/specs/fsl_utils_param.yml
Line 88 in 094cec2
Do we have a criterion when two or more fields are exclusive, which one we choose to drop?
Thank you!
The text was updated successfully, but these errors were encountered: