I understand that in the new 3.0.0 version the tractography commands preserve the order of streamlines in their outputs even with multithreading enabled (as per the changelog below)
Does this include the output of tcksift2? I am developing a pipeline that uses tckedit, tcksample and tcksift2, and I need the streamline order from each command to match up. Can I use tcksift2 with multi-threading as well, or should I use single threading for this.
tcksift2 doesn’t produce a new streamlines file, it produces a file of per-streamline weights – the order of which has to match the original input streamlines file anyway. So yes, it’s perfectly safe (and highly encouraged) to use multi-threading with that too.