For context, I plan on installing an Inheco On Deck Thermal Cycler (ODTC) on our Star Plus instrument in the near future. We already have several protocols with our current deck layout (without the ODTC). I was wondering how easy or tedious it is to update our current methods with the new deck layout containing the ODTC? Could anyone give insight of how that works?
Appreciate any help or advice as always
It shouldn’t require much work to add the ODTC to the original Deck Layout(s) associated with your Methods. However, if you want to create a new Deck Layout with the ODTC that is separate from your original Deck Layout, then you can use the instructions below:
- Open your Method in Method Editor
- Go to the “Method” menu across the top of the window, and select “Instruments and Smart Steps…” from the drop-down.
- In the window that pops up, you’ll see the Deck Layout that is currently associated with the Method
- You can change the Deck Layout by clicking the “Browse…” button, opening the new Deck Layout you want to use, then clicking “OK” to close the window. The new Deck Layout should open in Method Editor. At this point, return to your Method and Save so that the new Deck Layout association holds.
Let me know if you have any questions.
Thank you @DanHartman_Hamilton!
My main concern was that is another device was integrated to the deck then I would have to go through the hassle of rewriting the method to accommodate for the “new” layout.
As long as you choose a space on your deck that is both reachable for transport and also doesn’t interfere with your existing carriers/workflow you do not need to edit the existing methods. However if you are tight on space and carriers must be moved to allow use of the new device, then you will need to update deck layouts to compensate for moved labware. Otherwise your existing methods can remain agnostic to the ODTC as they do not use it i.e. no need to add initializations and such to existing code.
I think a relevant piece of information is that you can have something on the deck and not have it in your layout. The instrument will not complain because there is an ODTC connected to it, which does not show up in a method’s deck layout file. (The way it will complain if you have a head connected but do not have a default waste position for the head, even if your particular protocol does not use the head.)