Replace ViralAI With Internal Solution
@edsu7 is already working on this.
Since Jun 24, 2026.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
## The issue
ViralAI is tasked with producing lineage calls for the clinical data, which the iMS portal ingests for public usage.
However ViralAI seems not to be working as expected recently.
## Tasks
1. iMS portal should ingest the lineage calls produced by ViralAI.
- pedigree gets the csv (generated by ViralAI) from google storage, and updates iMS data using song and maestro.
- this process starts every Tuesday and Friday nights, when we produce a "release bundle", which ViralAI uses to produce the calls.
- after iMS ingests those calls, all samples submitted by "release" date should have lineage name in the explorer.
2. After iMS portal ingests the latest lineage calls, we will replace ViralAI with an in-house workflow that reproduces the same lineage calls. The benefits of replacing are: 1. faster at making the lineage calls public. 2. fewer 3rd party dependencies.
**- this is more of a devops task, not so much dev work.**
- @justincorrigible and @leoraba to provide a proposal, based on which we will evaluate effort and timeline.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.