Good to know!
I did a little more digging, since I was curious as to why both here and in another thread the script isn’t capturing any of the terminal output from the unsuccessful command:
dwi2response: Output of failed command:
tumbleweed appears on terminal
The problem is that when the fatal error occurs, the relevant (non-MRtrix3) library doesn’t write the error to the command’s standard error output, but to the current tty terminal. As a result, due to the mechanism used by the Python script library for calling these commands, the script library fails to capture this text, leaving you with an empty error message and a confused look. (Mind you, even if it were printed, the error message itself isn’t that clear: ‘Bus Error (core dumped)’)
I’m trying to fix this so that the script can give a more informative error; but for now, if “Output of failed command” is empty, there’s a good chance that you’ve run out of memory.
Rob