Is there any way I can build a librairy of submethods that I can easily import to any new method?
For instance, I have this set of actions which is always the same in all my methods:
Pickup tips
Apisrate from reservoir X
Dispense in labware whatever
Eject tips
Instead of re-writting it everytime, I would like to create a file (probably smt) that I can import to any new method I create. I usually do the copy paste from old method to new one but I would like to start building a proper toolbox for my future experiments while cleaning my code.
Hi KevinJ, I looked into this and decided to go with a template library instead of a submethod library. My understanding is that the submethod library steps “exist” in the submethod library such that when that smt is changed (if ever), then all methods that use that smt will be updated as well. Of course this can be a good or a bad thing. The template library is similar but it handles this part in a different way. For a submethod in a template library, when you pull that submethod into your method, that is essentially like copying and pasting the steps. Meaning you can change those steps in the submethod and it will only impact that method, not all methods that use that submethod from the template library. If you want to make multiple derivatives of that submethod in the same method you can. Just pull it over multiple times. Each time it creates a new submethod in your method.
hi Patrick,
Indeed, you are right. Great thank you!
I was more looking into converting a method into smt but I guess I will just quickly rebuild it. Thanks a lot for your help!
Hi there,
Thanks a lot for your answer.
Yes, from what I understood:
Sub librairy : toolkit that can be used in many methods. If the smt is modified, all the methods are affected
Sub template: more like a starting point to do not start from scratch everytime. LIke you mentionned: it is kind of like a copy paste that becomes local.
The thing that I still didn’t figure out is: is it possible to create a method directly from that librairy template? Or it is just better to create a generic MED file that contains the steps that I always use (initialize, subs) and just copy/paste rename everytime.
The way it works for me is that the specific template library contains several submethods (a template library is essentially identical to a sub method library except in the way it handles changes and instances). Those can be anything, like an initialize submethod that in my case initializes the hamilton, heater shakers, centrifuge etc. When i create a new method i drag that in. Then if you have a specific pipetting pattern, then you could make that as a submethod in your template library. For example, i have specific serial dilution, aliquotting, and spin/aspirate/shake steps that i drag in and modify as needed.
Ok great.
I played a bit with that and now I have a strange bug.
When I create a sub method librairy, the tool panel on the left is almost empty.
I do not see my ML_STAR, no gripper, almsot nothing:
I have tried to attach my deck to the librairy, load the librairy directly from a submethod but it remains empty. I also tried to load the HSLML_STARLib.hsl etc.
