thank you Camillo for taking the lead on this. Upon reading this I agree that more planned & organized development, rather than schizo ad-hoc development of the past, can be an accelerant for PLR.
All of your suggestions are excellent. For me, I particularly want to focus (and can take the lead on?):
- versioning
- more documentation
- every major resource subclass should have a doc page. right now, few do.
- dedicated cookbook with quick ‘how-to’s’
- full protocol examples
- error handling, either as proposed by Camillo or a similar method
Other priorities for me are:
- re-implement tip racks: currently the “rack” is redefined for every tip type, even though the physical rack object is the same.
- improve cytation5 integration drastically (filters, lenses). will soon be testing in production protocol
- we recently acquired 2 cytation1’s, the firmware looks identical at first glance
- finish currently wip machine integrations
- ml prep
- a4s plate sealer
- inheco odtc
- new machines:
- cytoflex flow machine
- image express
- maintenance scripts
- i didn’t believe in the past, but multiple reliable people say it’s actually useful
- our machines have stochastic errors, curious if this fixes
- io layer for CI (will explain in a post soon)
- higher level methods like serial dilute and aliquot
- robot arms if it comes up
Last week, I was able to create a protocol where every plate/resource/operation was already defined. It took less than an hour to write & water test this protocol with copilot. Since most of our protocols are fundamentally easy to express, writing code (one medium expression) should also be trivial.
I suggest creating a new thread on the forum for every individual action-point to be discussed in more detail. We already have threads for some topics. Let’s keep this thread to what Camillo proposed:
- what you want to do
- what you want to see