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

What to do when homology arms don't match genome sequence? #23

Open
manulera opened this issue Sep 23, 2024 · 3 comments
Open

What to do when homology arms don't match genome sequence? #23

manulera opened this issue Sep 23, 2024 · 3 comments

Comments

@manulera
Copy link
Owner

This happens in the MYTK MoClo kit, where the sequence of the homology arms of 500bp does not exactly match that of the genome, having a few mistmaches. What to do in a case like this? Include Ns?

@manulera
Copy link
Owner Author

Causes something like this: manulera/OpenCloning_frontend#241

@dgruano
Copy link
Collaborator

dgruano commented Sep 23, 2024

To me, it would make sense to add the Ns (or any of the other IUPAC symbols. We could validate them later with sequencing results, like we would do for this issue.

Additionally, we could:

  1. Add a feature named "unknown recombination site"
  2. Label the construct as "unfinished" or "missing information" so the users pay attention

@manulera
Copy link
Owner Author

Yes, I agree that it makes sense to use those symbols. The issue is that sometimes there will be gaps, and that is not really supported by the letter notation (would have to be something like N or -.

Also, we would have to decide what to do with the annotation present in the plasmid or locus and how to transmit it.

I would say that this is something to think about but not prioritary to fix, since at least for the time being we can prioritise the sequence of the insert.

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

No branches or pull requests

2 participants