library reamplifications
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Library batch needs to support reamplifications. Instead of starting with extract inputs, we start with library inputs to create more library fluid.
One idea is to leave the existing library batches (extract -> library) and create new kinds of objects for (library -> library). This may require additional changes accounting for where the exact library source for captures.
Another idea is to introduce a new layer. All library batches generate amplified libraries, and these are inputs to capture/shotgun batches.
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
No files, tests, or entry points are named. Start by mapping how existing extract-to-library batches represent sources and how capture or shotgun batches consume libraries, then compare the two proposed designs. Done means selecting and implementing a defined model for library-to-library reamplifications, including source tracking and affected batch behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100