Tecan Fluent Version Control (git)

I’m happy to share that our publication about PyFluent SLKS99/PyFluent is now available on ChemRxiv PyFluent: Bridging Open-Source Python Automation with Proprietary Liquid Handling for AI-Driven Laboratories | ChemRxiv

3 Likes

Do you use Method Recovery?

I usually disable it because in the past it was very unreliable. I wonder if behavior is the same if it’s disabled.

No we were told by our Tecan Apps engineer not to use this as it “never works”. Did not know there is a setting for this on/off. I can give it a shot, although the recovery process was really painful so we’re hesitant to do more than the scripts/methods at the moment. We don’t have a huge fleet so keeping labware/liquid classes in git is not a top priority. Method history changes a lot more so than the deck, labware, liquid classes.

I happen to have an internal system that does a lot of the same things that PyFluent does. For instance, I also settled on using pythonnet. Nice work!

I am curious about this doc string:

    IMPORTANT: We use comtypes.client.CreateObject instead of pythonnet to create
    the FluentControl object. This is critical because:
    1. comtypes objects have QueryInterface, which is needed for COM event subscription
    2. pythonnet objects don't have QueryInterface, so event subscription fails
   

    This allows us to properly receive ChannelOpens/ChannelCloses events.

I currently only use pythonnet for event subscription. What issues did you run into?

1 Like