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
{{ message }}
Repository navigation
Report: record BV-BRC-only evidence as not available, not zero, on non-genome runs #90
Goal: a sequence-only report must never look like a full genome report. Part of #87.
When BV-BRC is not the source, many fields are not "zero" but "not available": specialty genes, essentiality, taxonomy lineage, genome metadata. A score component with no evidence behind it currently contributes 0, exactly like "checked and false" (pitfall #12).
Scope
Every BV-BRC-derived field in report.json records its source, or not_available with a reason.
Status:#101 implements the run-level part (open, ready to merge, after #98 → #99 → #100).
Done:
On the --from-fasta route, M2 records not_available (component → reason) in m2_pdb/run.json. The runner prints those components as "not available", and the full report shows a "Not available on this run" note in its header.
A genome run and a FASTA run of the same protein are distinguishable from report.json alone (genome.annotation_route, genome.not_available), and a test pins this.
Left before closing:
A per-protein "evidence coverage" line in the HTML report: which sources answered, which did not apply, which were not run. The run-level note covers the FASTA route today, because every protein there lacks the same sources. A per-protein line matters once sources differ by protein: a partial UniProt mapping, a provider that failed for some proteins, or M2: virulence and AMR evidence without BV-BRC — VFDB and CARD by DIAMOND #91's VFDB/CARD rows.
Extend not_available beyond the FASTA route if other routes turn out to lack sources. None are known yet.
Activity
Jiahuic commentedon Oct 9, 2026
Status: #101 implements the run-level part (open, ready to merge, after #98 → #99 → #100).
Done:
--from-fastaroute, M2 recordsnot_available(component → reason) inm2_pdb/run.json. The runner prints those components as "not available", and the full report shows a "Not available on this run" note in its header.report.jsonalone (genome.annotation_route,genome.not_available), and a test pins this.Left before closing:
not_availablebeyond the FASTA route if other routes turn out to lack sources. None are known yet.Merge pull request #101 from NIAID-BRC-Codeathons/feat/90-not-available