run order not preserved about bidskit HOT 3 CLOSED

just a follow up note in case its helpful. Was talking w/ a fellow bidskit user, and I now believe that this is only an issue when the the same run happens twice, for some unplanned reason (e.g. technical error, participant-related issue). When the same task is intended to be run twice, and ProtocolTranslator appropriately labels them as run-01 and run-02, there will not be a problem. So just seems to be when you need to run the same task twice due to some error.

from bidskit.

Thanks, this is actually quite helpful. I'm planning on doing another pass on bidskit development in the next couple of weeks and will add some code to try to catch this situation. There is some argument for deleting failed runs from the DICOM folder prior to running bidskit, but that's only practical if your DICOM folder organization has series-level subfolders (ie not a flat organization).

from bidskit.

The issue may have been the arbitrary ordering of the list returned by glob, as described here. The list is now lexically sorted before being passed to run number generation. Let me know if this fixes things for you.

from bidskit.