You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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
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.
The text was updated successfully, but these errors were encountered: