OpenCloning / OpenCloning/OpenCloning_backend
Clarify assembly topology beyond circular
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 11
- Avg merge
- 14m
- Merged PRs (30d)
- 5
Description
Related to #368
When validating in pydna, you have to get a list of input sequences, and in the case of insertions, the same id appears twice in the input list, but only one should be kept. In other cases however, perhaps the same sequence is used twice? Although in that case probably a different id must be used, at least when doing it from the website.
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.
Research direction
Start with the pydna validation flow and read related issue #368. Determine how duplicate input sequence IDs should be handled for insertions versus legitimate reuse, then document or implement clear topology rules for both cases; done when the expected behavior is defined and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100