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

library reamplifications #146

Open
MatthewMah opened this issue Oct 11, 2023 · 2 comments
Open

library reamplifications #146

MatthewMah opened this issue Oct 11, 2023 · 2 comments
Labels
Urgent This is higher priority

Comments

@MatthewMah
Copy link
Contributor

MatthewMah commented Oct 11, 2023

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.

@KimCallan
Copy link
Collaborator

can we think about having a new section in the sidebar that is for Lib Reamps, and then we can make batches in it like how we do for Lysates, Extracts, etc. And if we have an upload function that lets us say which Lib-ID we are reamping and what well it is in.

@KimCallan
Copy link
Collaborator

some libraries have been re-amped multiple times on different batches, so we have to allow for multiple duplicate Lib-IDs to exist, but maybe we differentiate with a new ending .Amp1, .Amp2, etc. or something like it

@KimCallan KimCallan added the Urgent This is higher priority label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Urgent This is higher priority
Projects
None yet
Development

No branches or pull requests

2 participants