Is there space in PLR for an external (to any LH robot workstation) that would have the ability to coordinate many LH or other types of workstations that are running various protocols?
This would mesh well with the existing HTTP server that exists for LH robots by communicating in that manner via requests. This server would also have a database to track information regarding plates, wells, and parents that it could use to coordinate procedures on multiple machines running multiple procedures. It would integrate well with the current environment through LH callbacks, which could have an optional request sent out if a server is provided to the LH. This could additionally assist with state tracking of liquids as well as saving plate contents in the event of an error.
Thoughts?
3 Likes
probably something that adds a lot of values (besides the obvious, it make it much easier to use non-python languages with PLR). but has not been a priority for any user.
there is lh-server which tbh is quite underdeveloped. it’s been a long time since i used it, but since it’s part of ci it should still work. i implemented only some basic functions.
but the vision is that it implements the exact same protocol on the server side that the HTTPBackend does on the client side. Making it possible to actually use PLR on both ends (and theoretically even chain them).
We should also have servers for other front ends, similar to LH. and http backends for them.
interfacing with the resource model is an entirely uncharted project
if you want this, i definitely support developing it further!
I have a work in progress for this type of use case (and also inventory/protocols management). I have the backend done but need to finish up tests and docs before I share publicly. If you have any interest in contributing or want to see how I structured the approach or just have other questions, PM me and I can add you to the currently private repo.
4 Likes