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
Hello there,
We usually run hydra to produce a consensus fasta file which is later fed into the sierralocal pipeline. We realised that hydra reports D232N as N232D in the aavf file, however sierralocal captures it as D232N. D232N is a common nonpolymorphic accessory mutation selected in persons receiving RAL and EVG. Alone, it has little effect on INSTI susceptibility.
On further interrogation, we found out that it (D232N) is not even included in the mutation_db.tsv. How best can we rectify this
In addition, we request to be advised on how we can update the mutation_db.tsv in future.
The text was updated successfully, but these errors were encountered:
Updating the built in mutation database is not straightforward as Stanford HIVDB does not have this info available in an easy format for us to parse and generate a new file. For this, I recommend uploading your AAVF to this program and run it for analysis https://hivdb.stanford.edu/hivdb/by-reads/.
Thanks @ericenns,
I agree with you about the format.
We shall cross check with Stanford HIVDB too as recommend. Though from the screenshot below, it seems they have D as their reference but we shall further see how to compare with our aavf
Hello there,
We usually run hydra to produce a consensus fasta file which is later fed into the sierralocal pipeline. We realised that hydra reports D232N as N232D in the aavf file, however sierralocal captures it as D232N. D232N is a common nonpolymorphic accessory mutation selected in persons receiving RAL and EVG. Alone, it has little effect on INSTI susceptibility.
On further interrogation, we found out that it (D232N) is not even included in the mutation_db.tsv. How best can we rectify this
In addition, we request to be advised on how we can update the mutation_db.tsv in future.
The text was updated successfully, but these errors were encountered: