Exporting Variables in Fluent Control

Tecan
1

My workflow includes a user-provided list of sample dilution factors from 0x to 1000x, and then my script performs up to 3 fold dilutions across 3 plates to achieve the desired effect. The prepared samples are then moved to an assay plate, which requires a dynamic source labware including the neat tubes and 3 possible dilution plates.

My first thought is to export the source labware label into my worklist, but when using the export function, I do not see a way to control where in the destination file the variables are entered. It appears to default to writing into the wells after any occupied rows (column A at the end of my worklist). Is there any way to control which wells the export function writes to?

Alternatively I could export the info to a .xlsx file or just use an excel formula do define the labware, but I would like to avoid needing a VB script to convert to CSV as that requires some additional IT validation for each method, and I have not yet used any VB in Fluent, just Evoware and it looks a little more complicated with the VB .NET requirements.

Any other thoughts on this workflow are also appreciated.

2

Your middle paragraph is a bit confusing.

You want to export labware labels out of Fluent Control and into a worklist? And you want to do this with export function on Fluent Control but you cannot control where it’s exporting? Any additional visuals that you can provide?

With that said, VB will always be the cleanest and best way to tightly control your workflows through FC. It’s older but it’s still part of the .NET ecosystem which gives you access to pretty much any programming library available in .NET ecosystem from .NET Framework to .NET Core so you can do incredibly modern things with FC.

3

Thanks I’ll try to clarify. I am exporting the source labware string into my worklist CSV. I have an empty column in that file for the source labware to be written into. The Fluent export function writes the variables into A97 rather than A1.

image
image800Ă—280 4.23 KB

image
image761Ă—429 6.02 KB

4

Understood, and clarification, how are you pulling that source labware? How does it know to move from Source Tubes to Predilution 3 and back for example. Is that already well defined?

5

Yes that is defined from 1 of the 4 options for each sample. It’s a simple sliding scale based on how much each needs to be diluted.

image
image990Ă—352 21.2 KB

6

I assume you’re using the CSV to Worklist smart command?

Okay well if you don’t want to use VB right now,

I would also consider importing the CSV into an array and then you export the source labware label along with the array info for that sample into a new CSV. Line by Line.

The only problem is that you generate a lot of extra files that way on the Fluent Control backend and it can be slower than using a VB but it will work.

7

the “export variable” function is pretty limiting - it really only appends to the next available line

a couple of other options here:

  • use vb would be so much cleaner, quicker etc
  • consider a “concatenate” function to write the contents of the line to be exported - you only need to export 1 x variable & this contains the correct syntax for the columns required

I have written the exact scenario you are trying to create using vb.net functions, to alleviate the slowness of FluentControl in handling the calculations, reduce the coding in FC (& it’s instabilities) & also reduce the file archive bloat that FC performs each & every time variables are imported

DM me if you want more info - I understand the concern re IT validation/compliance but that effort is worth the benefits (in my opinion)

1 Like