Closed satra closed 10 years ago
The 4th parameter should be an unsigned int >= 1 so I'm not surprised that passing a float causes an error. Hans added quite a bit of error checking since the previous version which is probably why this error is being caught now.
thanks nick
pinging @hjmjohnson
hey hans this is disrupting the bsplinesyn generator in nipype - i'm happy to fix it on nipype's side, but 26.0, 0.0 and 3.0 should in theory be castable to int without error :)
let me know what you prefer - we are going to release a patch in nipype soon, so i can include it.
is there a place that lists the datatypes for each option?
My brain but I recognize that that's not very useful. :)
here come the brain machine interfaces! but for now i made this change:
it would be great to have this documented somewhere, but i'm closing this for now.
Thanks Satra. I'll put it on my to-do list.
Dear @satra and @ntustison
I'm still encountering this issue. I've installed the most recent version from github. Am I doing something wrong or is this "bug" still persisting? When manually removing the .0's from the command and running it, it runs successfully. Any suggestions?
p.s. realized this issue is probably better discussed in the nipype community. So will cross post this there.
relevant settings:
reg.inputs.transforms = ['Translation','Rigid', 'Affine', 'SyN', 'BSplineSyN']
reg.inputs.transform_parameters = [(0.1,),(0.1,), (0.1,), (0.2, 3.0, 0.0),(0.25,25,0)]
Description: itk::ERROR: CommandLineParser(0x183c7b0): ERROR: Parse error occured during command line argument processing
ERROR: Unable to convert '25.0' to type 'j' as unsigned int
this form of parameterization
results in an error while this doesn't:
also this error didn't happen on this version (bf3730d8a5614):
error: