Closed robbwh closed 3 years ago
Arg. I clearly didn't do extensive enough testing when I rewrote the command parser. I'll give it a look when I get back to work on Monday.
Fixed in 2.0alpha11, along with a couple other bugs that the testing exposed :-)
Excellent thanks! The outputs from happy look quite nice--especially viewed in 3D like in your 2019 paper.
May have more explicit questions later down the line...process seems to be working with a TR=2 and 41 slices. Only has agreement with hand recorded scanner pulse rate for about 1/2 of scans (other half it estimates too low of a pulse) but haven't done any QCing yet.
Anyway will likely post a question on neurostars at some point!
Describe the bug When running happy using rapidtide 1.9.1 specifying a motion file seems to work and happy completes.
However, When running rapidtide 2.0a10 specifying a motion file results in an error message:
Here is the full output when running happy:
Is this a known bug? A quick search led me to this commit: https://github.com/bbfrederick/rapidtide/commit/34bdcde3185ba3404f1383fb1f078a33b57135ad