You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the reconstruction code does not correctly handle data that were acquired with phase or slice oversampling enabled. This wouldn't be a big effort to include - but as I'm not aware of any reasons why oversampling would be useful for MP(2)RAGE scans (please let me know if you are aware of any!) then implementing this is not a priority. It is worth knowing, though, in case you have data acquired with it on!
It would be even less effort to add detection that oversampling was enabled and to warn the user that this would not be handled properly. Hopefully I'll get around to doing that soon. :)
The text was updated successfully, but these errors were encountered:
Currently the reconstruction code does not correctly handle data that were acquired with phase or slice oversampling enabled. This wouldn't be a big effort to include - but as I'm not aware of any reasons why oversampling would be useful for MP(2)RAGE scans (please let me know if you are aware of any!) then implementing this is not a priority. It is worth knowing, though, in case you have data acquired with it on!
It would be even less effort to add detection that oversampling was enabled and to warn the user that this would not be handled properly. Hopefully I'll get around to doing that soon. :)
The text was updated successfully, but these errors were encountered: