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
Hypothetically speaking, if the streamline coordinates of the input fg are not in double precision float, doesn't this double the ram usage without any associated gain in precision?
) its actually single point precision, so it seems that this is necessarily the case.
Also, even in cases where the input is in double point precision, is that level of precision actually useful given the diffusion resolutions we are typically working with?
Is this line necessary?
The text was updated successfully, but these errors were encountered:
I've tested some algorithms (encode, LiFE) using fg without converting to double. The results were within expected stochasticity. We need to test it with more algorithms but so far it seems that we don't need to convert to double.
vistasoft/fileFilters/mrtrix/dtiImportFibersMrtrix.m
Line 103 in 8c402f9
Hypothetically speaking, if the streamline coordinates of the input fg are not in double precision float, doesn't this double the ram usage without any associated gain in precision?
Indeed, at this point (
vistasoft/fileFilters/mrtrix/dtiImportFibersMrtrix.m
Line 79 in 8c402f9
Also, even in cases where the input is in double point precision, is that level of precision actually useful given the diffusion resolutions we are typically working with?
Is this line necessary?
The text was updated successfully, but these errors were encountered: