Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use alignments from tRNAscan-SE without re-creating them in R2DT #98

Open
patriciaplchan opened this issue Dec 3, 2022 · 0 comments
Open

Comments

@patriciaplchan
Copy link
Collaborator

Instead of creating tRNA alignments with cmalign and tRNA covariance models, the alignments generated by tRNAscan-SE in the secondary structure output can be used. The alignments generated by tRNAscan-SE use the domain-specific models, not isotype-specific models. The exceptions are mitochondrial tRNAs in vertebrates and selenocysteine tRNAs that use isotype-specific models. tRNAscan-SE also makes adjustments to the alignments originally generated by cmsearch. These include removing the non-Watson-Crick basepairs, adding missing basepair that sometimes occurs at the two ends of tRNA-fMet in bacteria, and removing extra helix such as variable arm or D/T-arm. That means when using tRNAscan-SE alignments, the SS and SS_cons included in the .afa file as input for infernal2mapping.py will always be the same. Since the current templates were generated from the consensus of the model training data, I expect that they will mostly match up with the secondary structure of individual tRNAs. The main variation will be the length of the variable arm for Type II cytosolic tRNAs, and the length of the D-arm and T-arm of the mitochondrial tRNAs. If Infernal/Traveler mapping can handle this variation, I think the current templates should just work. But I can certainly make adjustments to the templates if needed after trying out the fixes of the Infernal/Traveler mapping problem in combination with the use of tRNAscan-SE alignments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant