# Dwipreproc eddy\_cuda --slspec Unable to open file MultiBandGroups **URL:** \ **Category:** Uncategorized\ **Created:** [April 6, 2018, 6:45pm UTC](https://community.mrtrix.org/t/dwipreproc-eddy-cuda-slspec-unable-to-open-file-multibandgroups/1573 "2018-04-06T18:45:09Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![DAndrews](https://community.mrtrix.org/letter_avatar_proxy/v4/letter/d/da6949/32.png) [@DAndrews](https://community.mrtrix.org/u/DAndrews)\ **Post date:** [April 12, 2018, 6:36pm UTC](https://community.mrtrix.org/t/dwipreproc-eddy-cuda-slspec-unable-to-open-file-multibandgroups/1573/8 "2018-04-12T18:36:15Z")
Hi Rob, Your sensible explanations are once again helping keep me sane! I have tried using the _-continue_ option as you suggested. This appears to get around the _msg=MultiBandGroups: Unable to open file error_ but still returns _UnicodeDecodeError: ‘utf8’ codec can’t decode byte 0x9e in position 1: invalid start byte_ Therefore, I think adding the full path to the slspec.txt file for the --slspec flag might have worked, however the file “my\_slspec.txt” or “myslspec.txt” is failing to be read regardless. From reviewing [Hamed’s recent post](https://community.mrtrix.org/t/dwipreproc-command-error/1574) and the corresponding [GitHub issue](https://github.com/MRtrix3/mrtrix3/issues/953) a solution did not jump out at me. Did I miss something? It seems like the update for this should hopefully be available soon (days not weeks) 🤞😄 so I’m thinking my best option may be to wait it out. Although, this may not solve the unicode issue… --- _[View the full topic](https://community.mrtrix.org/t/dwipreproc-eddy-cuda-slspec-unable-to-open-file-multibandgroups/1573)._