Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
tckgen/tckedit: warn user if ROI voxel size is smaller than step size of streamlines #1855
Sounds appealing. Two concerns though:
I seem to recall having made an explicit decision at some point to not only not interpolate masks during tracking, but also to remove an old command-line option that toggled the behaviour.
For test runs of
Other factor to consider is that by using this mechanism, streamlines can only be comprehensively compared to all ROIs once the entire streamline trajectory has been produced. This is the same for ACT with back-tracking: if a streamline were to intersect an include region, only to then be truncated such that it then fails to intersect that region, the fact that the final streamline fails to intersect all include regions needs to result in its rejection; see code here and here.
While adding a
Given the comparably short computation time of this step relative to tracking, are we better off just using this mapping mechanism throughout all relevant commands always?