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
The tabular format of the BidsComponent zip_list implies an inherent ordering of component entries. Even though snakebids doesn't guarantee any particular insertion order when creating the table, the order should be stable across the lifespan of the component and across any modifications (especially if we support a sorting api in the future).
BidsComponent.expand() currently uses set() to deduplicate the expanded complement of paths, which randomizes the order. A new deduplication method that does not destroy insertion order should be implemented.
The text was updated successfully, but these errors were encountered:
.expand() in all three Expandables was using `set()` to deduplicate
paths following expansion. This was altering the order of the paths,
preventing predicatable expansion
This fix uses `dict.fromkeys` to deduplicate while preserving order
Resolveskhanlab#346
.expand() in all three Expandables was using `set()` to deduplicate
paths following expansion. This was altering the order of the paths,
preventing predicatable expansion
This fix uses `dict.fromkeys` to deduplicate while preserving order
Resolves#346
The tabular format of the
BidsComponent
zip_list implies an inherent ordering of component entries. Even though snakebids doesn't guarantee any particular insertion order when creating the table, the order should be stable across the lifespan of the component and across any modifications (especially if we support a sorting api in the future).BidsComponent.expand()
currently usesset()
to deduplicate the expanded complement of paths, which randomizes the order. A new deduplication method that does not destroy insertion order should be implemented.The text was updated successfully, but these errors were encountered: