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
Thanks for this tool! It really benefits me a lot.
However, there is a little bit problem here when use a batch program to traverse the result set for STT I found that the file names of the results are not following lexicographical order.
I hope to revise slicer2.py
Change Line 182 to
Yes, the segments are here sorted numerically instead of lexicographical order. But normally in Windows file explorer, the files can be sorted correctly.
I agree that following lexicongraphical order will bring convenience to many user programs to deal with the segments. However, the problem is how to decide the default length of a segment index. For example, if you use %05d, then what if there are over 100,000 segments (even if this seems to be impossible)? Or if we use dynamic lengths (for example, %02d for 11-100 segments, %03d for 101-1000 segments), will it bring new problems to user programs when matching name patterns? What is your opinion on this?
Thanks for this tool! It really benefits me a lot.
However, there is a little bit problem here when use a batch program to traverse the result set for STT I found that the file names of the results are not following lexicographical order.
I hope to revise slicer2.py
Change Line 182 to
The text was updated successfully, but these errors were encountered: