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

Flexibility as a property? #8

Open
photocyte opened this issue Jun 26, 2023 · 3 comments
Open

Flexibility as a property? #8

photocyte opened this issue Jun 26, 2023 · 3 comments

Comments

@photocyte
Copy link
Member

Microplates are generally pretty inflexible, but when you get into "PCR" plates (and PCR plates are a subset of microplates - I think the "full-skirted" ones may even be SLAS/ANSI standards compliant. Un-skirted clearly aren't given the footprint/skirt is part of the SLAS/ANSI standards), they may be are flexible enough that they can flex in robotics gripper systems (even "simple" robotics systems like small locking tab in a plate carrier for a plate reader). This can lead to dropping a plate or instrument damage.

A flexible property, with two states: "Inflexible", "Notably flexible" might be a place to annotate that the plate should only be used with robotics systems with caution.

@markdoerr
Copy link
Collaborator

Thanks, @photocyte, for this idea :)
in the current implementation, we have the property "MaxGrippingPressure" (mind: not force ! ;).
Do you think, we can use this Parameter to model, what you had in mind ?

@photocyte
Copy link
Member Author

I suppose, if MaxGrippingPressure = 0 -> indicates a piece of labware should not be used with automation… not the most intuitive annotation

@photocyte
Copy link
Member Author

A bit more context from bi-weekly discussion: I was coming from the direction of trying to prevent flexible plates from being used in incompatible instruments & causing them damage. Knowledge to not do this, is "implicit knowledge" for people who have a decent amount of automation experience. But having the knowledge be explicit, could prevent naive users & LLMS/AI generated protocols from making this mistake.

This is a related concept:
#5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants