Open
Conversation
Member
|
thanks for contributing this! just confirmed basic methods work on our 384 well odtc our 96 well odtc has some kind of problem, even the inheco software cannot find the ip. I will try again tomorrow running a method gives not entirely unexpected |
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Member
|
added an example notebook, start of docs |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
vibe-coded in 3 hours with gemini, tested against our 96w inheco ODTC and works
will need to be expanded to different model ODTCs (like 384)
The ODTC user flow is quite different from other thermal cyclers and as a result this backend is a little odd.
Before starting any PCR, you must first run a PreMethod for 7-10 minutes until the device is homogenously at temperature.
After PreMethod, you upload an xml protocol to the device (which is saved under a unique name until you delete it), which must have the same starting temp of your PreMethod.
If, by default, we decide to erase all methods in memory on the ODTC every time we write a new method, we could immediately upload and start a method containing a ramp from the current temp to the next temp you want to be, enabling set_block_temp and set_lid_temp to not be PreMethods and take <10 minutes