What problem does it solve? Demultiplexing short-read sequencing runs at FGCZ involves coordinating queue monitors, B-Fabric metadata, barcode validation, bcl2fastq/bases2fastq execution, and gStore archival — a multi-step process where failures (stuck runs, wrong base masks, barcode errors) are hard to diagnose without deep system knowledge. ## Core Features & Use Cases - Run and monitor demultiplexing: Start the automated queue monitor, manually run draugr.py on a single run, or reprocess specific orders with fine-grained skip flags. - B-Fabric integration: Query order metadata, track run status transitions (PROCESSING → DEMULTIPLEXING → DEMULTIPLEXING_FINISHED/FAILED), and set custom BasesMask attributes. - Per-chemistry base masks: Reference read structures and bcl2fastq masks for all 10x chemistries (3'/5' GEX, VDJ, ATAC, Multiome, Visium, Flex), including the ATAC i5 lowercase-y gotcha and the current manual-demux workaround for cellranger-atac/arc. - Use Case: A run is stuck in "Demultiplexing" status — check the draugr logs, identify the failure, and rerun with --demux-only-mode or --reprocess-orders to recover without repeating completed steps. ## Quick Start Ask the agent to check the demultiplexing status of a sequencing run and show the latest draugr log for troubleshooting.