Conversation
Use of this option forces tckstats to explicitly calculate the length of every streamline based on the distance between every sequential vertex pair, rather than relying on track file header information regarding step size to speed up the calculation. This is particularly important if some non-rigid transformation has been applied to the track data.
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use of this option forces
tckstatsto explicitly calculate the length of every streamline based on the distance between every sequential vertex pair, rather than relying on track file header information regarding step size to speed up the calculation. This is particularly important if some non-rigid transformation has been applied to the track data.In response to this forum post. Ended up opting against wiping the track file header fields in
tcknormalise: The tracking algorithm step size is still relevant information despite a non-linear transformation having been applied, so even ifoutput_step_sizewere removed (which makes sense),tckstatswould then revert to usingstep_sizeto calculate streamline length.There are of course other ways this issue could be addressed (e.g. never use step size information when calculating length); but all have their pros and cons (e.g. calculation of histogram bin size works best if the step size is known). Feel free to comment if you think one of the alternatives is preferable to this.