Hello!
I am trying to complete a mixing step without the single channels raising up above the well and back down again between mix cycles as they currently do. Below are the settings for this step. According to my searches in the forum when trying to see if this had been resolved before, I saw that this can get tricky with fixed height dispenses because the mix height is ignored (?), so I am not sure what the best way forward is. Thank you!
Hi @Ham ,
You have to use the functions from STAR Tools :: Pipetting Tools to control the end height of the pipetting step. You can download the demo here.
Hi Brandon,
Is there a copy of star tools that is not a .pkg?
Thanks,
Colin
Hi @cwehrhan
What I do here, in Venus. I do not import as recovery but as user specified and I create a “dump” directory on my desktop. That way I can import what I want where I want 
Hi @cwehrhan ,
STAR Tools is a collection of several libraries and functions. A pkg combines these files into one easy to share file so that they can be imported within VENUS to prevent file loss. My recommendation is to always import a pkg using Recovery mode and when prompted to overwrite a file to select No to All.
Once imported, STAR Tools will be located at C:\Program Files (x86)\HAMILTON\Library\STAR Tools and will include a demo method and 5 SMT libraries.
Hi Brandon,
Gotcha, thought it was a normal HSL library, not a collection of .smt’s + HSL! Imported without overwriting our current libraries thanks!
Hi Brandon,
Thank you so much for the information and resource! How is this implemented? I have the .smt open and see the PIP_MixFromFixedHeight submethod, but how do you implement it within the method as you show in the photo you sent?
Hi @Ham ,
Like all libraries, they can be added to your method by selecting Method at the top of the file and then select Libraries…. From there you can select Add Library… and then browse to C:\Program Files (x86)\HAMILTON\Library\STAR Tools\STAR Pipetting Tools.
The aspirate, dispense, and Mix functions all function similar to each other. It is sequence based but requires all positions to be within the same X coordinate at the time of pipetting.
You give each function an array of heights. These are in reference to the bottom of the well. You can use the TOOL_BuildArrayForChannels function to build these arrays.
From there, you reference the sequence, channel pattern, and end position you want the channels to go to after performing the task.
| End Position | Location of Channels at End of Command |
|---|---|
| 0 | Moves the channels to travel height which is Z coordinate 245 |
| 1 | Moves the channels to Labware Clearance which is dictated by the labware definition |
| 2 | Moves the channels to the entrance of the well which is dictated by the labware definition |
| 3 | Keeps the channels at the same location that the pipetting step occurred |
You do need to pick up tips and eject tips before and after the commands.
NOTE: Sample tracking is not accounted for with these commands!
Thank you so much for the detailed explanation!
I have a quick clarifying question:
For the channel pattern str, what is the string defined as? I have values for everything else ready, but am not sure what this variable is suppoed to be beyond relating to the location of the mix.
Hi @Ham ,
The channel pattern is a string variable that dictates which channel is being used where 1 = channel active and 0 = channel not active. The pattern is in order from left to right corresponding to channels 1 through N in that order. So, a channel pattern of “11110000” means only channels 1-4 are active for that function.
You can use the function PIP_BuildChannelPatternFromSequence to build your channel pattern so that it is compliant with the Pipetting Tools functions.
NOTE: It is advised that the same channel pattern that is used for pipetting is used for the Tip Pick up as well to ensure the correct channels have tips loaded.
Great, thank you! I really appreciate all of the help, I look forward to testing this out soon.
It appears there is a syntax error in my input. This mix is happening within a submethod with the i_plateLocationSeq variable passed through it. Using the general aspirate/dispense steps with this sequence works fine and is defined as ML_STAR.sequencename. It appears that the issue is within the BuildChannelPatternFromSequence step. Also, I see VANTAGE within the error messages - are those unrelated files that are in use when this is used on a Vantage? I would be implementing this on a Star.
Hi @Ham ,
It looks like you had an older version of the library installed prior to importing. To fix, delete the folder C:\Program Files (x86)\HAMILTON\Library\STAR Tools then reimport the demo pkg using recovery mode and selecting no to all. That should fix the first set of errors. Make sure to have your method closed before importing.
The liquid class library needs to be installed for the second set. You can download it from the link below:
When installing, do not check the box for WhipPip liquid classes when prompted.
Thank you! That would explain this error when trying to import into Venus 4
@Ham ,
Yeah, in this instance you can disregard that warning. The library was written in a way to be compliant still with VENUS 4.
Could you use this same library to mix in a variety of locations within the same well without returning to transport height? … I’m working on a similar mixing dilemma - currently, I’ve defined 6 mixing locations per well of a 24-well plate (a hexagon), and I am currently accessing each position for mixing with a virtual labware shift for each location. Ideally, the channels would be able to stay at mixing height when moving between each of these locations within the same well. Any thoughts?
Also to confirm, star tools should work just the same on vantage?
