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
Description
As PSD we are having to develop pipelines where there are faculty input points at various internal points within pipelines. i.e. where the faculty has manually prepared a plate outside of LIMS rather than gone through the previous steps in LIMS to get to that point.
Can we come up with a standard way to implement such input points to avoid complexities with labware states, state machines,
Who the primary contacts are for this work
PSD Developers
Knowledge or Stake holders
The two main examples of this recently are in Bioscan (for library prep) and scRNA (at donor pooling and at library prep). Developers with knowledge of those pipelines will have useful input.
Additional context or information
Output should include an annotated diagram of the 'standard' solution with plate purposes, purpose flags and state handling details.
Things to consider:
How the faculty samples should be input (manifests?)
How submissions should be done on the input plates vs intermediate plates. Do they have different submission templates? Different request and/or library types? What if they are just CustomerRequests?
How the plate purposes should be named ('input' suffix?)
Can we avoid custom state machines and plate purposes to implement this
The text was updated successfully, but these errors were encountered:
Have separate plate purposes similar to 007c scRNA ?
Currently the well-failing issue with Bioscan is due to Limber LIMS treating the Lysate plate as Stock plate which is not compatible with well-failing capability in Limber.
Can we have a separate standalone capability for well failing?
Can we manage the well failing in the downstream plates after the Lysate plate is created?
An alternative option could be that we wait to know more about the Anospp pipeline to be able to provide a common solution and currently capture failed well information separately in Google Sheets.
Also suggested by Emma D. that the well-failing capability implementation from a LIMS point of view can be deferred until the time there is more clarity on common/overlapping requirements across Bioscane, 007c scRNA, and Anospp pipelines to begin with, which can be derived when the requirements mentioned will be operationalized/validated.
Description
As PSD we are having to develop pipelines where there are faculty input points at various internal points within pipelines. i.e. where the faculty has manually prepared a plate outside of LIMS rather than gone through the previous steps in LIMS to get to that point.
Can we come up with a standard way to implement such input points to avoid complexities with labware states, state machines,
Who the primary contacts are for this work
PSD Developers
Knowledge or Stake holders
The two main examples of this recently are in Bioscan (for library prep) and scRNA (at donor pooling and at library prep). Developers with knowledge of those pipelines will have useful input.
Additional context or information
Output should include an annotated diagram of the 'standard' solution with plate purposes, purpose flags and state handling details.
Things to consider:
The text was updated successfully, but these errors were encountered: