blast_samples_chr2_chr3/ ========================= Full cluster membership for two additional loci, prepared to test whether the chr1 BIG-cluster BLAST failure (see blast_samples/README.txt) is specific to that one region or a general property of large clusters. Representative/consensus sequences for these same clusters are already in blast_samples/consensus_samples.fasta (labeled BIG_chr2_..., SMALL_chr2_..., BIG_chr3_..., SMALL_chr3_...) -- not duplicated here. FILES ----- full_chr2_BIG.fasta 1678 sequences. Locus chr2:100118009-100180909. Representative HG00675_chr2_region_100118009-100180909_hap0. full_chr2_SMALL.fasta 5 sequences. Same locus. Representative HG02442_chr2_region_100118009-100180909_hap0. full_chr3_BIG.fasta 1537 sequences. Locus chr3:100195058-100330759. Representative HG01492_chr3_region_100195058-100330759_hap1. full_chr3_SMALL.fasta 15 sequences. Same locus. Representative HG02090_chr3_region_100195058-100330759_hap1. full_members_chr2_BIG.tsv, full_members_chr2_SMALL.tsv, full_members_chr3_BIG.tsv, full_members_chr3_SMALL.tsv Raw clusters_summary.tsv rows for each FASTA above. Provenance/audit trail, not sequence data. PURPOSE OF THIS BATCH ---------------------- Answers: does the chr1 result generalize to other loci? Same BIG-vs-SMALL forward-BLAST test design as chr1, run at two independent regions. GENERATION ---------- Produced by extract_chr2_chr3_full_clusters.sh from clusters_summary.tsv and /clusters/_all_seqs.fasta, targeting the four cluster IDs above (already known from the original select_blast_samples.sh run). Re-extracted with reextract_with_fixed_dedup.sh on 2026-09-05 to correct the duplicate-representative bug described above.