Sort layers alphabetically for deterministic h5ad output#12
Merged
ygao61 merged 1 commit intoCOMBINE-lab:mainfrom Feb 19, 2026
Merged
Sort layers alphabetically for deterministic h5ad output#12ygao61 merged 1 commit intoCOMBINE-lab:mainfrom
ygao61 merged 1 commit intoCOMBINE-lab:mainfrom
Conversation
The HDF5 B-tree stores group children in insertion order, and Python set iteration order (used when populating layers from output_assays) is non-deterministic. This caused the layers (spliced, unspliced, ambiguous) to be written in different orders across runs, producing different md5 checksums even though the data was identical. Sort layers alphabetically via OrderedDict before writing h5ad files to ensure byte-level reproducibility. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
2 participants
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.
Summary
OrderedDict) before writing h5ad files to ensure byte-level reproducibilityoutput_assays) is non-deterministic. This caused the layers (spliced,unspliced,ambiguous) to be written in different orders across runs, producing different md5 checksums even though the data was identical.quants.h5adand the filteredfiltered_quants.h5adoutputsTest plan
1k_pbmc_v3test data) and verified bothquants.h5adandfiltered_quants.h5adnow produce identical md5 checksums across runs🤖 Generated with Claude Code