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

feat: Labware offset data should last indefinitely and only be deleted by the user and not after 20 runs (v6.3.1) #13430

Open
MSMDG opened this issue Aug 31, 2023 · 0 comments
Assignees
Labels
feature-request A request for a new feature or a change that isn't a bug. May require further triage or scoping.

Comments

@MSMDG
Copy link

MSMDG commented Aug 31, 2023

Overview

As of the moment (on v6.3.1) having multiple protocols and running them a few times per day will result in exceeding the 20 runs that are stored on the robot and labware offset will be deleted. Therefore, we need to perform a labware positional check for each protocol every 5 days. Having to do this so often, results in a very time-consuming task and a big inconvenience whereas other platforms require to do this for a minimum of just once per year or not even at all.

We would like for the Labware Offset Data to:

  • Last indefinitely and only be deleted/overwritten by the user.

  • Be independent of how many runs are performed.

  • If for a labware, labware offset data are missing, to have a more obvious notification/alert before starting the protocol rather than going to look for it if it exists.

Implementation details

No response

Design

No response

Acceptance criteria

No response

@MSMDG MSMDG added the feature-request A request for a new feature or a change that isn't a bug. May require further triage or scoping. label Aug 31, 2023
@MSMDG MSMDG changed the title feat: Labware offset data should last indefinitely and only be deleted by the robot user and not after 20 runs (v6.3.1) feat: Labware offset data should last indefinitely and only be deleted by the user and not after 20 runs (v6.3.1) Aug 31, 2023
@SyntaxColoring SyntaxColoring self-assigned this Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A request for a new feature or a change that isn't a bug. May require further triage or scoping.
Projects
None yet
Development

No branches or pull requests

2 participants