MotionTracking Reader

Reads a list of MotionTracking '.csv'-export-files into Knime. This is done by searching for csv-files recursively within the specified directory or by selecting a list of files directly.

Options

Input Files

There are two modes of operation. Either you can choose a single directory in which the nodes will search for MotionTracking files. The search is applied not only to the direct directory contents but also to also its subfolders.
The second mode is to select a set of files (by keeping the apple/windows-key pressed while selecting files).
In the advanced tab of the configuration dialog one can define the pattern and associate the keywords to interpret the information of the file Paths contained in the first column. The default pattern is:
(?<barcode>.*)__(?<row>[0-9]{3})(?<column>[0-9]{3})[0-9]{3}_(?<timpoint>[0-9]{1})(?<wellfield>[0-9]{3})[.]mtf
This pattern matches file paths from images acquired with the Opera (Perkin Elmer) and that are converted with motion tracking into mtf-files. Anything that is contained within () -> token, will be associated with the variable that is contained within. The rest of the syntax is normal regular expressions (see java-doc).

The mandatory variables are
barcode
row
column

The optional variables are:
timepoint: time point between scans
wellfield: field of view within one well
frame: can be a time-frame of a movie or a z-slice of a z-stack (usually not used in HCS).

Thus another example for the same type of paths:
(?<barcode>.*)__(?<row>[0-9]{3})(?<column>[0-9]{3})(?<frame>[0-9]{3})_(?<timpoint>[0-9]{1})(?<wellfield>[0-9]{3})[.]mtf

Views

This node has no views

Workflows

• No workflows found

Links

• No links available

Developers